Everything you need to vibe.

1. Install the vb CLI

Published to npm. Node 18+ is the only requirement.

npm i -g @vibehub/cli

# or with pnpm / bun
pnpm add -g @vibehub/cli
bun add -g @vibehub/cli

2. Authenticate

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

vb login
# opens browser → paste vbh_… token

vb whoami
# → you@example.com

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"
# captures code + prompts + model config

vb push
# uploads to VibeHub, mirrors 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 saved, parameterised sequence of vb steps that can be triggered manually or on a schedule. Each trigger creates a run with full logs and an output artifact.

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, or by pushing a .vb/workflows/*.yml file.

yamlname: ship-landing
description: Rebuild the landing page from a prompt diff
inputs:
  - name: headline
    type: string
    required: true
steps:
  - vb replay :prompt_template:
  - vb commit -m "feat: $headline"
  - vb push

Trigger

From the CLI, the dashboard, or POST /api/workflows/:id/trigger.

# from the CLI
vb workflow run ship-landing \
  --input headline="The vibe is the new commit"

# from the API
curl -X POST \
  https://vibehub.co/api/workflows/wf_… \
  -H "Authorization: Bearer vbh_…" \
  -d '{"inputs":{"headline":"…"}}'

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 can summarise activity, suggest workflows, and call any read tool on your behalf.

In your IDE

The MCP server lets Cursor, Claude Desktop, Windsurf, Continue.dev, and Zed talk to VibeHub directly. See the MCP reference.