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, 10:50:02 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

9 sources
jbdamask·Feb 28, 2026Submission

Show HN: Now I Get It – Translate scientific papers into interactive webpages

Understanding scientific articles can be tough, even in your own field. Trying to comprehend articles from others? Good luck. Enter, Now I Get It! I made this app for curious people. Simply upload an article and after a few minutes you'll have an interactive web page showcasing the highlights. Generated pages are stored in the cloud and can be viewed from a gallery. Now I Get It! uses the best LLMs out there, which means the app will improve as AI improves. Free for now - it's capped at 20 articles per day so I don't burn cash. A few things I (and maybe you will) find interesting: * This is a pure convenience app. I could just as well use a saved prompt in Claude, but sometimes it's nice to have a niche-focused app. It's just cognitively easier, IMO. * The app was built for myself and colleagues in various scientific fields. It can take a
Read the rest
n hour or more to read a detailed paper so this is like an on-ramp. * The app is a place for me to experiment with using LLMs to translate scientific articles into software. The space is pregnant with possibilities. * Everything in the app is the result of agentic engineering, e.g. plans, specs, tasks, execution loops. I swear by Beads (https://github.com/steveyegge/beads) by Yegge and also make heavy use of Beads Viewer (https://news.ycombinator.com/item?id=46314423) and Destructive Command Guard (https://news.ycombinator.com/item?id=46835674) by Jeffrey Emanuel. * I'm an AWS fan and have been impressed by Opus' ability to write good CFN. It still needs a bunch of guidance around distributed architecture but way better than last year.
305 points · Open discussion
juanre·Feb 21, 2026Submission

Show HN: Beadhub.ai – Real time coord for coding agents across different minders

Beads[1] (Steve Yegge's git-native issue tracking for agents) has been a great boost to my agents' productivity, but it's also made them more difficult to keep aligned. So I built BeadHub, a coordination layer on top of beads. The Go CLI (bdh) wraps the beads bd client transparently: your existing beads workflows keep working, and coordination is added automatically: - Agent-to-agent sync chat and async mail. - Claim detection with conflict rejection: agent A claims a task; if agent B tries to claim the same, bdh rejects it with a message explaining why. - Automatic file reservations: when a file is modified, all agents know it. - Live dashboard showing who's working on what, in real time. We use BeadHub to build BeadHub. Public dashboard: https://app.beadhub.ai/juanre/beadhub/ The agents-chatting-with-each-other part feels almost magical
Read the rest
. The agents negotiate task splits and API contracts, warn each other about breaking changes, and generally sort things out themselves. They also greatly improve coordination among the human team members, because they can handle the details in real time without involving their minders. Everything is open source (MIT). Self-host the full stack, or use the hosted version at https://beadhub.ai. Self-host everything with Docker: git clone https://github.com/beadhub/beadhub.git cd beadhub && make start # then in your repo: bdh :init --beadhub-url http://localhost:8000 --project my-project What doesn't work yet: agents can't be woken externally, so they need prodding to check their mail and incoming chats. In Claude Code, hooks trigger this automatically so latency is low. Other agents need reminding. Server and dashboard: https://github.com/beadhub/beadhub CLI: https://github.com/beadhub/bdh [1]: https://github.com/steveyegge/beads
2 points · Open discussion
juanre·Feb 20, 2026Submission

Show HN: I made a tool for Claude Code and Codex agents to work as teams

When I started using Beads [1] (Steve Yegge's git-native issue tracking for agents) my agents' productivity improved a lot. It also became clear that Beads is a great scaffold for agents to coordinate around, even when working for different human minders. So I built BeadHub, an OSS coordination layer on top of Beads. The Go CLI (bdh) wraps the beads bd client transparently: your existing beads workflows keep working, and coordination is added automatically. - Agent-to-agent chat and mail: agents message each other ("I'm refactoring auth, hold off on the login endpoint"). - Claim detection with conflict rejection: agent A sets a task to in-progress; if agent B tries the same, bdh rejects it with a message explaining why. - Automatic file reservations: when a file is modified, all agents know it. - Live dashboard showing who's working on wh
Read the rest
at, in real time. The agents-chatting-with-each-other part feels almost magical. The agents negotiate task splits and API contracts, warn each other about breaking changes, and generally sort things out themselves. They also greatly improve coordination among the human team members, because the agents can handle the details in real time without involving their minders. We use BeadHub to build BeadHub. Public dashboard: https://app.beadhub.ai/juanre/beadhub/ Try it — managed (no server setup): brew install beads curl -fsSL https://raw.githubusercontent.com/beadhub/bdh/main/install.sh | bash bdh :init --email you@example.com --project my-project bdh ready Or self-host everything with Docker: git clone https://github.com/beadhub/beadhub.git cd beadhub && make start # then in your repo: bdh :init --beadhub-url http://localhost:8000 --project my-project Everything is open source (MIT). Self-host the full stack, or use the hosted version at https://beadhub.ai — no signup required to browse the dashboard. bdh works with any agent that can run CLI commands. We use it with Claude Code (hooks make notifications automatic), but there's nothing Claude-specific about the protocol. Known limitation: agents can't be woken externally — they check for messages on every tool call. In Claude Code, hooks trigger this automatically so latency is seconds. Other agents may poll less frequently. Source: https://github.com/beadhub/beadhub CLI: https://github.com/beadhub/bdh [1]: https://github.com/steveyegge/beads
1 points · Open discussion
My experience is that Codex follows directions better but Claude writes better code. ChatGPT-5.2-Codex follows directions to ensure a task [bead](https://github.com/steveyegge/beads) is opened before starting a task and to keep it updated almost to a fault. Claude-Opus-4.5 with the exact same directions, forgets about it within a round or two. Similarly, I had a project that required very specific behaviour from a couple functions, it was documented in a few places including comments at the top and bottom of the function. Codex was very careful in ensuring the function worked as was documented. Claude decided it was easier to do the exact opposite, rewrote the function, the comments, and the documentation to saynit now did the opposite of what was previously there. If I believed a LLM could be spiteful, I would've believed it on that seco
Read the rest
nd one. I certainly felt some after I realised what it had done. The comment literally said: // Invariant regardless of the value of X, this function cannot return Y And it turned it into: // Returns Y if X is true
In Claude Opus 4.6
dsifry·Feb 3, 2026Submission

Show HN: Metaswarm: Production-ready agent swarms, MIT license

A few weeks ago I posted about GoodToGo https://news.ycombinator.com/item?id=46656759 - a tool that gives AI agents a deterministic answer to "is this PR ready to merge?" Several people asked about the larger orchestration system I mentioned. This is that system. I got tired of being a project manager for Claude Code. It writes code fine, but shipping production code is seven or eight jobs — research, planning, design review, implementation, code review, security audit, PR creation, CI babysitting. I was doing all the coordination myself. The agent typed fast. I was still the bottleneck. What I really needed was an orchestrator of orchestrators - swarms of swarms of agents with deterministic quality checks. So I built metaswarm. It breaks work into phases and assigns each to a specialist swarm orchestrator. It manages handoffs and uses BE
Read the rest
ADS for deterministic gates that persist across /compact, /clear, and even across sessions. Point it at a GitHub issue or brainstorm with it (it uses Superpowers to ask clarifying questions) and it creates epics, tasks, and dependencies, then runs the full pipeline to a merged PR - including outside code review like CodeRabbit, Greptile, and Bugbot. The thing that surprised me most was the design review gate. Five agents — PM, Architect, Designer, Security, CTO — review every plan in parallel before a line of code gets written. All five must approve. Three rounds max, then it escalates to a human. I expected a rubber stamp. It catches real design problems, dependency issues, security gaps. This weekend I pointed it at my backlog. 127 PRs merged. Every one hit 100% test coverage. No human wrote code, reviewed code, or clicked merge. OK, I guided it a bit, mostly helping with plans for some of the epics. A few learnings: Agent checklists are theater. Agents skipped coverage checks, misread thresholds, or decided they didn't apply. Prompts alone weren't enough. The fix was deterministic gates — BEADS, pre-push hooks, CI jobs all on top of the agent completion check. The gates block bad code whether or not the agent cooperates. The agents are just markdown files. No custom runtime, no server, and while I built it on TypeScript, the agents are language-agnostic. You can read all of them, edit them, add your own. It self-reflects too. After every merged PR, the system extracts patterns, gotchas, and decisions into a JSONL knowledge base. Agents only load entries relevant to the files they're touching. The more it ships, the fewer mistakes it makes. It learns as it goes. metaswarm stands on two projects: https://github.com/steveyegge/beads by Steve Yegge (git-native task tracking and knowledge priming) and https://github.com/obra/superpowers by Jesse Vincent (disciplined agentic workflows — TDD, brainstorming, systematic debugging). Both were essential. Background: I founded Technorati, Linuxcare, and Warmstart; tech exec at Lyft and Reddit. I built metaswarm because I needed autonomous agents that could ship to a production codebase with the same standards I'd hold a human team to. $ cd my-project-name $ npx metaswarm init MIT licensed. IANAL. YMMV. Issues/PRs welcome!
1 points · Open discussion
dsifry·Feb 3, 2026Submission

Show HN: 127 PRs to Prod this wknd with 18 AI agents: metaswarm. MIT licensed

A few weeks ago I posted about GoodToGo https://news.ycombinator.com/item?id=46656759 - a tool that gives AI agents a deterministic answer to "is this PR ready to merge?" Several people asked about the larger orchestration system I mentioned. This is that system. I got tired of being a project manager for Claude Code. It writes code fine, but shipping production code is seven or eight jobs — research, planning, design review, implementation, code review, security audit, PR creation, CI babysitting. I was doing all the coordination myself. The agent typed fast. I was still the bottleneck. What I really needed was an orchestrator of orchestrators - swarms of swarms of agents with deterministic quality checks. So I built metaswarm. It breaks work into phases and assigns each to a specialist swarm orchestrator. It manages handoffs and uses BE
Read the rest
ADS for deterministic gates that persist across /compact, /clear, and even across sessions. Point it at a GitHub issue or brainstorm with it (it uses Superpowers to ask clarifying questions) and it creates epics, tasks, and dependencies, then runs the full pipeline to a merged PR - including outside code review like CodeRabbit, Greptile, and Bugbot. The thing that surprised me most was the design review gate. Five agents — PM, Architect, Designer, Security, CTO — review every plan in parallel before a line of code gets written. All five must approve. Three rounds max, then it escalates to a human. I expected a rubber stamp. It catches real design problems, dependency issues, security gaps. This weekend I pointed it at my backlog. 127 PRs merged. Every one hit 100% test coverage. No human wrote code, reviewed code, or clicked merge. OK, I guided it a bit, mostly helping with plans for some of the epics. A few learnings: Agent checklists are theater. Agents skipped coverage checks, misread thresholds, or decided they didn't apply. Prompts alone weren't enough. The fix was deterministic gates — BEADS, pre-push hooks, CI jobs all on top of the agent completion check. The gates block bad code whether or not the agent cooperates. The agents are just markdown files. No custom runtime, no server, and while I built it on TypeScript, the agents are language-agnostic. You can read all of them, edit them, add your own. It self-reflects too. After every merged PR, the system extracts patterns, gotchas, and decisions into a JSONL knowledge base. Agents only load entries relevant to the files they're touching. The more it ships, the fewer mistakes it makes. It learns as it goes. metaswarm stands on two projects: https://github.com/steveyegge/beads by Steve Yegge (git-native task tracking and knowledge priming) and https://github.com/obra/superpowers by Jesse Vincent (disciplined agentic workflows — TDD, brainstorming, systematic debugging). Both were essential. Background: I founded Technorati, Linuxcare, and Warmstart; tech exec at Lyft and Reddit. I built metaswarm because I needed autonomous agents that could ship to a production codebase with the same standards I'd hold a human team to. $ cd my-project-name $ npx metaswarm init MIT licensed. IANAL. YMMV. Issues/PRs welcome!
5 points · Open discussion

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.