(2026-01-26) From Beads To Tasks Anthropic Productizes Agent Memory

From Beads to Tasks: Anthropic Productizes Agent Memory. An Anthropic engineer tweeted about the new task system in Claude Code v2.1.16: "We took inspiration from projects like Beads by Steve Yegge." — Antoine Brugeat, Anthropic

The community builds patterns. Anthropic productizes them. The pattern-to-product cycle continues

Why Todos Weren’t Enough

Claude Code has had todos since forever. Opus 4.5 is good enough at tracking state that simple todos became redundant for small tasks.
But projects got longer. Multi-session work. Subagents. Context window boundaries. The problem shifted from “what do I need to do” to “how do I coordinate complex work across sessions and agents.”

Todos don’t solve that. You need:

• Dependencies - task A blocks task B
• Persistence - survives session boundaries
• Coordination - multiple agents, same source of truth
• That’s what Beads solved. Now it’s what Tasks solves, built in.

What Tasks Actually Does

From the changelog: “Added new task management system, including new capabilities like dependency tracking

The CLAUDE_CODE_TASK_LIST_ID environment variable opts you into persistence and coordination. Without it, each session is isolated. With it, tasks persist to ~/.claude/tasks/<id>/ and multiple terminals see the same state.
This isn’t a Jira replacement. It’s session-level coordination for agentic workflows.

The Pattern Recognition

Different Layers, Not Competition

The honest take: Tasks doesn’t obsolete Beads or Flux. They solve different layers.

• Tasks: Session-level
• Beads: Project-levelGit
• Flux: Team-level (kan-ban board)

Analogy: Tasks is SQLite. Beads/Flux are PostgreSQL. Different scale, both valid.
If you’re coordinating work within a Claude Code session or across a few terminals: Tasks.
If you need project memory that survives across weeks and works with multiple agents: Beads.
If you need team-level visibility with a web dashboard: Flux.

Caveats

The “yet” qualifiers are intentional. This is v1. Anthropic ships fast.

The Moat Question

A friend sent me this today: Claude proactively offering to save a task for later. “Want me to add that now, or create a task for later?”
It’s in the system prompt now. That changes everything.

The real moat is the non-CLI human experience: IDEs, web UIs, dashboards, integrations that aren’t just Claude in a terminal.

Why This Matters

The CNC machine is taking shape.

Try It