Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as opaque submodule gitlinks on GitHub) into fully-tracked first-party content. AITM now merges its 7 vendored repos as first-party engines: - memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts - git: vendored C git (bundled binary) + gitnexus (in-process code intelligence) - agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess) Includes the full session's product build: Gitgram web/mobile/backend features, AITM website/CLI/MCP, the unified memory layer, engine build tooling (scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md), and extensive test suites. Build artifacts, node_modules, external/, and gemini-cli are gitignored. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@beads/bd - Beads Issue Tracker
Give your coding agent a memory upgrade
Beads is a lightweight memory system for coding agents, using a graph-based issue tracker. This npm package provides easy installation of the native bd binary for Node.js environments, including Claude Code for Web.
Installation
npm install -g @beads/bd
Or as a project dependency:
npm install --save-dev @beads/bd
What is Beads?
Beads is an issue tracker designed specifically for AI coding agents. It provides:
- ✨ Zero setup -
bd initcreates project-local database - 🔗 Dependency tracking - Four dependency types (blocks, related, parent-child, discovered-from)
- 📋 Ready work detection - Automatically finds issues with no open blockers
- 🤖 Agent-friendly -
--jsonflags for programmatic integration - 📦 Version-controlled - Dolt database with full history and branching
- 🌍 Distributed by design - Share one logical database via Dolt remotes
Quick Start
After installation, initialize beads in your project:
bd init
Then tell your AI agent to use bd for task tracking instead of markdown:
echo "Use 'bd' commands for issue tracking instead of markdown TODOs" >> AGENTS.md
Your agent will automatically:
- Create and track issues during work
- Manage dependencies between tasks
- Find ready work with
bd ready - Keep long-term context across sessions
Common Commands
# Find ready work
bd ready --json
# Create an issue
bd create "Fix bug" -t bug -p 1
# Show issue details
bd show bd-a1b2
# List all issues
bd list --json
# Start work
bd update bd-a1b2 --claim
# Add dependency
bd dep add bd-f14c bd-a1b2
# Close issue
bd close bd-a1b2 --reason "Fixed"
Claude Code for Web Integration
To auto-install bd in Claude Code for Web sessions, add to your SessionStart hook:
# .claude/hooks/session-start.sh
npm install -g @beads/bd
bd init --quiet
This ensures bd is available in every new session without manual setup.
Platform Support
This package downloads the appropriate native binary for your platform:
- macOS: darwin-amd64, darwin-arm64
- Linux: linux-amd64, linux-arm64
- Windows: windows-amd64
Full Documentation
For complete documentation, see the beads GitHub repository:
- Complete README
- Quick Start (documentation site) · repo pointer
- Installation Guide
- FAQ
- Troubleshooting
Why npm Package vs WASM?
This npm package wraps the native bd binary rather than using WebAssembly because:
- ✅ Full SQLite support (no custom VFS needed)
- ✅ All features work identically to native bd
- ✅ Better performance (native vs WASM overhead)
- ✅ Simpler maintenance
License
MIT - See LICENSE for details.