Realtime Voice from SSH remote project falls back to local/projectless session
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.818.31338
What subscription do you have?
Pro
What platform is your computer?
Linux 6.8.0-101-generic x86_64 x86_64
What issue are you seeing?
I'm using the Codex App on Ubuntu and connecting over SSH to a remote Ubuntu LXC container.
I open a project located inside the remote Ubuntu LXC container. The project is correctly shown as a remote project with the globe/remote indicator.
When I start Realtime Voice from this remote project, the new Voice conversation no longer stays attached to the SSH remote project. Instead, it falls back to a non-remote/projectless session and the globe/remote indicator disappears.
This is a regression. The exact same workflow was working correctly approximately 4 days ago with the same setup.
There is no visible error message. The Voice session silently loses the remote project/host association when it is created.
The remote target is an Ubuntu LXC container running Codex CLI version 149.
What steps can reproduce the bug?
- Run the Codex App on Ubuntu.
- Connect over SSH to an Ubuntu LXC container.
- Open a project located inside the remote container.
- Verify that the project is recognized as remote and shows the globe/remote indicator.
- Start Realtime Voice while this remote project is selected.
- Observe the newly created Voice conversation.
Actual result:
The Voice conversation opens as a non-remote/projectless session. The remote project association and globe/remote indicator are lost.
This happens consistently for me now.
The exact same procedure was working correctly approximately 4 days ago.
No code snippet is required because the issue occurs directly in the Codex App UI when starting Realtime Voice from an SSH remote project.
What is the expected behavior?
Starting Realtime Voice from an SSH remote project should preserve the currently selected remote project and SSH host.
The Voice conversation should remain associated with the same project inside the remote Ubuntu LXC container and continue showing the remote/globe indicator, as it did previously.
Additional information
Local machine:
- Ubuntu
- Codex App version: 26.818.31338
- Kernel: Linux 6.8.0-101-generic x86_64 x86_64
Remote environment:
- Ubuntu LXC container
- Connected over SSH
- Codex CLI version: 149
The affected project is located inside the remote Ubuntu LXC container.
Normal SSH remote project sessions work correctly. The regression happens specifically when starting Realtime Voice from the selected remote project.
This exact workflow was working correctly approximately 4 days ago.
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
Begin at the Codex App's Realtime Voice launch path for a selected SSH remote project and reproduce the workflow against the Ubuntu LXC container described in the report. No files or tests are named; trace how the selected project and SSH host are passed into the new Voice conversation. Done means the conversation remains attached to the remote project and retains the globe indicator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust, ubuntu
- Domain
- cli, desktop, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100