> ## Documentation Index > Fetch the complete documentation index at: https://docs.avibe.bot/llms.txt > Use this file to discover all available pages before exploring further. # Commands > Common Avibe CLI and chat commands. # 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 ` | 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 | ### Show Pages | Command | What it does | | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | `vibe show status` / `path` / `list` | Inspect, resolve, or list the session's [Show Page](/concepts/show-pages) | | `vibe show update --visibility private\|public\|offline` | Set visibility, a custom public link, or take the page offline | | `vibe show annotate --on\|--off [--mode smart\|screenshot]` | Turn the user's [annotation](/concepts/annotating-show-pages) overlay on/off or switch mode (no chat message) | | `vibe show reply --message "…"` | Answer a page annotation, anchored where the user pointed | | `vibe show mark --message "…"` | Leave a callout on an element (same target replaces) | | `vibe show marks` / `vibe show unmark …` | List active marks / retire one or more | Show Pages are the agent's visual surface and the [annotation](/concepts/annotating-show-pages) loop runs over them: the user points at the page, the agent answers back on it. The agent drives these commands — a user rarely runs them directly. ### Vaults | Command | What it does | | ----------------------------------- | ----------------------------------------------------------------------- | | `vibe vault list` / `find` / `tags` | Discover secret names and value-free metadata without revealing values | | `vibe vault request ` | Ask the user to provide a missing secret in the Workbench | | `vibe vault run` | Inject selected static secrets into one child process | | `vibe vault fetch` | Attach a static credential to an authenticated HTTP request at egress | | `vibe vault access` / `await` | Request approval for protected use and read the completed request | | `vibe vault sign` | Sign a 32-byte digest with a keypair; the private key is never exported | Agents refer to [Vaults](/concepts/vaults) by secret name, tag, or Skill tag. Standard secrets are available now. Protected operations describe a pre-launch passkey flow and must not hold real secrets until the immutable sandbox integrity gate is enforced. Avoid commands that print environment variables or secret-bearing debug output when using `vibe vault run`. ### 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 | Together these commands form the Avibe Harness. A user can ask their agent to watch a PR, wait for CI, schedule a daily status check, start a separate investigation session, or fan out background checks. The agent can combine the primitives without making the user memorize every flag. Each subcommand accepts `--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 --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 |