Everything you need to vibe.

1. Install the vb CLI

One command on macOS or Linux — Node 18+ is the only requirement. Working from a checkout of the VibeHub repo instead? npm install && npm link puts the same vb bin on your PATH.

curl -fsSL https://vibehub.co/install.sh | sh

vb --version

2. Authenticate

Open the dashboard, generate a token, and paste it once.

vb login
# opens browser → paste vbh_… token

vb whoami
# → API https://vibehub.co · token vbh_3f9c…

3. Create a project

Either click + New project in Dashboard → Projects, or wrap an existing git repo from the CLI.

cd my-project
vb init
# wraps the repo with a .vb/ directory

4. Commit the vibe

Same shape as git commit. vb captures the open agent session and bundles it in.

vb commit -m "feat: add waitlist"
# commits + uploads the diff and LLM transcript

vb push
# git push to origin + mirror to GitHub

Project

A git repo registered with VibeHub. Has an owner, a slug, and a visibility (public / private). Create one from Dashboard → Projects or by running vb init in any git repo — never a migration.

Vibe object

A content-addressed bundle of spec, prompts, transcript, model config, diff, eval, and artifact. The unit of work on VibeHub — what gets pushed, forked, and replayed.

Session

An open agent conversation. Starts open, accumulates messages, becomes attached once linked to a commit, and is otherwise cleaned up as orphaned.

Commit

A git commit captured into VibeHub. Carries the diff, file stats, and the session that produced it. Attaching a session to a commit is the moment a vibe is born.

Workflow

A named automation with a trigger (on_commit, on_publish, on_fork, schedule) and an action, triggered from the dashboard or the API. Each trigger creates a run with status and metrics.

Collection

A curated list of vibes — your own or anyone's. Use them to organise the gallery, build playlists, or share a starter pack with your team.

Define

In the dashboard at Workflows → New — pick a name, a trigger, and an action. Workflows can be active, paused, or draft; only active ones can be triggered.

You can also ask the in-dashboard agent to create one for you — it has a create_workflow tool.

Trigger

From the dashboard, or POST /api/workflows/:id/trigger (dashboard session auth).

POST /api/workflows/<id>/trigger
# → { "workflow": { …, "status": "active",
#      "runsCount": 4 } }

From the dashboard

1. Open Dashboard → Projects, click the cog on your project (or open it → Settings).
2. Fill in Owner, Repo, and Default branch.
3. Paste a fine-grained PAT from github.com/settings/personal-access-tokens with contents: read & write on the target repo.
4. Save. The token is encrypted at rest; only the prefix is visible afterwards.

From the CLI

# link once
vb mirror set --repo owner/repo --token ghp_…

# from now on every push mirrors
vb push                  # pushes to origin + mirrors to GitHub

# explicit re-mirror without re-pushing
vb mirror push

# inspect the current config + last status
vb mirror show

# skip the mirror on a single push
vb push --no-mirror

In the dashboard

Open the agent panel from any page. It has a ~35-tool toolkit over your workspace: listing and inspecting vibes, commits, diffs, blame, branches, and analytics, plus write actions — creating and updating vibes, forking, running, managing collections and workflows, and following builders. Destructive tools (delete) require an explicit confirmation turn. Each assistant turn costs 1 credit.

In your IDE

Claude Code gets a full plugin — auto transcript capture plus a /vibehub:capture skill. Everything else speaks MCP: Cursor, Claude Desktop, Windsurf, Zed, JetBrains, Visual Studio, Continue.dev. See the MCP reference and Dashboard → Integrations for one-line installs.