codex - ✅(Solved) Fix Add a way to ask side questions without affecting the main session context [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18125Fetched 2026-04-17 08:32:26
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1cross-referenced ×1unlabeled ×1

Fix Action

Fixed

PR fix notes

PR #18190: Add /side conversations

Description (problem / solution / changelog)

The TUI supports long-running turns and agent threads, but quick side questions have required interrupting the main flow or manually forking/navigating threads. This PR adds a guarded /side flow so users can ask brief side-conversation questions in an ephemeral fork while keeping the primary thread focused. This also helps address the feature request in #18125.

The implementation creates one side conversation at a time, lets /side open either an empty side thread or immediately submit /side <question>, and returns to the parent with Esc or Ctrl+C. Side conversations get hidden developer guardrails that treat inherited history as reference-only and steer the model away from workspace mutations unless explicitly requested in the side conversation.

The TUI hides most slash commands while side mode is active, leaving only /copy, /diff, /mention, and /status available there.

Changed files

  • codex-rs/tui/src/app.rs (modified, +473/-16)
  • codex-rs/tui/src/app/side.rs (added, +390/-0)
  • codex-rs/tui/src/app_event.rs (modified, +7/-0)
  • codex-rs/tui/src/app_server_session.rs (modified, +50/-0)
  • codex-rs/tui/src/bottom_pane/chat_composer.rs (modified, +28/-5)
  • codex-rs/tui/src/bottom_pane/command_popup.rs (modified, +7/-0)
  • codex-rs/tui/src/bottom_pane/footer.rs (modified, +9/-1)
  • codex-rs/tui/src/bottom_pane/mod.rs (modified, +16/-0)
  • codex-rs/tui/src/bottom_pane/slash_commands.rs (modified, +49/-5)
  • codex-rs/tui/src/chatwidget.rs (modified, +184/-35)
  • codex-rs/tui/src/chatwidget/slash_dispatch.rs (modified, +80/-15)
  • codex-rs/tui/src/chatwidget/snapshots/codex_tui__chatwidget__tests__side_context_label_preserves_status_line.snap (added, +9/-0)
  • codex-rs/tui/src/chatwidget/snapshots/codex_tui__chatwidget__tests__slash_side_requests_forked_side_question_while_task_running.snap (added, +11/-0)
  • codex-rs/tui/src/chatwidget/tests.rs (modified, +1/-0)
  • codex-rs/tui/src/chatwidget/tests/helpers.rs (modified, +5/-0)
  • codex-rs/tui/src/chatwidget/tests/side.rs (added, +292/-0)
  • codex-rs/tui/src/slash_command.rs (modified, +13/-1)
  • codex-rs/tui/tooltips.txt (modified, +1/-0)
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI, CODEX APP

What feature would you like to see?

It’d be really nice if Codex had a /btw feature. Right now, if I want to ask something on the side without polluting the main context, I have to fork a new session.

Additional information

No response

extent analysis

TL;DR

The user is requesting a new feature, specifically a /btw command, to allow for side conversations without creating a new session.

Guidance

  • The user is looking for a way to have a side conversation without polluting the main context, suggesting a need for a feature that allows for temporary or secondary discussions.
  • To achieve this, the development team could consider adding a new command or feature that creates a temporary or nested conversation thread.
  • The user's current workaround is to fork a new session, which they find inconvenient.
  • The development team may want to consider the user experience and workflow implications of adding such a feature.

Notes

The issue lacks technical details, and the request is for a new feature rather than a fix for an existing issue.

Recommendation

Apply workaround: The user can continue to use the current workaround of forking a new session until the requested feature is implemented, as there is no clear indication of a existing solution or fix.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING