> Manage beads daemon processes across all repositories and worktrees.
Manage and monitor beads daemon processes across all repositories and worktrees. Use to list running daemons, check health, view logs, or stop unresponsive processes.
/plugin marketplace add shaneholloman/beads/plugin install beads@beads-marketplaceManage beads daemon processes across all repositories and worktrees.
beads daemons <subcommand> [flags]
The beads daemons command provides tools for discovering, monitoring, and managing multiple beads daemon processes across your system. This is useful when working with multiple repositories or git worktrees.
List all running beads daemons with metadata.
beads 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 socketsExample:
beads daemons list
beads daemons list --search /Users/me/projects --json
Check health of all beads daemons and report issues.
beads daemons health [--search DIRS] [--json]
Reports:
Flags:
--search - Directories to search for daemons--json - Output in JSON formatExample:
beads daemons health
beads daemons health --json
Stop a specific daemon gracefully.
beads daemons stop <workspace-path|pid> [--json]
Arguments:
<workspace-path|pid> - Workspace path or PID of daemon to stopFlags:
--json - Output in JSON formatExample:
beads daemons stop /Users/me/projects/myapp
beads daemons stop 12345
beads daemons stop /Users/me/projects/myapp --json
View logs for a specific daemon.
beads daemons logs <workspace-path|pid> [-f] [-n LINES] [--json]
Arguments:
<workspace-path|pid> - Workspace path or PID of daemonFlags:
-f, --follow - Follow log output (like tail -f)-n, --lines INT - Number of lines to show from end (default: 50)--json - Output in JSON formatExample:
beads daemons logs /Users/me/projects/myapp
beads daemons logs 12345 -n 100
beads daemons logs /Users/me/projects/myapp -f
beads daemons logs 12345 --json
Stop all running beads daemons.
beads daemons killall [--search DIRS] [--force] [--json]
Uses escalating shutdown strategy:
Flags:
--search - Directories to search for daemons--force - Use SIGKILL immediately if graceful shutdown fails--json - Output in JSON formatExample:
beads daemons killall
beads daemons killall --force
beads daemons killall --json
After upgrading beads, restart all daemons to use the new version:
beads daemons health # Check for version mismatches
beads daemons killall # Stop all old daemons
# Daemons will auto-start with new version on next beads command
Check daemon status and view logs:
beads daemons list
beads daemons health
beads daemons logs /path/to/workspace -n 100
Remove stale daemon sockets:
beads daemons list # Auto-cleanup happens by default
beads daemons list --no-cleanup # Skip cleanup
Discover daemons in specific directories:
beads daemons list --search /Users/me/projects
beads daemons health --search /Users/me/work
If you see stale sockets (dead process but socket file exists):
beads daemons list # Auto-cleanup removes stale sockets
If daemon version != CLI version:
beads daemons health # Identify mismatched daemons
beads daemons killall # Stop all daemons
# Next beads command will auto-start new version
If graceful shutdown fails:
beads daemons killall --force # Force kill with SIGKILL
If daemon isn't discovered:
beads daemons list --search /path/to/workspace
Or check the socket manually:
ls -la /path/to/workspace/.beads/beads.sock