Codex VSCode Extension does not work when using Cloud + Local Changes + Detached Head
Resolved 💬 3 comments Opened Sep 1, 2025 by Cidan Closed Nov 22, 2025
💡 Likely answer: A maintainer (gpeal, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
_No response_
Which model were you using?
_No response_
What platform is your computer?
_No response_
What steps can reproduce the bug?
Create a detached head state in your local git repo, set Codex to use cloud and your local changes. Codex will never kick off a cloud job, and will always fail with an error.
What is the expected behavior?
The job should kick off in the cloud.
What do you see instead?
An error banner across the top of the screen saying the job could not be started.
Additional information
_No response_
3 Comments
Can you kick off tasks from a non-detached state? I just tried and it still worked.
I can, yes, but not if the detached state is not also head.
Detached state is very common for detached workflows using tooling like Jujutsu, in which you don't deal with branches. The easiest way to test is to install and setup Jujutsu and create a commit ahead of main, then try to use that.
I think this bug is no longer relevant, so closing. If you are seeing similar behavior with the latest versions of codex, please open a new bug.