Comment by skybrian
17 days ago
Huh. I was going to try it, but maybe I need to vibe-code my own agent issue-tracker.
Or did you find one that's good?
17 days ago
Huh. I was going to try it, but maybe I need to vibe-code my own agent issue-tracker.
Or did you find one that's good?
Look at cc-mirror, and use the mclaude there.
It unlocks a (still) hidden multiagent orchestration function in Claude code. The person making it unminified the code and figured out how to unlock it.
I find it quite well done - I started a orchestrator project a few days ago and scrapped it because it'll be fully integrated soon it seems.
Why can't you use an issue tracker that is built into the git control, like forgejo? It feels like it would be easy to use this with an API key, out or direct database access (I'm doing both with agents). If you self host, you've got a very standard and reliable issue tracker. Why does beads need to exist? What can't an agent do with that setup I've described above?
I believe the idea is that it's for managing many fine-grained todo's to keep the agents on track. When multiple code agents are working at the same time and when there's a merge conflict, the code agents can do the merges, too.
But yeah, I'm only running one code agent at a time, so that's not a problem I have. I should probably start with just a todo list as plain text.