How to Draft Threads With a Manus Cue Connector for X Posting

Drafting threads is the right job for a Manus Cue connector for X posting, because a post on X is public the moment it lands and Cue documents no step where you approve one. Cue is the personal agent app Manus launched on 28 September 2026, and each Cue agent gets its own email, phone number, wallet and computer. This guide covers the X half: the field name, how a thread works, and what a drafts-only key changes.

The short version: connect Cue to the AdaptlyPost MCP server with a Contributor key as in the pillar guide, tell it the X field is twitterConnectionIds with platform value TWITTER, and have it save every X post as a draft. You publish.

What does Cue change about posting to X?

Cue changes who holds the pen: a Cue agent writes and acts as its own identity, and Manus has not documented an approval gate for its actions as of 29 September 2026. On X that matters most for threads, where one wrong part sits in public next to the rest. The fix sits on the AdaptlyPost side. A key issued under the Contributor role creates drafts and cannot schedule or publish, so nothing reaches your timeline until a person sends it.

Manus's own X example points the same way. The Manus 2.0 help article describes an Automation that watches a product account on X and drafts a summary when a new update appears, and adds: "You still decide what goes out." That example is Manus rather than Cue, and it is the right default for Cue too.

What do I tell Cue before its first X draft?

Tell Cue to read your X account back, confirm the field name from the tool schema, and save drafts only. The connector setup, the Manus server form and the token role are in the pillar guide. The X addition is this prompt:

Use the AdaptlyPost connector. Read-only first.
 
1. Call list_accounts and show me the X account: username and status.
2. Confirm from the create_post schema that X posts use
   twitterConnectionIds and the platform value TWITTER.
3. Every X post you make is a draft: create_post with saveAsDraft: true.
   Number thread parts "1/", "2/" and so on, one draft per part.

Step 1 is the one to insist on. Posting as the wrong handle is the X mistake that is hardest to walk back, and list_accounts returns the username attached to each connection.

Why is the X field still twitterConnectionIds?

The X field is twitterConnectionIds because the AdaptlyPost API named it before the rebrand and renaming a published field breaks existing integrations. The spec fetched on 29 September 2026 has twitterConnectionIds in both the create and bulk request schemas, uses TWITTER as the platform value, and contains no xConnectionIds anywhere. The Grok bot template for X posting tells the longer story of why the name stayed.

An MCP client reads the field from the tool schema, so Cue gets it right when it reads before it writes. An agent improvising from the brand name invents xConnectionIds, which the spec does not define, and the request then has no X target. Step 2 of the prompt above exists to catch that.

How does Cue draft an X thread?

Cue drafts an X thread as one numbered draft per part, because AdaptlyPost has no thread object and a Contributor key cannot use the bulk endpoint. A thread in AdaptlyPost is a sequence of timed posts. POST /social-posts/bulk schedules 1 to 100 of them in one call, but it requires the posts.schedule permission, which the Contributor role lacks.

You:  Draft a 4-part thread on our launch for X.
 
Cue:  create_post { platforms: ["TWITTER"], contentType: "TEXT",
                    twitterConnectionIds: ["..."], timezone: "Europe/Kyiv",
                    text: "1/ ...", saveAsDraft: true }
      ... repeated for "2/", "3/" and "4/" ...
      Four drafts saved. IDs: ...

You then publish the parts in order, two minutes apart, from AdaptlyPost. Spacing reads better anyway: a thread dumped at once reads as a dump, and the same posts two minutes apart read as a thread being written.

If you trust the setup after a few weeks, an Editor key changes the trade. Cue then books the whole thread through the bulk endpoint, with platforms, timezone and twitterConnectionIds once at the top and each post carrying its own contentType, text and scheduledAt. You also lose the only enforced approval step, so make that switch deliberately.

How do X and Bluesky share one request?

X and Bluesky share one request by adding blueskyConnectionIds next to twitterConnectionIds, since neither network has a config object in the AdaptlyPost spec. As of 29 September 2026 the spec defines per-platform configs for Pinterest, TikTok, Instagram, Facebook, YouTube and LinkedIn only. X and Bluesky take a connection ID array, text and optional media.

Use platformTexts so each timeline gets its own version instead of one caption trimmed to fit both. mediaAltTexts carries alt text for each image, up to 1,000 characters each, and AdaptlyPost sends it to both X and Bluesky. The X posting API page lists the rest of the X request.

