Beads:给编码智能体一个住在仓库里的轻量 issue 追踪器
Оригинальный заголовок: Beads is the next best thing to use in your workflow. Did you try it? Any tips?
Заголовок и краткое изложение на выбранном языке ожидают перевода.
Beads 为编码智能体提供一个直接放在代码仓库里的轻量 issue 追踪器,智能体可以创建、更新和关闭 beads(issue),并查询它们之间的依赖关系。
Edit:
I assumed people know about it
So to give context
Beads gives coding agents a lightweight issue tracker that lives right inside your repo. Instead of the agent losing track of tasks between sessions or scattering TODOs across random markdown files, it creates, updates and closes "beads" (issues), complete with dependencies it can actually query.
What's improved for me:
Agents remember what's left to do. When I start a new session, the agent checks what's open and picks up where it left off. I'm no longer re-explaining context every time.
Long tasks stay on track. The agent breaks bigger work into smaller issues and follows the dependency order instead of wandering off or forgetting half the plan.
No more markdown clutter. I used to end up with a pile of plan files that went stale fast. Now the work lives in one structured place.
It's just git. Everything syncs with the repo, so there's no extra service to host or account to manage.
Better visibility. I can glance at the open issues and see exactly what the agent is working on and what's blocked.
Rough edges: There's a small learning curve getting the agent to use it consistently. You'll want to mention it in your agent instructions so it becomes a habit. It's also a young project, so expect things to keep changing.
Overall it's become a regular part of my workflow, and I'd recommend giving it a try if you do a lot of multi-session work with coding agents. Happy to answer questions about how I use it.
Источник: Reddit · ClaudeCode / Codex / VibeCoding · reddit.com