But all it is is a task-graph system. Each bead is task, and agents can just pick up tasks to work on... But the problem is embedding just enough context in the task that the agent can do it right. But often it doesn't, so the agent has to guess missing context. And it often produces plausible code that is wrong.

I loved Beads, but kept running into issues because it is so git heavy. One: not every system and project I work on uses git. Two: Sometimes I'd switch branches, and that would screw up Beads state entirely.

Beads keeps the issue tracker state in git. This can only work if you don’t have a PR Review-Gate to submitting patches (to file bugs issues etc) but I’ve found it unexpectedly helpful for personal projects. Helpful enough to entertain the idea in other contexts.

I highly recommend you pair it with beads from yegge: opus can lay out a large project with beads, and keep track of what to do next and churn through the list beautifully with a little help.

Bonds feels a bit busy for my taste.

I used to use Beads for all my Claude Code projects... but the other thing is Beads is a behemoth of code.