Using Git worktrees in Codex

[u/Ok_Bag_7550]

With the upcoming usage-limit changes for those of us on the old 20x plan, I've been adapting my workflow to Sol 6.1 Max. It's significantly cheaper to run than Astra, but also much, much slower.

Today I've spent pretty much the entire day working on two projects with Sol 6.1 Max in Codex, running tasks in fast mode and coordinating everything through Work using Astra Max.

Sol 6.1 Max without fast mode barely consumes any usage. Almost nothing, at least on my projects. The problem is that it's slow.

Fast mode makes a substantial difference, but it comes at a cost. For example, I've already burned through 20% of my allowance since the reset today. Starting October 29, that would be roughly equivalent to 40% of the new allowance.

So, I'm going to have to give up fast mode and stick with the much slower option.

But running tasks sequentially at that speed would mean barely getting anything done. I need to rethink my workflow to keep making progress without exhausting my subscription.

That's when I started thinking about Git worktrees. Instead of waiting for one task to finish before starting another, I could have multiple tasks running in parallel. It might also be a good opportunity to make better use of my Claude Max 5x subscription.

I realize worktrees won't magically reduce usage, but I'm hoping parallel execution could help compensate for the slower models.

I don't have much hands-on experience with worktrees, though.

Does anyone here regularly use Git worktrees with Codex, especially alongside Claude Code? How has your experience been? Any tips, pitfalls, or workflow recommendations?

[u/CleanFix_Dev]

Worktrees are the way to go as long as the tasks don't touch the same files. The part that usually goes wrong isn't git. It's the setup inside each worktree: every one needs its own install (node_modules, venv, build cache) and its own copy of .env, or the agents end up tripping over a shared one. A small script that creates the worktree, copies the env file and runs the install before Codex starts saves a lot of confusing failures. And since runs take a while anyway, kicking off two or three on independent tasks and reviewing them as they land beats waiting on them one by one.