baoyu-post-to-x

Post to X (Twitter)

Posts text, images, videos, and long-form articles to X via a real Chrome browser.

In Codex, do not conflate these browser paths:

• Codex Chrome plugin / @chrome / Chrome Extension: use the bundled chrome:Chrome skill and its Node REPL browser client. This is required whenever the user says "Codex Chrome plugin", "Codex 自带的 Chrome 插件", @chrome, or similar.
• Chrome Computer Use: use mcp__computer_use__.* against the visible Google Chrome UI only when the user asks for Computer Use or no Chrome-plugin preference is stated and Computer Use is available.
• CDP script mode: use only as a fallback when the selected mode is unavailable or the user explicitly asks for CDP/script mode.

Script Directory

Important: All scripts are located in the scripts/ subdirectory of this skill.

Agent Execution Instructions:

1. Determine this SKILL.md file's directory path as {baseDir}
2. Script path = {baseDir}/scripts/<script-name>.ts
3. Replace all {baseDir} in this document with the actual path
4. Resolve ${BUN_X} runtime: if bun installed → bun; if npx available → npx -y bun; else suggest installing bun

Script Reference:

Execution Mode Selection (Required)

Choose exactly one mode before interacting with X:

1. If the user explicitly asks for the Codex Chrome plugin, @chrome, the Chrome extension, or "Codex 自带的 Chrome 插件", use Codex Chrome Plugin Mode. Do not call Computer Use first.
2. If the user explicitly asks for Chrome Computer Use, use Chrome Computer Use Mode. Do not fall back to CDP, Playwright, the in-app Browser, or the Chrome plugin without telling the user and getting approval.
3. If the user explicitly asks for CDP/script mode, use CDP Script Mode.
4. Otherwise, prefer Chrome Computer Use Mode. For Markdown X Articles with local content images, use the tested X editor flow: insert each body image from the toolbar (Insert -> Media -> dialog icon button Add photos or video) at its placeholder, then delete the placeholder text. Use CDP Script Mode only when the selected browser-control mode is unavailable or the UI upload/selection flow is unreliable.

Never use the in-app Browser for X publishing workflows.

Codex Chrome Plugin Mode

Use this mode whenever the user requests the Codex Chrome plugin, @chrome, or the Chrome Extension path. This uses the user's real Chrome profile and X login through the bundled Chrome plugin, not Computer Use and not CDP.

Setup

1. Load the chrome:Chrome skill before browser work.
2. Use tool_search for node_repl js if the Node REPL js tool is not already visible.
3. Initialize the Chrome browser client exactly as the Chrome skill specifies, then run a lightweight call such as browser.user.openTabs() to verify the extension connection.
4. If the first lightweight call fails, wait 2 seconds and retry once. If it still fails, follow the Chrome skill's extension checks and recovery steps. If checks pass but communication still fails, ask the user before opening a new Chrome window. Do not switch to Computer Use or CDP silently.

General rules

• Use the Chrome plugin's browser.tabs.*, tab.playwright.*, tab.cua.*, and file chooser APIs for X UI actions.
• Shell commands are allowed for Markdown preprocessing and rich-HTML clipboard preparation. For X Article body images, do not rely on image clipboard paste; use the editor's Insert -> Media upload flow.
• If a file upload fails with Not allowed, tell the user: To enable file upload, go to chrome://extensions in Chrome, click Details under the Codex extension, and enable "Allow access to file URLs." See https://developers.openai.com/codex/app/chrome-extension#upload-files for details.
• If the Chrome plugin reports native pipe is closed, retry the lightweight browser call once after 2 seconds, then run the Chrome skill health checks. If Chrome is running, the extension is enabled, and the native host manifest is correct, ask permission to open a new Chrome window and retry. Do not keep sending browser actions through the broken pipe.
• Never click Publish, Post, or any externally visible submit action without explicit final confirmation from the user in the current conversation.

X Articles

1. Convert Markdown and keep the image map:

   ${BUN_X} {baseDir}/scripts/md-to-html.ts article.md --save-html /tmp/x-article-body.html > /tmp/x-article.json

