https://paddo.dev/blog/from-beads-to-tasks/
-
takes inspo from Beads by Steve Yegge
-
Claude code had to-dos. It wasn’t enough for longer projects. Problem of coordinating complex work across sessions and agents. you need
- dependencies (what task blocks another?)
- persistence
- coordination (multiple agents, same source of truth)
tasks
-
built into claude code, session-level scope (beads is project-level, integrates with any agent that reads files) - diff scale, solves a diff problem than beads
-
task management system with dependency tracking
-
tasks live in
~/.claude/tasks -
updates broadcast to all sessions watching the same task list
-
env var identifies task list to watch
-
Intended for coordinating work within a session or across a few terminals.
-
CLI tooling has no moat. Any good pattern that fits in a system prompt becomes native - real moat is non-CLI human experience: IDEs, web UIs, dashboards