Commands
Local CLI
Service lifecycle
Remote Web UI
Updates
Utilities
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.