Skip to content
VibeGuild
Menu
Sign inGet started

Getting started

VibeGuild is in private beta — you need an invite code to create an account, and a signed-in account to use the app.

1. Create your account

  1. Go to sign up and enter your invite code, name, email, and a password.
  2. Click the verification link we email you — you'll be signed in automatically.

2. Install the app

Signed in, head to Download — it always serves the current beta build for your platform. Both are published from the same release:

  • macOS (Apple Silicon) — a .dmg; drag VibeGuild to Applications.
  • Windows (x64) — an installer that installs per user, so there is no admin prompt.

First launch

Beta builds are not code-signed yet, so each platform asks once before it will run a fresh download. In-app updates skip all of this.

On macOS, the download is quarantined and the app is reported as "damaged". Clear it once, in Terminal, after moving the app to Applications:

xattr -d com.apple.quarantine /Applications/VibeGuild.app

On Windows, SmartScreen warns on the installer: choose More info, then Run anyway.

3. Sign in from the app

Click Sign in in the app (bottom of the left rail, or Settings → Account). Your browser opens to approve the sign-in; the app itself never sees your password. You stay signed in across restarts, and the app keeps working offline for a day at a time.

4. Make your first workspace

  1. Click New workspace and pick a project folder — usually a repo.
  2. Pick a layout (1×2, 2×2, 1+2, …). The "Start with" steppers pre-fill the grid: two Claude Code panes and a terminal in a 2×2, say — the rest start empty and you fill them whenever.
  3. That's it. Each pane is a real terminal, running in your project folder — your agents behave exactly as they do in your own shell.

Agent panes launch the CLIs you already have installed. A pane whose agent isn't installed says so and offers an Install button that runs the vendor's own one-liner in that pane, so there is nothing to check up front — but if you'd rather confirm from a shell:

claude --version   # Claude Code
codex --version    # Codex

5. Try the parts that aren't a terminal

With something running, these are the fastest ways to see what the app adds on top of the CLIs:

  • Press Cmd+K (macOS) or Ctrl+Shift+K (Windows) for command mode, then p s to split the focused pane, or v g to open the git panel.
  • Click a pane's branch pill and pick a new branch: that pane moves into its own worktree and its agent restarts there, leaving every other pane where it was.
  • Ask an agent something only the app can answer — "what are my other panes doing?" — to see the built-in MCP tools work.

Staying up to date

The app updates itself. When a release lands, a chip appears in the status bar and the update dialog tells you what changed; installing restarts the app, so it never happens without you clicking. You can also check on demand from the command palette ("Check for updates"). Updated builds are already trusted, so the first-launch steps above never come back.

Where to go next