Comment by giancarlostoro
17 days ago
What's really amazing to me is this is how I've thought about building the same thing, by using beads... Glad someone in the hivemind did it.
17 days ago
What's really amazing to me is this is how I've thought about building the same thing, by using beads... Glad someone in the hivemind did it.
> I've thought about building the same thing, by using beads... Glad someone in the hivemind did it.
Gas Town is from the creator of beads.
This makes even more sense, it definitely feels like a logical step with beads. I use Beads a lot, its one of the few things I use with Claude Code.
I had the same thought of using beads to build a multi-agent orchestrator with a defined set of workflows.
But to keep things tractable, i've kept the orchestration within a collection of subagents in a single Claude code session. The orchestration system is called Pied-Piper and you can find the code here - https://github.com/sathish316/pied-piper
It is only 1.6k Lines of Go code.
Late to the party, would love to know more of your workflow with how you're using beads.
I use Zed (this is completely optional since claude code can work 100% stand alone), Claude Code (I have Max) and Beads. I also take advantage of the .claude/instructions.md file and let Claude know to ALWAYS use Beads, and to use rg instead of "grep" which is kind of slow (if anyone from Anthropic is reading this, for the love of GOD use ripgrep instead of grep), a small summary about the project, and some ground rules. If there's key tickets that matter for the project I tell it to note them in the instructions. The instructions files the first thing Claude reads when you first open up a chat window with it, if you make amendments ask it to reread the file.
Outside of that its trial and error, but I've learned you don't need to kick off a new chat instance very much if at all. I also like Beads because if I have to "run" or go offline I can tell it to pause and log where it left off / where its at.
For some projects I tell claude not to close tickets without my direct approval because sometimes it closes them without testing, my baseline across all projects is that it compiles and runs without major errors.
Also, and I forgot this. I make them ALWAYS commit changes. Every single time, if this horrifies you, just remember you can always revert code, people need to stop getting scared of version control, use it to your full advantage.