remote control not working
Open
Nobody has claimed this yet.
app-server
bug
iOS
remote
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
.149
What subscription do you have?
Max
Which model were you using?
gpt 5.6 sol
What platform is your computer?
happens on mac and linux
What terminal emulator and version are you using (if applicable)?
No response
Codex doctor report
What issue are you seeing?
> Codex CLI 0.149.0; Remote Control iOS; reproduced with Linux/Omarchy and macOS hosts.
>
> 4. Close the CLI session; the same thread then loads successfully on iOS.
>
> The Remote app-server log reports:
> thread-store conflict: thread <id> already has an active writer
> followed by:
> Failed to create session
>
> Expected: Remote should at least read and display an active thread’s history without acquiring a second writer, then perform an explicit handoff if interaction requires ownership.
>
> This began approximately one week ago.
What steps can reproduce the bug?
Uploaded thread: 01a02b35-2b00-7d81-8474-25909de34719
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 with the Remote app-server flow that handles the reported thread-store conflict and failed session creation, using uploaded thread 01a02b35-2b00-7d81-8474-25909de34719 and reproducing with an active CLI session on macOS or Linux. Done means Remote can read and display an active thread's history without a second writer, then performs an explicit handoff before interaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, rust
- Domain
- distributed-systems, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100