Commands
Local CLI
Service lifecycle
| Command | What it does |
|---|---|
vibe | Start Avibe and open the local Web UI |
vibe status | Show local service and configuration status |
vibe restart | Restart all services |
vibe restart --delay-seconds N | Restart N seconds from now so an active conversation can reply first |
vibe stop | Stop the local Avibe service |
vibe doctor | Run diagnostics for common setup issues |
vibe version | Print the installed version |
Remote Web UI
| Command | What it does |
|---|---|
vibe remote | Guided sign-in and pairing for the avibe.bot tunnel |
vibe remote pair <key> | Pair using a one-time key copied from avibe.bot |
vibe remote status | Show pairing and tunnel state (add --json for machine output) |
vibe remote start | Start the cloudflared tunnel after pairing |
vibe remote stop | Stop the tunnel without removing the pairing |
Updates
| Command | What it does |
|---|---|
vibe check-update | Check if a newer release is available |
vibe upgrade | Upgrade Avibe to the latest release |
Utilities
| Command | What it does |
|---|---|
vibe screenshot | Capture the local desktop to a PNG file |
Agent Harness
| Command | What it does |
|---|---|
vibe agent run | Run one Agent job now; add --async for one-shot background work, or --fork-session to branch from an existing Session |
vibe runs list / show / cancel | Inspect and manage concrete Agent Run records |
vibe task add | Save a recurring or one-off time trigger that creates Agent Runs later |
vibe task list | List saved tasks (use --brief or --all) |
vibe task show / update / pause / resume / run / remove | Manage one saved task |
vibe watch add | Run a managed waiter that creates a follow-up Agent Run when it succeeds |
vibe watch list / show / pause / resume / remove | Manage one watch |
--help for the full argument list, including
--session-id, --fork-session, --post-to, --deliver-key, --message,
--message-file, --cron, --at, --async, and --timezone where
applicable.
Use vibe agent run --fork-session <session-id> --message "..." when a new
Agent Session should branch from an existing Session’s native backend context.
The fork keeps the source backend. --agent, --model, and
--reasoning-effort may override the forked Session only when the Agent backend
does not change.
Chat usage
| In chat | What it does |
|---|---|
| Mention the bot | Start a task or ask a question |
| Reply in thread | Continue the same agent session |
/stop | Stop the current session where supported |
| Plain message in enabled scope | Send work to the configured agent |