Clicking the desktop app's fork button does not create a forked conversation or surface any error. A new forked conversation should open, or the app should surface an actionable error if the current thread cannot be forked.

• 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.
• codex-rs/tui/src/app.rs handles AppEvent::ForkCurrentSession and surfaces an error if the current thread is not forkable

TL;DR

The issue is likely due to a missing or incorrect button handler for the fork button in the desktop app, which can be resolved by verifying the button's click event handler.

Guidance

• Verify that the fork button in the desktop app has a click event handler assigned to it, and that it correctly calls the AppEvent::ForkCurrentSession handler.
• Check the desktop app's code for any typos or incorrect function calls that might prevent the fork button from working as expected.
• Review the codex-rs/tui/src/app.rs file to ensure that the AppEvent::ForkCurrentSession handler is correctly implemented and surfaces an error if the current thread is not forkable.
• If the issue persists, try debugging the desktop app to see if any errors are thrown when the fork button is clicked.

Example

No code example is provided as the issue lacks specific code details.

Notes

The issue may be specific to the private desktop-client code, which is not publicly available. Therefore, the solution may require access to the private codebase.

Recommendation

Apply workaround: Verify the button's click event handler and review the AppEvent::ForkCurrentSession handler implementation to ensure correct functionality. This is because the issue is likely related to the desktop app's wiring, and verifying the event handler can help identify the root cause.