335887e000
* fix(daemon): check for stale startlock before waiting 5 seconds When a previous daemon startup left behind a bd.sock.startlock file (e.g., from a crashed process), the code was waiting 5 seconds before checking if the lock was stale. This caused unnecessary delays on every bd command when the daemon wasn't running. Now checks if the PID in the startlock file is alive BEFORE waiting. If the PID is dead or unreadable, the stale lock is cleaned up immediately and lock acquisition is retried. Fixes ~5s delay when startlock file exists from crashed process. * perf: add benchmarks for large descriptions, bulk operations, and sync merge Added three new performance benchmarks to identify bottlenecks in common operations: 1. BenchmarkLargeDescription - Tests handling of 100KB+ issue descriptions - Measures string allocation/parsing overhead - Result: 3.3ms/op, 874KB/op allocation 2. BenchmarkBulkCloseIssues - Tests closing 100 issues sequentially - Measures batch write performance - Result: 1.9s total, shows write amplification 3. BenchmarkSyncMerge - Tests JSONL merge cycle with creates/updates - Simulates real sync operations (10 creates + 10 updates per iteration) - Result: 29ms/op, identifies sync bottlenecks Added BENCHMARKS.md documentation describing: - How to run benchmarks with various options - All available benchmark categories - Performance targets on M2 Pro hardware - Dataset caching strategy - CPU profiling integration - Optimization workflow This completes performance testing coverage for previously unmeasured scenarios. * docs: clarify daemon lock acquisition logic in comments Improve comments to clarify that acquireStartLock does both: 1. Immediately check for stale locks from crashed processes (avoids 5s delay) 2. If PID is alive, properly wait for legitimate daemon startup (5s timeout) No code changes - only clarified comment documentation for maintainability. --------- Co-authored-by: Steve Yegge <steve.yegge@gmail.com>
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 ⚡