VibeAround Command Line

The VibeAround npm package is the fastest way to start from a terminal. It installs both vibearound and the shorter va command, plus the native CLI, TUI, launcher, standalone server, and bundled Web Hub assets.

Beta note: the command-line distribution, standalone server, va-launch, and TUI are early beta surfaces. They are usable for terminal-first workflows, but expect sharper edges than the desktop app while the server, launch layer, Web Hub, CLI, and TUI continue to separate and stabilize.

npm install -g vibearound

Core Commands

Command	Use it for
`va serve`	Start the standalone local VibeAround server and bundled Web Hub.
`va tui`	Open the terminal dashboard for agents, sessions, runtime state, and chat.
`va launch --profile NAME`	Launch a saved agent profile.
`va launch --profile-path PATH`	Launch from a profile JSON file.
`va status`	Show a compact runtime summary.
`va doctor`	Diagnose endpoint, auth, and server health.

Typical Flow

Install the CLI with npm.
Run va serve to start the local server.
Open va tui in another terminal for a keyboard-first dashboard.
Use va launch --profile codex or another saved profile to start an agent.
Use the desktop app, Web Hub, browser, mobile, or messaging channel as additional entry points to the same local hub.

Configuration Files

VibeAround stores local CLI configuration under ~/.vibearound by default. Set VIBEAROUND_DATA_DIR if you want a different data directory.

There are two different profile files:

File type	Path	Used by
Provider profile	`~/.vibearound/profiles/<id>.json`	`va launch --profile <id>`
Launch profile	Any JSON path you choose	`va launch --profile-path <path>`

Provider profiles describe model credentials and API bridge behavior. Launch profiles describe the native launch request: agent, workspace, terminal, command, args, and env.

Minimal Provider Profile

This example launches Codex with a saved xAI / Grok provider profile.

mkdir -p ~/.vibearound/profiles

~/.vibearound/settings.json

{
  "default_agent": "codex",
  "enabled_agents": ["codex"],
  "workspaces": ["/Users/example/project"]
}

~/.vibearound/profiles/codex-work.json

{
  "id": "codex-work",
  "label": "Codex Work",
  "provider": "xai",
  "auth_mode": "api_key",
  "api_types": ["openai-responses"],
  "credentials": {
    "api_key": "xai-your-key"
  },
  "overrides": {
    "openai-responses": {
      "model": "grok-4.3"
    }
  }
}

The id must match the filename stem. For the example above, the file must be named codex-work.json.

va launch --profile codex-work --dry-run
va launch --profile codex-work

Use --dry-run first when you are editing files by hand. It validates the profile and prints the launch plan without spawning the agent.

Minimal Launch Profile

Use --profile-path when you want to bypass provider-profile resolution and directly describe a native launch. This file is useful for scripts, smoke tests, or launching with explicit environment variables.

./codex-launch.json

{
  "schemaVersion": 1,
  "agent": "codex",
  "profileId": "direct-codex",
  "workspace": "/Users/example/project",
  "terminal": "terminal",
  "command": "codex",
  "env": {
    "OPENAI_API_KEY": "sk-your-key"
  },
  "args": {
    "native": ["-c", "check_for_update_on_startup=false"]
  }
}

va launch --profile-path ./codex-launch.json --dry-run
va launch --profile-path ./codex-launch.json

Supported terminal values include system-terminal, terminal, iterm2, powershell, gnome-terminal, konsole, xfce4-terminal, xterm, kitty, alacritty, and wezterm.

File Safety

These files can contain API keys. Keep ~/.vibearound local, avoid committing profile JSON to a repository, and prefer environment-specific copies for team or CI workflows.

Notes

The command is va serve, not va server. The npm wrapper also ships the native vibearound-server binary internally, but the user-facing command is va serve.