Desktop fork button does nothing
Resolved 💬 0 comments Opened Apr 13, 2026 by iamhectorlopez Closed May 2, 2026
Summary
Clicking the desktop app's fork button does not create a forked conversation or surface any error.
Reproduction
- Open an existing conversation in the Codex desktop app.
- Click the fork button in the conversation controls.
- Observe that nothing happens.
Expected
A new forked conversation should open, or the app should surface an actionable error if the current thread cannot be forked.
Actual
The click appears to be a no-op.
Notes
- A user screenshot shows the conversation-level fork icon in the desktop UI, but the click does not trigger visible navigation, confirmation, or error handling.
- I audited the public openai/codex repo before filing this. The shared fork backend appears to exist in the public codebase:
- codex-rs/app-server/src/codex_message_processor.rs handles hread/fork
- codex-rs/tui/src/app.rs handles AppEvent::ForkCurrentSession and surfaces an error if the current thread is not forkable
- I could not find the desktop-specific button handler in the public repo, so this may be a private desktop-client wiring/regression rather than a shared hread/fork implementation bug.
Why this issue still belongs here
The bug is user-facing in Codex, and the public repo is the closest visible tracker even if the failing button wiring lives outside the currently published source tree.