Deeper worktree config options and worktree subthreads
What variant of Codex are you using?
App
What feature would you like to see?
I want to be able to find my worktrees more easily. Some things in my local dev environment are also set up to work better from a specific directory on my machine. It would be great if I could configure a global “worktree directory” where Codex creates worktrees. Bonus points if this could also be configured per project, with the global value used as the default if nothing is specified.
I’d also like to be able to open multiple threads against the same worktree. Right now, if I go to a project, talk through a plan, and then click “Fork into new worktree,” I’m effectively locked into that single thread. If that agent is busy, I can’t ask it side questions. Normally I’d just open a new thread for that, but forking into a new worktree only forks that one thread. It doesn’t promote the worktree into its own project (or something similar) that would allow multiple threads to be opened against it.
Additional information
_No response_
2 Comments
They had this before, couple weeks ago. When you were in a worktree thread, there was a button at the top to "Start a project" which would give you a kind of collapsible folder on the left for that worktree and you could open up multiple threads within that. Haven't used it for a while because I didn't need it but of course as soon as I need it today I realise it's gone. Super weird of them to just remove this very obviously useful feature, unless I've missed something please correct me.
I'm also missing the option to start a new thread on the same worktree. There's a bunch of use-cases, but the simplest one that I frequently find useful is using a new un-biased session to review the changes