f29c0e3cba
CONTRIBUTING.md: - Two tracks: humans (GitHub flow) and agents (beadboard-driver + bd) - Copy-pasteable agent instructions for quick setup - PR size guidelines (under 100 lines preferred, 200+ needs issue first) - Quality gates, claim workflow, professional conduct expectations - beadboard-driver and bd setup for agent contributors GitHub Issue templates: - Bug report: structured fields (steps, platform, Dolt status, versions) - Feature request: problem/proposal/area, opt-in to implement - Config: links to Discord and contrib:open issue filter contrib:open labels: - Tagged 4 orchestrator beads for community contribution - Left session race condition (beadboard-4v7) as internal README: - Updated banner to link to CONTRIBUTING.md - Updated Contributing section with Discord link and contrib:open workflow Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .beads.bak | ||
| archetypes | ||
| backup | ||
| dolt-backup-20260228-101523/beads | ||
| hooks | ||
| templates | ||
| .beads-credential-key | ||
| .gitignore | ||
| agent.txt | ||
| config.yaml | ||
| create_help.txt | ||
| debug.txt | ||
| dep_help.txt | ||
| dolt-config.log | ||
| dolt-server.port | ||
| dolt-sql-server.log | ||
| epic_create.txt | ||
| interactions.jsonl | ||
| issues.jsonl | ||
| issues.jsonl.bak-20260228-153309 | ||
| lint_output.txt | ||
| mem.txt | ||
| metadata.json | ||
| npm_test_output.txt | ||
| npm_test_output2.txt | ||
| npm_test_output3.txt | ||
| README.md | ||
| SESSION_NOTES.md | ||
| task1.txt | ||
| task2.txt | ||
| task3.txt | ||
| test_output.txt | ||
Beads - AI-Native Issue Tracking
Welcome to Beads! This repository uses Beads for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.
What is Beads?
Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
Learn more: github.com/steveyegge/beads
Quick Start
Essential Commands
# Create new issues
bd create "Add user authentication"
# View all issues
bd list
# View issue details
bd show <issue-id>
# Update issue status
bd update <issue-id> --status in_progress
bd update <issue-id> --status done
# Sync with git remote
bd sync
Working with Issues
Issues in Beads are:
- Git-native: Stored in
.beads/issues.jsonland synced like code - AI-friendly: CLI-first design works perfectly with AI coding agents
- Branch-aware: Issues can follow your branch workflow
- Always in sync: Auto-syncs with your commits
Why Beads?
✨ AI-Native Design
- Built specifically for AI-assisted development workflows
- CLI-first interface works seamlessly with AI coding agents
- No context switching to web UIs
🚀 Developer Focused
- Issues live in your repo, right next to your code
- Works offline, syncs when you push
- Fast, lightweight, and stays out of your way
🔧 Git Integration
- Automatic sync with git commits
- Branch-aware issue tracking
- Intelligent JSONL merge resolution
Get Started with Beads
Try Beads in your own projects:
# Install Beads
curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
# Initialize in your repo
bd init
# Create your first issue
bd create "Try out Beads"
Learn More
- Documentation: github.com/steveyegge/beads/docs
- Quick Start Guide: Run
bd quickstart - Examples: github.com/steveyegge/beads/examples
Beads: Issue tracking that moves at the speed of thought ⚡