Regression: “Save as project” button missing (worktree management workflow)
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.217.1959 (669)
What subscription do you have?
Plus
What platform is your computer?
Darwin 24.5.0 arm64 arm
What issue are you seeing?
The “Save as project” action (the button with the tooltip “Save as a project so you can start new threads from this worktree”) is no longer visible in the Codex app.
I used this feature constantly because it makes worktree management fast and frictionless. Losing it adds several manual steps every time I spin up a new worktree.
This feature is described in the docs here: https://developers.openai.com/codex/app/worktrees#adding-a-worktree-to-the-sidebar
Why this matters
The Codex app is built around agent management. In practice, worktree management is essential to that experience. The missing button removes a core shortcut and adds a lot of friction to a frequent workflow.
Workaround (current manual flow)
Now I have to do this repeatedly:
- Hover over the thread name to get the worktree folder name (it’s a random 5-character ID).
- Click Open project.
- Browse to and open the worktree folder.
- Rename the folder in the sidebar to match the branch name.
This is frustrating.
Before, it was a single click, and the saved project/folder would already be named after the branch.
What steps can reproduce the bug?
- Open the Codex app.
- Start a new thread that creates a new worktree.
- Click "Create branch here".
- Look for the “Save as project” button in the header/top bar.
- Notice it isnt present.
What is the expected behavior?
After following the steps above, the “Save as project” button is available in the thread/worktree header.
<img width="1190" height="200" alt="Image" src="https://github.com/user-attachments/assets/ac656129-1762-4031-aae7-def606557076" />
Clicking it saves/creates the project entry for that worktree and automatically uses the created branch name so the project list stays organized.
Additional information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