Can Cue reply to mentions on X through AdaptlyPost?

Cue cannot reply to mentions or send direct messages on X through AdaptlyPost, because the AdaptlyPost spec defines no reply, mention or DM endpoint. The connector creates posts and reports their results per platform. That limit works in your favour with an agent that has its own identity.

A Cue agent sends messages as itself from its own email and phone number, and Runtimewire noted on 28 September 2026 that the launch material does not explain how users "restrict what agents can do with their email or phone identity." Keep your X login away from the agent. Through AdaptlyPost it reaches only the handles you connected, with only the permissions the key carries.

What breaks on X specifically?

An X connection that lapses between drafting and publishing breaks a thread, because AdaptlyPost refuses posts to an account marked unauthorized with a 400 until you reconnect it in the dashboard. list_accounts returns each account's status, so ask Cue for it before you publish a thread drafted days earlier. AdaptlyPost also fires an account.unauthorized webhook if you want the warning pushed to you.

After publishing, list_post_results reports each platform separately, and retry_failed_platforms reruns only the failures. Media needs an upload first, and X video goes through an initialize, append and finalize sequence that takes longer than an image. AdaptlyPost counts rate limits per API key and returns RateLimit-Remaining and RateLimit-Reset on every response, with Retry-After on a 429.

Frequently Asked Questions

Can Cue schedule an X thread with a Contributor key?

No. The Contributor role creates and edits its own drafts and cannot schedule or publish, and the bulk endpoint requires the posts.schedule permission. Cue saves one draft per part, and you publish them in order.

Does the connector work with an X Premium account?

Yes. The AdaptlyPost spec sets no maximum length on text, so X applies whatever limit your account carries. Put the long version in platformTexts for TWITTER and a shorter one for Bluesky in the same call.

How is this different from the Muse and Grok routes?

Cue connects through a custom MCP server added in Manus, while Meta Muse builds its own client from the OpenAPI spec and a Grok bot template installs from a share link. The Meta Muse connector for X posting and the Grok template post cover those routes. All three send twitterConnectionIds.

Can a Manus Automation watch X and draft posts for me?

Manus documents an Automation that watches a product account on X and drafts a summary of each update, with the decision left to you. That is a Manus 2.0 feature. Manus has not documented scheduled or triggered tasks inside Cue as of 29 September 2026, so test in Cue before relying on it.

Does the token decide which X account Cue posts as?

No. The connection ID in twitterConnectionIds decides the handle, and the token decides what Cue is allowed to do. Read the handle back with list_accounts before the first draft.

How do I stop Cue posting to X?

Revoke the adaptly_ token at adaptlypost.com/api-tokens, and AdaptlyPost disconnects every agent using it at once. Your X connection stays in AdaptlyPost. The pillar guide covers removing the connector in Manus.

What does a Cue thread draft look like in AdaptlyPost?

Each part is its own draft, created with create_post, platforms set to TWITTER and saveAsDraft: true. The text starts with "1/", "2/" and so on, because AdaptlyPost has no thread object. You publish the drafts in order from AdaptlyPost.

What happens if Cue uses xConnectionIds instead of twitterConnectionIds?

The request has no X target, because the AdaptlyPost spec does not define xConnectionIds. Agents guess this name from the brand. Tell Cue to read the create_post schema before it writes, and it will use twitterConnectionIds.

What if my X account disconnects before I publish a thread?

AdaptlyPost refuses posts to an account marked unauthorized with a 400 until you reconnect it in the dashboard. Ask Cue for list_accounts before you publish drafts that are days old. An account.unauthorized webhook can push the warning to you.

When should I switch Cue from a Contributor key to an Editor key?

Switch after a few weeks of drafts you have no edits for, and do it on purpose. An Editor key lets Cue schedule a whole thread through the bulk endpoint, 1 to 100 posts in one call. You also lose the only enforced approval step.

Create a Contributor token and let Cue draft your next thread, or read the MCP setup guide first.

Sources: Manus's Introducing Manus 2.0 (28 September 2026), Manus Help Center What is new in Manus 2.0?, Manus docs on custom MCP, Runtimewire coverage (28 September 2026), the AdaptlyPost MCP setup guide and the AdaptlyPost OpenAPI spec. Checked 29 September 2026.