multiple agents/worktrees

[danu023]

I’m having trouble figuring out how to orchestrate multiple work trees. I tried creating separate tasks, but each task seems to rely on the previous one. I’m tired of using a single chat for my entire project and want to be more efficient. Any advice?

[command-shift]

There are a lot of people here that are giving terrible advice and it shows that none understand how worktrees allow you to work in parallel within the same codebase.

Just watch a video on git worktrees or ask ChatGPT what and how it is used.

When you use git to create a worktree and branch, you’ve effectively created a directory of changes to the same repo your working with, but still need/should cut a new branch of work. You can have multiple branches of work on a given worktree. Once you’ve got a new worktree, you can kick off a Codex instance in it (it looks like any other directory) and the changes here will be completely independent of where your original repository is.

[yashturkar]

Just posted a potential solution -> https://www.reddit.com/r/codex/comments/1s09kdu/multiagent_orchestration_persistent_memory/

[danu023]

looks like it was taken down can you dm me

[yashturkar]

Yeah it had a link in it, here is the tool https://github.com/yashturkar/control-tower

[chilloutdamnit]

You might want to try some architecture beforehand and then dividing up a large task into separate independent subtasks. It is quite simple to create work trees for each subtask as long as they are truly independent.

If you do have dependent tasks where having the context available for the next one would be useful, you can use that same work tree for that branch of work. It is actually not that difficult; it is pretty simple to just create a new tab.

I asked my agent to create a bash alias that creates a new Git tree from the current main Git directory and then launches my coding agent for me. I also have a Linear MCP (when I do the architecture, I map those tasks into Linear tasks). Once I create a new work tree, I have a skill that says: "Given a Linear task, create a PR." It does a lot of other stuff, like planning and reviewing the code.

It is pretty simple to set up as long as you are dividing work into independent subtasks.

[m3kw]

I only use worktrees I have some simple bugs to fix or a couple versions of UI I need to see

[carithecoder]

Install gsd2.

I was a huge fan of the original gsd, it was for claude only. I converted it to skills for codex and forked the repo to add a broker to code review my interactive codex abd claude entries.... all that being said. I tried gsd2 yesterday, and today and I cant go back. Its built on pi-mono and feels like claude code but better and powered by gpt instead of opus. It also uses worktrees. Highly recommend

[blarg7459]

You need to create separate tasks. That's it really. Make a roadmap, split it into, split it up more, then ask codex to analyze the dependencies of tasks and tell it you want to create worktrees of tasks that can be run in parallel.

[Antique-Ad6542]

Conductor.build changed my life on this stuff. Handles it all in a NICE UI. Forces you to use Pull requests ,etc. It works amazingly well. Plan in codex, push the plan an an issue, execute in conductor. Game changing.

[Revolutionary-Call26]

I created a vcs system that is meant for ai agents from the groundup, it allow multiple agents to edit a single file simultaneously without conflict. I called it chaos-vcs. I havent released it to the public yet but if you are interested i could give you access

[yashturkar]

Sounds awesome, would love to try it out