Skip to main content

Commands

Local CLI

Service lifecycle

Remote Web UI

Updates

Utilities

Show Runtime archives accumulate under ~/.avibe/runtime/show-runtime/downloads as new versions are installed. Cleanup keeps the archive used by the current runtime plus the rollback version, and removes only verified, completed archives. vibe doctor reports when stale archives are reclaimable. Internal agent trace events (agent_events tool-call traces — diagnostic material, never chat messages) are retained for 30 days by default. A daily background pass deletes only older traces; chat history, deliveries, and newer traces are never touched. Configure the window or opt out via the runtime.agent_events_trace_retention_days and runtime.agent_events_trace_retention_enabled config fields. The automatic pass never compacts the database — physical space is reclaimed by the explicit vibe data retention --run --compact maintenance command (best run during a maintenance window or with the service stopped, because VACUUM briefly holds the database’s sole writer lock), which compacts only after a free-space safety preflight and reports a reason when it defers.

Show Pages

Show Pages are the agent’s visual surface and the annotation 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

Agents refer to 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

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 <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