{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibhxfzcjygl4s5c4ej2hr3xsmgtpz3yvuyt3mtn6z3jloilywvgqi",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mm52dsegota2"
  },
  "path": "/t/add-fork-conversation-support-to-codex-in-the-mobile-app/1381222#post_1",
  "publishedAt": "2026-05-18T13:03:54.000Z",
  "site": "https://community.openai.com",
  "textContent": "I would like Codex conversations in the mobile app to support the same “fork conversation” workflow available in the Codex desktop app.\n\nCodex remote access from mobile is already very useful: I can continue threads, answer questions, approve actions, review what Codex found, and change direction while away from my Mac.\n\nHowever, when I reach a point where there are multiple possible directions, I cannot easily fork the current conversation from mobile. On desktop, forking is a very natural workflow: I can preserve the current thread, explore and ask add questions.\n\nOn mobile, this limitation makes the remote workflow feel less complete. I often want to make a quick decision from my phone, but I hesitate because changing direction in the current thread can pollute or derail the original work.\n\nForking is especially valuable for coding-agent workflows because decisions are often exploratory:\n\n  * Try implementation A without losing implementation B\n  * Investigate a bug from an earlier point in the thread\n  * Explore a refactor separately from the main fix\n  * Ask Codex to take a different technical direction without overwriting the current plan\n  * Preserve a safe thread before approving more invasive actions\n\n\n\nThis matters even more on mobile, because mobile is often used exactly when the user needs to make a quick decision while away from the workstation.\n\nA simple first version could be:\n\n  * Add “Fork conversation” in the message/context menu\n  * Allow forking from the latest message\n  * Ideally, match desktop behavior and allow forking from an earlier message\n  * After forking, open the new thread immediately in the mobile app\n  * Keep the fork associated with the same connected host/project/worktree behavior as desktop\n\n\n\nThis would make Codex mobile remote access much more useful and safer to use during real development work, because users could explore alternative paths without damaging the original thread.",
  "title": "Add “Fork conversation” support to Codex in the mobile app"
}