7 people asked for
All time, since Sep 14, including 2 thumbs-up on GitHub.
Inject messages into open threads
“The automation and I need to contribute to the same conversation without forking it or quitting the desktop app.”
What gets counted gets built. Pile on.
Paste this into your agent. It files your request, with what you need it for.
I want this: rapsheet.dev/sheets/codex/issues/9187/file Follow it to file my request. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Send messages from a local process into an open desktop thread. External app-server cannot resume a thread owned by the running Desktop app; reporters want results to appear in the same already-open chat.
Is this your request?
File my request- Where
- App Server
- Error text
thread <redacted> already has an active writer- Versions
- 0.154.0 to 26.908.31748
- Platforms
- Linux, macOS, Windows
Not quite your request?
- Selected chat change events2 people
- Steer active turn externally6 people
- Wake thread on process completion4 people
Original reports5, newest first
- app-server: let local tools post to a thread the desktop app has open (and tell MCP servers their thread id)On GitHub#54683
- Feature request: event delivery into an existing local Codex Desktop chatOn GitHub Discussions#50754
- Feature request: external wake / message injection for an existing Codex Desktop or CLI sessionOn GitHub#47193
- Feature request: supported local API to enqueue messages into existing desktop Codex threadsOn GitHub Discussions#46797
- No thread works both in the panel and via CLI at the same time (writer-lock vs. panel-visibility conflict)On GitHub#45406