2. Read the JSON output for title, coverImage, and contentImages (placeholder → localPath).
3. Open or create the article draft at https://x.com/compose/articles.
4. Upload the cover with the Chrome plugin file chooser flow. If upload is blocked by extension permissions, stop and report the exact permission fix above.
5. Fill the title, then copy rich HTML:

   ${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts

Preferences (EXTEND.md)

Check EXTEND.md in priority order — the first one found wins:

If none found, use defaults.

EXTEND.md supports: Default Chrome profile

Prerequisites

• Google Chrome or Chromium
• bun runtime
• First run: log in to X manually (session saved)

Pre-flight Check (Optional)

Before first use, suggest running the environment check. User can skip if they prefer.

${BUN_X} {baseDir}/scripts/check-paste-permissions.ts

Checks: Chrome, profile isolation, Bun, Accessibility, clipboard, paste keystroke, Chrome conflicts.

If any check fails, provide fix guidance per item:

References

• Regular Posts: See references/regular-posts.md for manual workflow, troubleshooting, and technical details
• X Articles: See references/articles.md for long-form article publishing guide

Chrome Computer Use Mode

Use this mode when the user explicitly asks for Chrome Computer Use, or when no Chrome-plugin preference is stated and Codex can control Google Chrome with Computer Use. This uses the user's existing Chrome window, cookies, login, extensions, and X session.

General rules:

• Start each assistant turn that controls Chrome by calling get_app_state for Google Chrome.
• Prefer element-index actions when available; use coordinates only for editor text selection or drag selection.
• Do not use the in-app Browser, the Chrome plugin, Playwright, or CDP for X UI actions in this mode unless the user approves a mode change.
• Never click Publish, Post, or any externally visible submit action without an explicit final confirmation from the user in the current conversation.

Regular posts:

1. Open or navigate Chrome to https://x.com/compose/post.
2. Type the post text into the composer using Computer Use.
3. For each image, run:

   ${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts image /absolute/path/to/image.png

4. Paste with Computer Use (super+v on macOS, control+v on Windows/Linux), then wait until X finishes uploading media.
5. Ask for confirmation before clicking Post.

Video posts:

1. Open or navigate Chrome to https://x.com/compose/post.
2. Type the post text into the composer.
3. Use the visible media upload/file picker UI to attach the video.
4. Wait for upload and processing to complete.
5. Ask for confirmation before clicking Post.

Quote tweets:

1. Open the tweet URL in Chrome.
2. Use the visible quote/repost UI to choose Quote.
3. Type the comment.
4. Ask for confirmation before clicking Post.

X Articles:

1. Convert Markdown and keep the image map:

   ${BUN_X} {baseDir}/scripts/md-to-html.ts article.md --save-html /tmp/x-article-body.html > /tmp/x-article.json

2. Read the JSON output for title, coverImage, and contentImages (placeholder → localPath).
3. In Chrome, open https://x.com/compose/articles, create or open the draft, upload the cover if present, and fill the title.
4. Copy rich HTML to the clipboard:

   ${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts html

If Computer Use selection, toolbar upload, or file-picker control becomes unreliable, stop and report the blocker instead of switching to the Chrome plugin or CDP silently.

CDP Script Mode (Fallback)

Use the script sections below only when the selected browser-control mode is unavailable, unreliable, or explicitly not requested. These scripts launch or reuse a real Chrome instance via CDP and keep the browser open for review.

Do not use CDP Script Mode when the user explicitly requires the Codex Chrome plugin or Chrome Computer Use unless the user approves the fallback after you explain the blocker.

Post Type Selection

Unless the user explicitly specifies the post type:

• Plain text + within 10,000 characters → Regular Post (Premium members support up to 10,000 characters, non-Premium: 280)
• Markdown file (.md) → X Article

Regular Posts

${BUN_X} {baseDir}/scripts/x-browser.ts "Hello!" --image ./photo.png

Parameters:

Note: Script opens browser with content filled in. User reviews and publishes manually.

Codex mode note: If the user explicitly requested the Codex Chrome plugin, use Codex Chrome Plugin Mode. Otherwise, if Chrome Computer Use is enabled, use Chrome Computer Use Mode instead of running x-browser.ts.

Video Posts

Text + video file.

${BUN_X} {baseDir}/scripts/x-video.ts "Check this out!" --video ./clip.mp4

Parameters:

Note: Script opens browser with content filled in. User reviews and publishes manually.

Codex mode note: If the user explicitly requested the Codex Chrome plugin, use Codex Chrome Plugin Mode. Otherwise, if Chrome Computer Use is enabled, use Chrome Computer Use Mode instead of running x-video.ts.

Limits: Regular 140s max, Premium 60min. Processing: 30-60s.

Quote Tweets

Quote an existing tweet with comment.

${BUN_X} {baseDir}/scripts/x-quote.ts https://x.com/user/status/123 "Great insight!"

Parameters:

Note: Script opens browser with content filled in. User reviews and publishes manually.

Codex mode note: If the user explicitly requested the Codex Chrome plugin, use Codex Chrome Plugin Mode. Otherwise, if Chrome Computer Use is enabled, use Chrome Computer Use Mode instead of running x-quote.ts.

X Articles

Long-form Markdown articles (requires X Premium).

${BUN_X} {baseDir}/scripts/x-article.ts article.md
${BUN_X} {baseDir}/scripts/x-article.ts article.md --cover ./cover.jpg

Parameters:

Frontmatter: title, cover_image supported in YAML front matter.

Codex mode note: If the user explicitly requested the Codex Chrome plugin, follow Codex Chrome Plugin Mode above. If the user explicitly requested Chrome Computer Use, follow Chrome Computer Use Mode. Otherwise, prefer Chrome Computer Use; for Markdown articles with local content images, use the toolbar Insert -> Media image-upload workflow before falling back to x-article.ts in CDP Script Mode.

CDP fallback note: The script opens browser with article filled in. User reviews and publishes manually unless --submit is used.

Publish safety: Do not use --submit or click Publish unless the user explicitly confirms the final public publish action.

Post-Composition Check: The script automatically verifies after all images are inserted:

• Remaining XIMGPH_ placeholders in editor content
• Expected vs actual image count

If the check fails (warnings in output), alert the user with the specific issues before they publish.

Troubleshooting

Chrome debug port not ready

CDP fallback only: if a script fails with Chrome debug port not ready or Unable to connect, kill existing Chrome CDP instances first, then retry:

pkill -f "Chrome.*remote-debugging-port" 2>/dev/null; pkill -f "Chromium.*remote-debugging-port" 2>/dev/null; sleep 2

Important: This should be done automatically — when encountering this error, kill Chrome CDP instances and retry the command without asking the user.

Notes

• First run: manual login required (session persists)
• In Codex Chrome Plugin Mode and Chrome Computer Use Mode, use the user's existing Chrome session and do not launch a separate CDP profile
• CDP scripts only fill content into the browser by default; user must review and publish manually unless --submit is explicitly used
• Cross-platform: macOS, Linux, Windows

Extension Support

Custom configurations via EXTEND.md. See Preferences section for paths and supported options.