Tasks orchestration is now broken when connected to a remote host
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.820.71523
What subscription do you have?
Pro $200
What platform is your computer?
Darwin 25.5.0 arm64 arm & Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
In the past few days orchestration of tasks via the codex desktop app is no longer working.
Up until last week, I could leave the desktop app open on Mac and connect via Windows via the app. Through Windows then, I could send messages via my main "orchestrator" task which would then prompt other "sub" tasks.
This is now no longer working. Codex says:
I prepared the bounded prompts, but they were not delivered: the Codex task-coordination service became unavailable after the remote reconnect. Desktop control is also prohibited from operating the Codex app, so I cannot safely bypass it.
Again, I'd like to highlight the fact that this was working just fine for the past few months up until last week more or less.
Now instead, I can't keep the Mac app open because when I try to access the same task via Windows, Codex will complain with something along the lines of "this conversation is open in another app..." and doesn't allow me to send prompts anymore.
Codex will sometimes try to use the CLI instead which obviously breaks the whole workflow.
What steps can reproduce the bug?
- Start an orchestration task on Mac
- Close the Mac app
- Use the desktop app via Windows remotely connected to the Mac
- Ask the orchestration task to prompt the "sub" tasks
- Observe the issue
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the five listed steps and tracing the remote reconnect and task-coordination failure, including the “conversation is open in another app” response. Compare the behavior with the prior working workflow described in the report. The issue names no files, tests, or expected behavior, so completion criteria need clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100