Draft-first X/Twitter account management workflow for OpenClaw. Use when the user wants to read their X account context, draft tweets, replies, quote tweets, or threads, and keep every write action gated behind explicit approval. Use with the OpenClaw X plugin when managing a personal X account safely.
Use the X plugin as a draft-first system, not an autonomous posting engine.
Never treat a generated tweet/reply/quote as ready to publish by default. Always:
Working now:
x_account_connectx_account_auth_urlx_account_completex_account_mex_timeline_mex_timeline_mentionsx_post_getx_post_contextx_post_createx_post_replyx_post_quotex_post_threadx_post_approvex_post_publishx_util_resolve_urlStill partial:
Prefer read actions before drafting whenever the content depends on an external post or thread. Use:
x_util_resolve_url to normalize a target post URLx_post_get for a single post with normalized outputx_post_context for a post plus immediate referenced contextx_timeline_mentions when deciding whether/how to replyx_timeline_me when recent account voice/context mattersUse:
x_post_create for a normal tweetx_post_reply for a replyx_post_quote for a quote tweetx_post_thread for multi-post threadsTreat returned draftId as the durable handle for follow-up approval/publish steps.
Use x_post_approve only after the user has explicitly approved the exact draft.
Then use x_post_publish only for the approved draft id.
Do not mutate draft text between approval and publish.
Before drafting a reply:
A quote tweet should add something:
Do not produce empty applause unless the user wants that tone.
When the user does not specify tone, prefer concise, high-signal writing over bloated threadbait. Offer 2-3 options when tone uncertainty is real.
That is the intended shape for Prince’s eventual dedicated X-managing agent.