Skip to content

Latest commit

 

History

History
147 lines (107 loc) · 3.26 KB

operations.md

File metadata and controls

147 lines (107 loc) · 3.26 KB

Operations

Day-2 operations for running Baudbot in production-like environments with predictable deploy, rollback, and health-check workflows.

Core lifecycle commands

# Start / stop / restart service
sudo baudbot start
sudo baudbot stop
sudo baudbot restart

# Status and logs (status includes deployed version + broker connection/health state)
sudo baudbot status
sudo baudbot logs

# Attach / inspect active sessions
sudo baudbot attach
sudo baudbot sessions
sudo baudbot subagents list
sudo baudbot subagents reconcile

Subagent management

# List package state
sudo baudbot subagents list

# Status for all or one package
sudo baudbot subagents status
sudo baudbot subagents status sentry-agent

# Lifecycle toggles
sudo baudbot subagents install sentry-agent
sudo baudbot subagents enable sentry-agent
sudo baudbot subagents autostart-on sentry-agent
sudo baudbot subagents start sentry-agent

# Disable and remove
sudo baudbot subagents stop sentry-agent
sudo baudbot subagents disable sentry-agent
sudo baudbot subagents uninstall sentry-agent

Deployment and upgrades

# Deploy source + config to runtime
sudo baudbot deploy

# Update from upstream with preflight checks and release publishing
sudo baudbot update

# Roll back to previous or specified release snapshot
sudo baudbot rollback previous

Provision with a pinned pi version (optional):

BAUDBOT_PI_VERSION=0.52.12 baudbot install

Updating API keys after install

# Prompt for value (hidden input)
sudo baudbot env set ANTHROPIC_API_KEY

# Or inline with immediate restart
sudo baudbot env set OPENAI_API_KEY sk-... --restart

# Inspect stored value source (prints value)
baudbot env get ANTHROPIC_API_KEY --admin
sudo baudbot env get ANTHROPIC_API_KEY --runtime

# Optional: switch admin source to command backend
sudo baudbot env backend set-command 'your-secret-tool export baudbot-prod'
sudo baudbot env sync --restart

Slack broker registration

# Register this server to a broker org (after dashboard registration)
sudo baudbot broker register \
  --broker-url https://your-broker.example.com \
  --org-id org_1234abcd \
  --registration-token <token-from-dashboard-callback>

Do not use baudbot setup --slack-broker — setup is host provisioning only.

Health and security checks

# Runtime/system health checks
sudo baudbot doctor

# Security posture audit
sudo baudbot audit

# Deep audit (extension scanner + extra checks)
sudo baudbot audit --deep

Test commands

# Full test suite
npm test

# JS/TS only
npm run test:js

# Shell/security-script suites
npm run test:shell

# Coverage
npm run test:coverage

# Lint + typecheck
npm run lint
npm run typecheck

Common runbook actions

  • verify Gateway bridge responsiveness
  • verify control/sentry/dev sessions are healthy
  • clean stale worktrees
  • prune old session logs if needed (sudo -u baudbot_agent ~/runtime/bin/prune-session-logs.sh --days 14)
  • verify deployed version/manifests
  • perform rollback when upgrade regressions are detected

Uninstall

# Preview
sudo baudbot uninstall --dry-run

# Execute
sudo baudbot uninstall

For architecture context, see architecture.md. For threat model details, see ../SECURITY.md.