beads vs bemyagent
Distributed graph issue tracker for coding agents on Dolt: dependency-aware beads replace markdown plans — bd ready/claim/close, cell-level merge, push/pull across machines and agents. CLI + MCP. — versus — One markdown bootstrap file that scaffolds a structured workspace for any coding agent — persistent project docs plus a task tree run through a Think→Task→Execute→Verify cycle with human pacing gates.
bemyagent bootstraps a markdown task tree in one file; beads replaces exactly that with a dependency-aware tracker once parallel agents start stepping on each other.
| beads | bemyagent | |
|---|---|---|
| Stars | 26k | 22 |
| Forks | 1.7k | 6 |
| Language | Go | HTML |
| License | MIT | MIT |
| Last activity | yesterday | 28 days ago |
| Topics | coding, memory | coding, memory |
| Curated connections | 2 | 6 |
beads — the curator's take
Steve Yegge's answer to agents drowning in markdown TODOs: task state as a versioned database with real merge semantics, so parallel agents claim and release work without trampling each other — the dependency graph decides what's 'ready'. When NOT: solo short-horizon sessions — bd init plus a Dolt store is infrastructure, and if tasks finish in one sitting a todo list wins. Note it remembers WORK, not knowledge — recall memory is a different shelf.
bemyagent — the curator's take
Try it when your agent keeps drifting on multi-session projects and a flat CLAUDE.md isn't enough structure: one file bootstraps a disciplined docs+work tree, it's agent-agnostic (self-registers into .cursorrules/AGENTS.md), and INTERACTIVE mode gives you real plan/result approval gates. NOT for quick scripts or single-session work — the ceremony outweighs the benefit — and it's a young one-maintainer protocol: no enforcement layer exists, so compliance depends entirely on the model faithfully following a long ruleset; weaker models will ignore half of it. Expect to adapt conventions yourself rather than lean on tooling or community.