beads/website/versioned_docs/version-1.0.0/multi-agent/routing.md
Isaac Karrer 7f0a165f4e
feat(docs): version Docusaurus site and align llms-full with snapshots (#3033)
* feat(docs): version Docusaurus site and align llms-full with snapshots

Add docs version 1.0.0, version dropdown, lastVersion defaulting to stable,
merged markdown config, and RELEASING steps for future doc snapshots.
generate-llms-full.sh reads the latest entry in versions.json.

README links the published documentation site.

Closes #2644

Made-with: Cursor

* fix(docs): update org URLs to gastownhall and refresh 1.0.0 snapshot

- Update default orgName in docusaurus.config.ts from steveyegge to
  gastownhall to match the repo's new home
- Update hardcoded steveyegge URLs in generate-llms-full.sh
- Refresh versioned_docs 1.0.0 snapshot to include quickstart changes
  from #3032 which merged after the original snapshot was taken
- Regenerate llms-full.txt with corrected URLs and updated content

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: matt wilkie <maphew@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-06 21:12:54 -07:00

2.2 KiB

id title sidebar_position
routing Routing 2

Multi-Repo Routing

Automatic issue routing across repositories.

Overview

Routing enables:

  • Issues created in one repo routed to another
  • Pattern-based routing rules
  • Fallback to default repository

Configuration

Create .beads/routes.jsonl:

{"pattern": "frontend/**", "target": "frontend-repo", "priority": 10}
{"pattern": "backend/**", "target": "backend-repo", "priority": 10}
{"pattern": "docs/**", "target": "docs-repo", "priority": 5}
{"pattern": "*", "target": "main-repo", "priority": 0}

Route Fields

Field Description
pattern Glob pattern to match
target Target repository
priority Higher = checked first

Pattern Matching

Patterns match against:

  • Issue title
  • Labels
  • Explicit path prefix

Examples:

{"pattern": "frontend/*", "target": "frontend"}
{"pattern": "*api*", "target": "backend"}
{"pattern": "label:docs", "target": "docs-repo"}

Commands

# Show routing table
bd routes list
bd routes list --json

# Test routing
bd routes test "Fix frontend button"
bd routes test --label frontend

# Add route
bd routes add "frontend/**" --target frontend-repo --priority 10

# Remove route
bd routes remove "frontend/**"

Auto-Routing

When creating issues, beads checks routes:

bd create "Fix frontend button alignment" -t bug
# Auto-routed to frontend-repo based on title match

Override with explicit target:

bd create "Fix button" --repo backend-repo

Cross-Repo Dependencies

Track dependencies across repos:

# In frontend-repo
bd dep add bd-42 external:backend-repo/bd-100

# View cross-repo deps
bd dep tree bd-42 --cross-repo

Hydration

Pull related issues from other repos:

# Hydrate issues from related repos
bd hydrate

# Preview hydration
bd hydrate --dry-run

# Hydrate specific repo
bd hydrate --from backend-repo

Best Practices

  1. Use specific patterns - Avoid overly broad matches
  2. Set priorities - Ensure specific patterns match first
  3. Default fallback - Always have a * pattern with lowest priority
  4. Test routes - Use bd routes test before committing