Short summary of my journey towards agentic orchestration with Thurbox and Fleet.
I wanted to handle multiple Claude code sessions in parallel so I created Thurbox based on tmux, I created it way before herdr or alternatives that are nowadays very popular.
With Thurbox I could clearly increase my productivity and reduce the overhead of having multiple Claude Code sessions running in parallel for multiple project on dedicated worktrees.
Next challenge was keeping in mind and orchestrating cleanly those multiple tasks without getting confused or forgetting what I started. Having some kind of agentic ticket manager (like beads) did not work very well for me. And orchestration like Gastown seemed too complex for what I want. So I quickly realized that I needed a dedicated agent that I first called "fleet" with all the context of my project and that could create sessions and send tasks via Thurbox CLI. I have then discovered very good projects with very similar approach (like firstmate). Mine was tied to my custom setup. It was not as clean as firstmate, but it was already working very nicely with Thurbox.
That is why I started few days ago this Fleet repo, that I am planning to use on a daily basis and make evolve! Goal is not like firstmate and fit with different backends, I want to create something that perfectly match Thurbox features. Feel free to try and helping me improving it!
By the way I am still trying to add proper support for Thurbox to some popular orchestration framework (Gascity, Firstmate...)
Top comments (0)