After having to do a ton of git stashing and branch fumbling, I decided I needed to something to more ergonomically run these agents in their own dedicated spaces.
I tried a lot of the existing products but they either were too convoluted or flat out didn't work. Some of them also seem to roll their own chat UI which I don't think is the right approach, I wanted to something to lightly wrap my terminal sessions.
So I built FleetCode! It uses git worktrees and let's you run multiple agents at once. It's made my multi agent coding workflow much easier.
It's free and open source, would love some feedback!
Then we wouldn't need our Kanban board AND a separate board for just that.
Or I guess if these tools integrated into JIRA and suggested tickets, that could be nice.
* Agent UI is the CLI itself, no wrapper UI.
* Isolate your work with worktrees (though we do our best to make sure you never have to think about them!)
* Many agents to choose from (Claude, Codex, Gemini, Amp, etc), and more to come!
* Features to support running your app in parallel (port vars, untracked file copying).
* Basics like code editor, git commit UI, branch diff UI.
* Easy access to your local IDE from the worktree.
* Soft launch of our Jira integration if you click on the repository name in the sidebar and click “Jira”, start your agents quickly right from a backlog-esque view of your work! (Next release will integrate Jira into onboarding)
Say hi on our discord too! https://discord.gg/devswarm
We’ve been building DevSwarm with DevSwarm and building like this is just unreal. Honestly can't imagine building any other way now.
edit: Oh forgot to mention we're in free-beta right now, so please download it and tell us what you think!
Do let us know if you tried out DevSwarm.ai and if you found something missing. We built it for the same reason.
And kudos to any of us on this thread that see where coding is going! We call it high velocity engineering, or hive coding, as the code matters.
* create a dev container for the project
* install the agent (Claude Code in my case) in the container as part of the dev container definition
* launch the container through DevPod (no affiliation) which automatically connects VS code or a JetBrains agent
So now I can run these in parallel, on a remote server if I want, and in "YOLO" mode. Personally, I'm finding this superior to the git worktree alternative.
It is based off Shopify CEO Tobi's `try` implementation[1].
[0]: https://github.com/aperoc/toolkami [1]: https://github.com/tobi/try
https://github.com/stravu/crystal
Did you use TypeScript to build FleetCode because of electron app?
Dagger has a nice solution for this in this space called Container Use - https://container-use.com/introduction
It does git worktree based parallelisation as well.
Edit: Ah! I see you mentioned several tools. Sorry I saw the repo and immediately thought of container use as I have been planning to give it a go this week. Did you happen to try it too? And where did it breakdown?
GitButler does this cool thing where you can work on multiple branches at the same time, applied to the same working directory. For example you can work on the css while an agent works on the admin panel on a separate branch. It would be cool to have this with a tool like FleetCode.
But it was just a bit too much cognitive dissonance for me to try it.
It seems like the next big thing is parallel coding... I've tried GitButler, Spectator, Vibe-Kanban, and Conductor in the past week. And there is now FleetCode.
I liked Spectator's idea (use a separate docker container for each) but it didn't quite work right. So back to worktrees which seem to work just fine.
At some point, we will probably consolidate on 2-3 dominant tools in this space.
I wonder if even work trees will be needed if we can do a "create a copy-on-write version of my code folder" which would result in nearly zero-cost copies of the repo.
I do not use it collaboratively. I use it to continuously ship smaller things while working on bigger pieces and I constantly move independent changes around to different “lanes” to ship frequently as parts of my work mature.
With Magit I used staging area and amended commits continuously. With GitButler I “assign” files or chunks by dragging them into lanes as I am happy with the changes, and when I have a logical unit I commit it. Having this multiple staging areas has been a great workflow improvement as well.