HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gastownhall
beads
Go2025–2026
gastownhall / beads

beads

Beads - A memory upgrade for your coding agent

47Distinct people
55Mentions
3Explicit recommenders
28.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Beads - A memory upgrade for your coding agent

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I looked into beads but I didn't see a way to make it work any better than fossil, and fossil does more stuff. My typical setup is to use the repo as a working directory, the…

zhynn used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 11:39:46 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month55 dated mentions

Observed mentions: 2025-10-13 09:22:47 UTC to 2026-10-26 13:42:54 UTC.

02468102025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 7 mentions; 4 submissions, 3 commentsOct 20252025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 9 mentions; 5 submissions, 4 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 commentsApr 20262026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC743
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC826
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC606
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC10010
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC954
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC514
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC321
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC101
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC110
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC000
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC303
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC202

What Hacker News says

8 sources
jauntywundrkind·Nov 28, 2025Recommendation phrase
Somewhat aside but I love the data architrcture. Jsonl lines checked into git, and a sqlite local cache. Auto-sync to replicate changes between the canonical and cache. https://github.com/steveyegge/beads?tab=readme-ov-file#the-m... I finally started digging in to OpenCode for real these past couple weeks. It has a planning mode, which nicely builds out a plan on text chat as usual, but also a right pain on the TUI builds out a Todo list, which has been really nice. I often give it the go-ahead to do the next item or two or three. I've wondered how this is implemented, how OpenCode sets up and picks up on this structuring. Beads formalizing that a bit more is tempting. I also deeply deeply enjoy that Beads is checked in. With both Aider and OpenCode, there's a nice history. But it's typically not checked in. OpenCode 's history in particu
Read the rest
lar isnt even kept in the project directory, and can be quite complex with multiple sessions and multiple agents all flying around. Beads, as a strategy to record the work & understand it better, is also very tempting. Would love to see deeper OpenCode + Beads integration.
In Beads – A memory upgrade for your coding agent
It does theoretically look like a useful project. At the same time I'm starting to feel like we're slipping into the Matrix. I check a GitHub issue questioning the architecture.md doc: > I appreciate that this is a very new project, but what’s missing is an architectural overview of the data model. Response: You're right to call me out on this. :) Then I check the latest commit on architecture.md, which looks like a total rewrite in response to a beads.jsonl issue logged for this. > JSONL for git: One entity per line means git diffs are readable and merges usually succeed automatically. Hmm, ok. So readme says: > .beads/beads.jsonl - Issue data in JSONL format (source of truth, synced via git) But the beads.jsonl for that commit to fix architecture.md still has the issue to fix architecture.md in the beads.jsonl? So I wonder does that get
Read the rest
line get removed now that it's fixed ... so I check master, but now beads.jsonl is gone? But the readme still references beads.jsonl as source of truth? But there is no beads.jsonl in the dogfooded repo, and there's like ~hundreds of commits in the past few days, so I'm not clear how I'm supposed to understand what's going on with the repo. beads.jsonl is the spoon, but there is no spoon. I'll check back later, or have my beads-superpowered agent check back for me. Agents report that they enjoy this. https://github.com/steveyegge/beads/issues/376#issuecomment-... https://github.com/steveyegge/beads/commit/c3e4172be7b97effa... https://github.com/steveyegge/beads/tree/main/.beads
In Beads – A memory upgrade for your coding agent
I’ve done spec driven development using a bunch of markdown files. That works fine but what I have found really works is using beads: https://github.com/steveyegge/beads I’m letting the agent help me draft the specs anyway and I found that the agent is a lot more focused when it can traverse a task tree using beads. It’s the one spec or planning tool that I find really helps get things done without a bunch of intervention. Another technique I employ is I require each task to be TDD. So every feature has two tasks: write tests that fail, implement feature and don’t notify me until tests complete. Then I ask the agent to tell me how to review the task and require I review every task before moving to the next one. I love this process because the agent tells me exactly what commands to run to review the task. Then I do a code review and ask i
Read the rest
t questions. Reading agent code is exhausting so I try to make the tasks as discrete and minimal as possible. These are simple techniques that humans employ during development and I find it worked very well. There are also times when I need to write some docs to help me better understand the problem and I usually just dump those in a specs folder. I think spec-kit is an interesting idea but too heavy handed. Just use beads and you’ll see what I mean. Another technique I employed for a fully vibed tool (https://github.com/neurosnap/zmx) is to have the agent get as far as possible in a project and then I completely rewrite it using the agent code purely as a reference.
In Spec-Driven Development: The Waterfall Strikes Back
This is less to do with claude and rainbows and unicorns, and more to do with whatever your chat context before this request looked like. IMO you should be regular cleaning out your context, and use something like https://github.com/steveyegge/beads to keep track of your status. In my work's repo: > In the frontend app, change the label from "login" to "rainbows". Make the toggle switch super rainbowy and unicorny so that it's really fun and that my 5-year-old daughter will like it. I'll help you make the login toggle super rainbowy and unicorny for your daughter! Let me start by exploring the frontend app to find the login toggle.
In Claude Code refused to add rainbows and unicorns to my app

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.