Happy belated first birthday to Beads!

Beads was introduced on Oct 13, 2025 in a blog article by its creator Steve Yegge. Beads is the original agentic memory tool. You tell your coding agents to use Beads for task management and they work for longer…since Oct 2025, which is 2,700 AI years.

Beads was the forebear to Gas Town, which became Gas City. Gas Town was the original software factory, another category that now has a lot of imitators, similar to agentic memory. Steve didn’t just create tools. He created categories. Beads and Gas City now have a real company behind them called Gas City Inc.

If you’re not familiar with Beads, let me catch you up and explain why it is unique, including how Dolt is involved. My hope is you’ll try Beads and become a Beads (and thus, Dolt) user.

What is Beads?#

From my initial article on Beads and Gas Town, my first paragraph summary still holds:

Beads is a command line tool, bd, coding agents use to manage tasks. Beads stores tasks as issues in a .beads directory in your project folder. You tell your coding agent to use Beads to manage its tasks, and voila, your coding agent will start to be able to accomplish longer tasks and remember things.

Steve’s very early insight was that coding agents work better and for longer when their task lists are managed and persisted outside of context. Beads is the result of that insight. Beads is cited as inspiration in the launch announcement of Claude Code tasks.

It was clear we needed to evolve Todos to help Claude work on longer projects. This need was also emerging in the community and we took inspiration from projects like Beads by Steve Yegge.

The agentic memory category now has dozens, if not hundreds, of players. Beads is the OG, the project that launched a thousand ships.

How is Dolt Involved?#

Beads adopted Dolt in early 2026 as its primary store. Dolt replaced a fragile SQLite + JSONL export system that provided sharing and versioning capabilities via Git. Dolt made version control and sharing first-class primitives in the Beads system.

One of Steve’s agentic engineering superpowers is to watch the tool calls agents are making.

The complicated Beads CLI isn’t for humans; it’s for agents. What I did was make their hallucinations real, over and over, by implementing whatever I saw the agents trying to do with Beads, until nearly every guess by an agent is now correct.

Steve noticed agents inspecting the JSONL Git history to resolve issues in Gas Town. From this, Steve concluded Beads needed versioning as a first-class concept in the system. But, the SQLite to JSONL export and import meant synchronizing two distinct systems of record. Dolt delivered both SQL and Git-style versioning in a single system of record, a logical, superior replacement.

Moreover, the JSONL checked into Git meant that pushing your project to a Git remote like GitHub also meant pushing your Beads. Git remotes allowed you to share Beads between computers or users. Dolt always supported remotes like DoltHub, but that requires separate authentication. Despite the permissions challenges, there are lots of Beads databases on DoltHub. Steve requested Dolt support Git remotes to keep the “Beads classic workflow” where no additional authentication beyond GitHub credentials was required. We delivered. You can now share fully versioned Beads via GitHub, DoltHub, or a live Dolt server.

Dolt is an essential piece of what makes Beads special.

What Else Makes Beads Special?#

Dolt isn’t the only thing that makes Beads special. Here are some of my favorite non-Dolt aspects of Beads.

Easy to Use#

Beads has a two-step setup process. You download it with NPM or Homebrew and add one line in your AGENTS.md.

This project uses bd (beads) for issue tracking.

After this, you’ll start to notice your agents working for longer and delivering better work.

You can start to add more complicated workflows later. But those two simple steps are all it takes to start getting value from Beads immediately.

For Agents, By Agents#

Beads pioneered the “for agents by agents” category, as noted in Steve’s quote above. “The complicated Beads CLI isn’t for humans; it’s for agents”. Beads is still proudly engineered by agents.

The Gas City team continues pushing the envelope on what is possible with coding agents. Beads now has a named agent maintainer, Bee, who plans tasks using, you guessed it, Beads!

If you’re looking for inspiration on how to deploy agents within your organization to get more done, look no further than Beads (and Gas City). This team is always on the cutting edge.

Active Community#

The Beads project has always been a very accepting open source project where agent-generated PRs are encouraged. If you’re trying to learn agentic engineering outside of your stodgy, “no agents here” company, Beads is a great place to get your first agent-engineered PR accepted. The community gathers on the Gas City Discord. You’ll even find me there from time to time.

Conclusion#

In October 2025, Beads was groundbreaking. Now, it’s the foundation of (gas) cities. What a difference a year makes! Congratulations to Steve and the Gas City team. Try Beads today and let me know what you think. You can find me on our Discord or Gas City’s.