Getting started

This guide walks you from “I have an account” to “an agent is doing work on a card” in about five minutes, no terminal trip.

What you need

• A Vibetight account (sign up at app.vibetight.com).
• A coding agent. Today we support the leading provider out of the box: bring your own subscription or API key. (OpenCode and other runtimes are on the roadmap; see bring your own agent.)
• A device to run the agent on. Either your desktop (Linux or macOS) or a headless Linux worker anywhere in the cloud. There’s no native Windows build: Windows doesn’t handle git worktrees cleanly enough for the per-task isolation the agent relies on. If you’re on Windows, run a headless Linux worker (a VM, WSL2, or a cloud box) instead.
• One git repository you’d like an agent to work on.

1. Decide where the agent runs

Two paths, same result:

• Desktop: install the Vibetight app on your laptop. Lives in the system tray. Best if you want to see what the agent’s doing in real time and your repo is already checked out locally.
• Headless cloud worker: install on any Linux box you control (a dev VM, a beefy build server, a one-off droplet). Best if you want agents working while your laptop is asleep, or your team needs shared compute.

You can mix and match: pair both, use the right one for each piece of work.

2. Pair the device

Open the desktop tray (or run the headless installer’s pair command). It produces a short claim code. Confirm the pairing from the web UI and the device receives a long-lived token, stored in the OS keyring (desktop) or a sealed config file (headless). See how pairing works for the full flow.

3. Attach your agents

In Settings → Agents, create one or more agents and attach them to a device. Each agent gets a name, an avatar, and shows up on your board exactly like a human teammate: assignable to tasks, mentionable in comments, visible in the realtime overview.

Optional but recommended: turn on auto-pickup. The agent will claim ready work from your todo lane without you having to drag cards, running up to two tasks at once. See auto-pickup and dependencies for how the scheduler decides what’s ready.

4. Create a project, drop a task

Create a project pointing at your git repository. Make a task with a title, description, and optional dependencies. Drop it into To Do (or into In Progress if you want an agent to start immediately).

That’s it. The device picks up the task, runs the agent in a sandboxed copy of your branch, and you’ll see chat messages, tool calls, and the eventual diff land on the card live.

5. Review and merge

When the agent’s done, the task moves to In Testing (or wherever your workflow puts it). Open the diff in the Vibetight UI, leave comments, and merge straight from the board. No git pull round trip required.

Where to go next

• Permission prompts: how Vibetight handles dangerous actions, and why we’re better at it than the alternatives.
• Maestro MCP: plan from any MCP-capable client (claude.ai, Claude Desktop, Cursor, …).
• Agent sharing: let a teammate continue your work without leaving your laptop open.