Skip to main content

Users FAQ

Why are there two binaries (vibecontrols and vibe)?​

They do different things:

  • vibecontrols is the CLI for managing everything on the backend (vibes, sessions, targets, vibedecks, webhooks, etc.). Install from @vibecontrols/cli.
  • vibe is the agent runtime that runs on a machine to host sessions, tunnels, plugins. Install from @vibecontrols/agent.

You install both. The CLI talks to the backend (which talks to the agent).

Can I run vibes on a remote machine?​

Yes — install @vibecontrols/agent on the remote machine, run vibe start, and the agent registers via its outbound tunnel. From then on it appears in Targets in the web app.

How do vibes differ from Docker Compose?​

A vibe is a project context in a database (with type, status, env vars, git metadata, hierarchy). It doesn't start containers — sessions inside the vibe do whatever you tell them to (which might include docker compose up).

There's no vibe.yaml file. Vibes are created via CLI/GraphQL.

What does a VibeDeck do?​

A VibeDeck is a Stream-Deck-style grid of action buttons. Each button runs a command, script, or webhook with one click. Not a "bundle of vibes."

How many concurrent sessions can one agent handle?​

No hard limit in code. Bounded by your machine's RAM/CPU. The agent's REST API isn't a bottleneck.

Is there a free tier?​

Yes — single-developer use is free on the cloud-managed offering. Team features (sharing, vibedeck share links, multi-agent) require a paid Burdenoff Workspaces tenant.

Where is my data stored?​

  • Vibes / sessions / notes / prompts / webhooks — backend Postgres (your tenant's region)
  • Per-agent config + plugin state — locally at ~/.boff/vibecontrols/agents/<id>/ (encrypted SQLite)
  • CLI credentials — ~/.config/vibecontrols-cli/auth.json (mode 0600)

Can I self-host?​

Yes — see Self-hosted setup.

How do I report a bug?​

GitHub Issues on github.com/algoshred/vibecontrols or the community forum.