e7f532db93
* bd sync: 2025-10-30 12:12:27 * Working on frontend * bd sync: 2025-11-06 16:55:55 * feat: finish bd monitor human viewer * Merge conflicts resolved and added tests * bd sync: 2025-11-06 17:23:41 * bd sync: 2025-11-06 17:34:52 * feat: Add reload button and multiselect status filter to monitor - Changed status filter from single select to multiselect with 'Open' selected by default - Added reload button with visual feedback (hover/active states) - Updated filterIssues() to handle multiple selected statuses - Added reloadData() function that reloads both stats and issues - Improved responsive design for mobile devices - Filter controls now use flexbox layout with better spacing * fix: Update monitor statistics to show Total, In Progress, Open, Closed - Replaced 'Ready to Work' stat with 'In Progress' stat - Reordered stats to show logical progression: Total -> In Progress -> Open -> Closed - Updated loadStats() to fetch in-progress count from stats API - Removed unnecessary separate API call for ready count * fix: Correct API field names in monitor stats JavaScript The JavaScript was using incorrect field names (stats.total, stats.by_status) that don't match the actual types.Statistics struct which uses flat fields with underscores (total_issues, in_progress_issues, etc). Fixed by updating loadStats() to use correct field names: - stats.total -> stats.total_issues - stats.by_status?.['in-progress'] -> stats.in_progress_issues - stats.by_status?.open -> stats.open_issues - stats.by_status?.closed -> stats.closed_issues Fixes beads-9 * bd sync: 2025-11-06 17:51:24 * bd sync: 2025-11-06 17:56:09 * fix: Make monitor require daemon to prevent SQLite locking Implemented Option 1 from beads-eel: monitor now requires daemon and never opens direct SQLite connection. Changes: - Added 'monitor' to noDbCommands list in main.go to skip normal DB initialization - Added validateDaemonForMonitor() PreRun function that: - Finds database path using beads.FindDatabasePath() - Validates daemon is running and healthy - Fails gracefully with clear error message if no daemon - Only uses RPC connection, never opens SQLite directly Benefits: - Eliminates SQLite locking conflicts between monitor and daemon - Users can now close/update issues via CLI while monitor runs - Clear error messages guide users to start daemon first Fixes beads-eel * bd sync: 2025-11-06 18:03:50 * docs: Add bd daemons restart subcommand documentation Added documentation for the 'bd daemons restart' subcommand across all documentation files: - commands/daemons.md: Added full restart subcommand section with synopsis, description, arguments, flags, and examples - README.md: Added restart examples to daemon management section - AGENTS.md: Added restart examples with --json flag for agents The restart command gracefully stops and starts a specific daemon by workspace path or PID, useful after upgrading bd or when a daemon needs refreshing. Fixes beads-11 * bd sync: 2025-11-06 18:13:16 * Separated the web ui from the general monitoring functionality --------- Co-authored-by: Steve Yegge <stevey@sourcegraph.com>
4.7 KiB
4.7 KiB
bd daemons - Daemon Management
Manage bd daemon processes across all repositories and worktrees.
Synopsis
bd daemons <subcommand> [flags]
Description
The bd daemons command provides tools for discovering, monitoring, and managing multiple bd daemon processes across your system. This is useful when working with multiple repositories or git worktrees.
Subcommands
list
List all running bd daemons with metadata.
bd daemons list [--search DIRS] [--json] [--no-cleanup]
Flags:
--search- Directories to search for daemons (default: home, /tmp, cwd)--json- Output in JSON format--no-cleanup- Skip auto-cleanup of stale sockets
Example:
bd daemons list
bd daemons list --search /Users/me/projects --json
health
Check health of all bd daemons and report issues.
bd daemons health [--search DIRS] [--json]
Reports:
- Stale sockets (dead processes)
- Version mismatches between daemon and CLI
- Unresponsive daemons
Flags:
--search- Directories to search for daemons--json- Output in JSON format
Example:
bd daemons health
bd daemons health --json
stop
Stop a specific daemon gracefully.
bd daemons stop <workspace-path|pid> [--json]
Arguments:
<workspace-path|pid>- Workspace path or PID of daemon to stop
Flags:
--json- Output in JSON format
Example:
bd daemons stop /Users/me/projects/myapp
bd daemons stop 12345
bd daemons stop /Users/me/projects/myapp --json
restart
Restart a specific daemon gracefully.
bd daemons restart <workspace-path|pid> [--search DIRS] [--json]
Stops the daemon gracefully, then starts a new one in its place. Useful after upgrading bd or when a daemon needs to be refreshed.
Arguments:
<workspace-path|pid>- Workspace path or PID of daemon to restart
Flags:
--search- Directories to search for daemons--json- Output in JSON format
Example:
bd daemons restart /Users/me/projects/myapp
bd daemons restart 12345
bd daemons restart /Users/me/projects/myapp --json
logs
View logs for a specific daemon.
bd daemons logs <workspace-path|pid> [-f] [-n LINES] [--json]
Arguments:
<workspace-path|pid>- Workspace path or PID of daemon
Flags:
-f, --follow- Follow log output (like tail -f)-n, --lines INT- Number of lines to show from end (default: 50)--json- Output in JSON format
Example:
bd daemons logs /Users/me/projects/myapp
bd daemons logs 12345 -n 100
bd daemons logs /Users/me/projects/myapp -f
bd daemons logs 12345 --json
killall
Stop all running bd daemons.
bd daemons killall [--search DIRS] [--force] [--json]
Uses escalating shutdown strategy:
- RPC shutdown (2 second timeout)
- SIGTERM (3 second timeout)
- SIGKILL (1 second timeout)
Flags:
--search- Directories to search for daemons--force- Use SIGKILL immediately if graceful shutdown fails--json- Output in JSON format
Example:
bd daemons killall
bd daemons killall --force
bd daemons killall --json
Common Use Cases
Version Upgrade
After upgrading bd, restart all daemons to use the new version:
bd daemons health # Check for version mismatches
bd daemons killall # Stop all old daemons
# Daemons will auto-start with new version on next bd command
# Or restart a specific daemon
bd daemons restart /path/to/workspace
Debugging
Check daemon status and view logs:
bd daemons list
bd daemons health
bd daemons logs /path/to/workspace -n 100
Cleanup
Remove stale daemon sockets:
bd daemons list # Auto-cleanup happens by default
bd daemons list --no-cleanup # Skip cleanup
Multi-Workspace Management
Discover daemons in specific directories:
bd daemons list --search /Users/me/projects
bd daemons health --search /Users/me/work
Troubleshooting
Stale Sockets
If you see stale sockets (dead process but socket file exists):
bd daemons list # Auto-cleanup removes stale sockets
Version Mismatch
If daemon version != CLI version:
bd daemons health # Identify mismatched daemons
bd daemons killall # Stop all daemons
# Next bd command will auto-start new version
Daemon Won't Stop
If graceful shutdown fails:
bd daemons killall --force # Force kill with SIGKILL
Can't Find Daemon
If daemon isn't discovered:
bd daemons list --search /path/to/workspace
Or check the socket manually:
ls -la /path/to/workspace/.beads/bd.sock