{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigbt3x63be2yzopnspqnk3ghdifpei3mjxmjmpuh5om3jygvuwqqq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmcwbq22i7s2"
  },
  "path": "/t/codex-in-app-browser-x-composer-repeatedly-fails-with-clipboard-editor-state/1381384#post_1",
  "publishedAt": "2026-05-20T21:41:39.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "x.com"
  ],
  "textContent": "I am using the Codex desktop app with the in-app browser to help manage a real social-posting workflow on x.com. The workflow is: Codex finds a post, drafts a reply, stages it in the X composer, and the human user reviews/edits/approves before posting.\n\nThis is extremely useful when it works, but the browser/editor interaction is failing often enough that the workflow becomes brittle.\n\n## Environment\n\n  * Codex desktop app on macOS\n  * In-app browser logged into x.com\n  * Target editor: X reply composer / contenteditable text field\n  * Human remains in the loop for final approval\n\n\n\n## What happens\n\nAfter one or two successful staged replies, Codex often fails when trying to fill the X composer. The visible/runtime error presented to the agent is:\n\n`Browser Use encountered an error interacting with this webpage's clipboard: Browser Use virtual clipboard is not installed`\n\nOther related behavior I saw in the same session:\n\n  * Filling the composer sometimes appends the new draft to the old draft instead of replacing it.\n  * Select-all/delete did not reliably clear the composer contents.\n  * Opening a fresh X tab sometimes fixes it, but not always.\n  * Fully reconnecting/resetting the browser session and opening a fresh tab usually fixes it.\n  * The problem appears more likely after the human user manually interacts with the browser/editor between Codex actions.\n\n\n\n## Repro shape\n\n  1. Open Codex desktop app.\n  2. Use the in-app browser logged into x.com.\n  3. Navigate to an X post.\n  4. Have Codex stage text into the reply composer.\n  5. User edits or manually posts, then asks Codex to stage another reply.\n  6. Repeat across a few posts.\n\n\n\nExpected: Codex can reliably replace the text in the active composer.\n\nActual: the composer may fail with the virtual clipboard error, or duplicate/append stale rich-text contents instead of cleanly replacing the draft.\n\n## Why this matters\n\nThis is not just a toy browser task. The workflow was: AI-assisted social/content operations with human approval. Codex was genuinely useful at finding targets, drafting replies, and keeping the user honest, but the browser bridge/editor state issue kept breaking the flow.\n\nA reliable first-class way to set text in modern contenteditable editors, or a more robust fallback when the virtual clipboard is unavailable, would make this kind of human-in-the-loop browser workflow much more dependable.",
  "title": "Codex in-app browser X composer repeatedly fails with clipboard/editor state"
}