Back
47/65
Lesson 47
8 min
BV: Graph-Aware Triage
Analyze issue dependencies with graph metrics and robot mode
Ready to level up?
Mark complete to track your learning progress.
Analyze issue dependencies with graph metrics and robot mode
Mark complete to track your learning progress.
Use BV to triage issues with graph-aware intelligence and coordinate multi-agent work through robot mode.
BV (Beads Viewer) is a high-performance Terminal UI for browsing, triaging, and analyzing issues tracked by the Beads system. While br manages the issue data, BV is your intelligence layer — computing dependency graphs, identifying bottlenecks, and giving AI agents structured triage recommendations.
BV computes 9+ graph metrics over your issue dependency graph, including PageRank, betweenness centrality, HITS scores, eigenvector centrality, and k-core decomposition. It uses these to surface the highest-impact work items automatically.
PageRank, betweenness, HITS, eigenvector, k-core
40+ flags for AI agent automation
Split-view Kanban with live reload
Baseline snapshots with threshold alerts
Click "Run Triage" to compute graph metrics and see recommendations
The --robot-triage flag is BV's mega-command. It runs a two-phase analysis — first computing graph metrics, then combining them with status, age, and blocking relationships to produce a prioritized list of what to work on next.
# Full triage with all metrics (the main entry point)bv --robot-triage# Just get the single top recommendationbv --robot-next# Triage grouped by label (for multi-agent workload splitting)bv --robot-triage-by-label# Triage grouped by trackbv --robot-triage-by-track# Scope triage to a specific labelbv --robot-triage --label "backend"
bv --robot-triage as your starting point — never run bare bv from an agent. The robot flags produce structured JSON that agents can parse directly.BV builds a full dependency graph from your issues and computes metrics used by real-world network analysis. These reveal which issues are true bottlenecks versus just noisy.
BV connects issues to source files, letting you assess the blast radius of changes and plan sprints with realistic capacity.
# Which beads touch this file?bv --robot-file-beads src/auth/login.ts# What's the blast radius of changing these files?bv --robot-impact src/api/routes.ts,src/db/schema.ts# Full impact network analysisbv --robot-impact-network# Code hotspots (files with the most linked issues)bv --robot-file-hotspots# Sprint capacity planningbv --robot-capacity --agents=3# Forecast completion ETAsbv --robot-forecast
BV can snapshot your project's health metrics and detect when things drift outside thresholds — useful for CI alerts or periodic health checks.
# Proactive alerts (drift + anomalies)bv --robot-alerts# Detect drift from baselinebv --robot-drift# Performance and cache metricsbv --robot-metrics# Diff since a git ref (time-travel)bv --robot-diff --since HEAD~5# View historical statebv --as-of v1.0.0# Label health (velocity, staleness, cascade effects)bv --robot-label-health
bv --robot-alerts in a cron job or CI step. Exit code 0 means healthy, 1 means drifted, 2 means critical — perfect for automated monitoring.BR manages issue data, BV analyzes it with graph intelligence
Use triage-by-label to assign work across spawned agents
Search past sessions for context on high-priority beads
Coordinate triage decisions across concurrent agents