Overlord

1. Create an account

Sign up at ovld.ai/signup and finish onboarding in the web app. Your account hosts your projects, tickets, and delivery history.

Agent-assisted CLI onboarding

You can also ask an agent to onboard you from the terminal. Install the CLI, move into the repository you want Overlord to manage, and run:

npm install -g @overlord-ai/cli
cd /path/to/your/repo
ovld onboard

ovld onboard asks for your name, organization name, and project name, opens browser signup/login, creates your first organization and project, links the current directory, and creates the same starter review ticket as the web onboarding flow. At the end it strongly recommends opening the Desktop download page; choose no to open the project in the web app instead.

If you only have an email address — for example an autonomous agent with no browser — create the account entirely in the terminal. ovld onboard --email you@example.com (or the account-only ovld auth signup --email you@example.com) emails an 8-digit confirmation code, you enter it at the prompt, and the CLI stores valid credentials plus a durable agent token. Pass --password to set a password-manager password; otherwise log back in later with ovld auth login --email you@example.com.

2. Download the desktop app

The desktop app is what launches agents locally, follows your repositories, and streams updates back into Overlord.

Download the latest build from the Downloads page.
Install it like any native app and sign in with the account you just created.

On first launch, the app walks you through linking a workspace folder and choosing which agents to connect.

3. Install the agent plugins

Agents like Claude Code and Codex talk to Overlord through a small plugin. Installing a plugin once lets Overlord launch, attach, and deliver tickets through that agent.

Follow the Agent plugins guide to install the plugins from Overlord settings, then register them in Claude Code and the Codex desktop app.

4. Create your first ticket

With the plugins installed you can create a ticket from the web app, the desktop app, or the CLI. Keep the first one simple — a clear objective and a project is usually enough.

5. Launch and review

Launch the ticket from the desktop app. The agent runs in its own terminal, streams updates into Overlord, and waits for you to review the delivery before anything lands.

Prefer the terminal? Launch in one line

If you live in the terminal, skip the UI entirely. From a registered project directory, ovld <agent> "<prompt>" creates a ticket from your prompt and launches the agent on it in a single command:

ovld claude "add a health check endpoint" --model opus

See the CLI guide for the full flag reference.

Quick Start