Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix TUI-usable session-control primitive in Codex CLI [2 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#17101•Fetched 2026-04-09 08:02:26
View on GitHub
Comments
2
Participants
2
Timeline
10
Reactions
1
Author
PrathyushmnchlaPrathyushmnchla
Participants
github-actions[bot]github-actions[bot]PrathyushmnchlaPrathyushmnchla
Timeline (top)
labeled ×5unlabeled ×3commented ×2
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

Codex CLI

What feature would you like to see?

I know this overlaps with my earlier request, but this is a narrower ask and the workflow need is real for me.

My prior codex inject request (#11415) was closed as not planned.
I am not asking to revive that exact command. I am asking for the underlying capability in Codex: a native, App Server–aligned way to send/stream control messages to active sessions. If easier, this could also be done by extending MCP-trigger capabilities.

Practical context: in Claude, channel-style external messaging workflows are already usable, and I can stream inputs and adjust training hyperparameters live in a loop. OpenCode has this workflow too, so switching is a practical alternative. Otherwise, in Codex, achieving the same behavior means building a custom JSON-RPC client and reimplementing session-control plumbing outside native TUI/CLI.

Request

Please expose a first-class, TUI/CLI-usable session-control/channel primitive in Codex with functionality equivalent to the Claude channel workflow, implemented however you think is best.

I do not need a full orchestration framework—just this control path directly from TUI/CLI.

What we tried

  • Tested codex mcp-server directly.
  • codex + codex-reply works only inside the same live MCP server process.
  • thread_id from codex exec --json does not continue via codex-reply (Session not found for thread_id).
  • In Claude, the development-channel path proactively wakes the TUI session when external messages arrive.

So this request is specifically for a native Codex CLI control/wake path for active sessions.
Perhaps an MCP-server-routed external trigger could wake a waiting TUI session.

Drafted by Codex

Additional information

References

extent analysis

TL;DR

Implement a native session-control primitive in Codex CLI to send control messages to active sessions, potentially by extending MCP-trigger capabilities.

Guidance

  • Review the App Server documentation to understand the current protocol surface for thread/turn/event control and identify potential extension points.
  • Investigate the Claude channel workflow implementation to determine if similar functionality can be adapted for Codex.
  • Consider using the codex mcp-server command as a starting point for developing a native control path for active sessions.
  • Examine the release notes for rust-v0.

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…
#request error#file not found#serialization error#model compatibility#GPU setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING