Quickstart

This guide walks the full first-time loop: install the CLI, sign in, deploy a static site, share it, and iterate. Every step shows the verification you should see, so you know whether to continue or troubleshoot.

If you'd rather skip the local CLI and use a coding agent (Claude Code, Codex, Cursor, Antigravity, Antigravity CLI, Windsurf, OpenCode, Copilot CLI, Hermes Agent) or a chat client (ChatGPT, Claude Desktop), jump to MCP — but doing this once locally builds the right mental model for everything else.

1. Install the CLI

curl -fsSL https://vibehost.com/install.sh | sh

iwr -useb https://vibehost.com/install.ps1 | iex

vibehost --version

The installer drops a single static binary; no Node runtime needed. Config lives at ~/.config/vibehost/config.json (mode 600 — never shared, never committed).

2. Sign in

vibehost login

vibehost login --email you@example.com --password "$VIBEHOST_PASSWORD"

vibehost whoami

3. Create your first app

Apps are the unit of deployment. Names are workspace-scoped, lowercase, 2–40 chars ([a-z][a-z0-9-]*).

vibehost app create my-first-site --display-name "My First Site" --description "Hello-world static site from the quickstart"

The name is the immutable slug used in URLs; --display-name and --description are optional display metadata the dashboard shows (it falls back to the name when unset). Change them any time with vibehost app update.

Verify:

vibehost app inspect my-first-site --json

inspect is the single most useful agent-facing command — it returns runtime, visibility, password status, channels, recent deployments, custom domains, grants, and active share links in one call. You'll use it a lot.

4. Deploy

We need something to deploy. The simplest possible site:

mkdir -p hello && echo '<h1>Hello, VibeHost</h1>' > hello/index.html

Now deploy:

vibehost deploy ./hello --app my-first-site

You'll see something like:

{
  "ok": true,
  "data": {
    "id": "depl_abc123...",
    "url": "https://my-first-site-your-workspace.vibehost.space",
    "immutableUrl": "https://depl_abc123.vibehost.space",
    "deployKind": "static",
    "status": "healthy"
  }
}

Two URLs to understand:

• url — the alias URL. Moves to whatever's current on this channel. Share this with humans.
• immutableUrl — the permanent URL for this exact artifact. Use this when you need to reference a specific version that won't change under you (bug reports, code review, archived demos).

Open the alias URL in a browser. You should see "Hello, VibeHost".

cd hello && vibehost link --app my-first-site
vibehost deploy   # uses linked app from .vibehost/project.json

5. Share it

By default new apps are private — only you can view. Three ways to share:

vibehost app visibility my-first-site public

vibehost app grants add-email teammate@example.com viewer --app my-first-site

vibehost app share-link create --app my-first-site --expires 7d

6. Iterate

Change the HTML and redeploy:

echo '<h1>Hello, world. v2.</h1>' > hello/index.html
vibehost deploy

The alias URL refreshes immediately (within ~5s of healthy status). The previous deployment is still accessible at its own immutableUrl — VibeHost never deletes deployments on redeploy, only the channel alias moves.

Roll back if v2 is broken:

vibehost rollback --app my-first-site

Alias snaps back to v1's immutableUrl. No re-upload, instant.

What just happened

Common first-deploy failures

Hit something else? Run vibehost doctor — it probes auth, API reachability, version skew, and config gotchas in one shot.

Next

• CLI reference — every command, every flag
• Channels — preview deploys, promote, rollback
• Custom domains — bring your own hostname
• Grants and visibility — control who sees what
• MCP — drive everything you just did from Claude / Cursor / ChatGPT
• Recipes — end-to-end scenarios (MVP demo, client delivery, CI/CD, ...)
• Personal access tokens — drive it from any HTTP client