openai / openai/codex

VS Code extension: Support /side and /btw side conversations

Open
#43,207 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement extension session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

IDE Extension (VS Code)

What feature would you like to see?

Please add side conversations to the Codex VS Code extension, accessible through /side and /btw or an equivalent UI action.

While Codex is working on a task, I want to ask questions about its reasoning, findings, or the code without interrupting or redirecting that task. The side conversation should inherit the main conversation's context so I do not need to repeat the background.

Proposed behavior
  • Open a side conversation from the current chat, including while the main task is running.
  • Give the side conversation access to the main chat's context.
  • Keep side-chat messages and answers separate from the main conversation; they should not automatically steer the active task.
  • Let the main task continue while I ask follow-up questions in the side chat.
  • Prefer a side-by-side pane so both conversations remain visible, with a straightforward way to close the side chat and return to the main chat.
Example use case

Codex is implementing a change. I want to ask, "Why did you choose this approach?" or "Can you explain the function you just mentioned?" in a side conversation while implementation continues.

Related issues
  • #18125 — Add a way to ask side questions without affecting the main session context (closed; requested for CLI and Codex app).
  • #28186 — Render /side and /btw conversations in a TUI sidecar pane (terminal UI presentation).
  • #34498 — Show /side chats in a split pane instead of replacing the main chat (description specifies CLI).

This request specifically asks for side-conversation support in the VS Code extension, with the related issues providing context for the desired interaction.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the VS Code extension's existing chat and task-running flows, then compare the requested behavior with related issues #18125, #28186, and #34498. Define how a side conversation inherits context without steering the active task, remains visible alongside it, and can be closed; done means these interactions work while the main task continues.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.