edited the README.md intro
This commit is contained in:
14
README.md
14
README.md
@@ -1,12 +1,20 @@
|
||||
# bd - Beads Issue Tracker 🔗
|
||||
|
||||
**Issues chained together like beads.**
|
||||
**Give your coding agent a memory upgrade**
|
||||
|
||||
> **⚠️ Alpha Status**: This project is in active development. The core features work well, but expect API changes before 1.0. Use for development/internal projects first.
|
||||
|
||||
A lightweight, dependency-aware issue tracker designed for AI-supervised coding workflows. Track dependencies, find ready work, and let agents chain together tasks automatically.
|
||||
Beads is a lightweight memory system for coding agents, using a graph-based issue tracker. Four kinds of dependencies chain issues together like beads, making them easy for agents to follow for long distances.
|
||||
|
||||
## The Problem
|
||||
Drop Beads into any project where you're using a coding agent, and you'll enjoy an instant upgrade in organization, focus, and your agent's ability to handle long-horizon tasks over multiple sessions. The agent will use issue tracking instead of creating a swamp of rotten half-implemented markdown plans.
|
||||
|
||||
Beads gives agents long-term planning, solving their amnesia getting lost in nested markdown plans. And they will no longer silently pass over issues due to lack of context space -- they will file issues for newly-discovered work as they go. No more lost work, ever.
|
||||
|
||||
Beads issues are backed by git, but through a clever design it manages to act like a managed, centrally hosted SQL database shared by all of the agents working on a project (repo), even across machines.
|
||||
|
||||
Agents report that they enjoy working with Beads, and they will use it spontaneously for both recording new work and reasoning about your project in novel ways. As a human, you'll have more fun and less stress with agentic coding.
|
||||
|
||||
## The Problem Beads Solves
|
||||
|
||||
You're 200 messages deep in a coding session with your AI agent. You've discovered 12 bugs, planned 8 features, debated 3 architectural changes. The agent asks: **"What should I work on next?"**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user