Less than a month ago I wrote an }}">entire post explaining how to use three memory layers with Claude Code: Linear for strategy, Beads for tactics, and Tasks for execution. A nice, elegant pyramid.

Yeah, no.

Today I'm retiring Beads. Not on a whim, but because reality has made it abundantly clear that a tool causing more problems than it solves isn't a tool. It's dead weight.

What Beads Brought to the Table

For those who didn't read }}">the original post , Beads was a git-backed issue tracker. A Claude Code plugin that stored issues in JSONL files inside your repo. Brilliant idea on paper:

Git persistence : issues lived in .beads/ and got committed with your code.

Dependencies : one issue could block another.

Offline : worked without an internet connection.

The LLM could see it directly : no APIs, no configuration. The agent read the files and that was it.

The promise: an intermediate layer between "what I want to do this week" (Linear) and "what I'm doing right now" (Tasks).…