Skip to content

Set up Overlord

Overlord can be used from its desktop app, the CLI, or an installed agent connector. The quickest terminal-first setup is below.

Install the CLI, then authenticate against your Overlord backend:

Terminal window
npm install -g --no-fund overlord-cli
ovld auth login
ovld auth status

ovld auth login opens a browser-based sign-in flow. If you use Overlord Desktop on the same computer, the CLI can reuse its local sign-in session.

For a hosted backend, use ovld config set cloud <url> before signing in. For a local backend, use ovld config set local [url]; the default is http://127.0.0.1:4310.

Run the interactive setup to choose a backend, check authentication, prepare connectors, and select a terminal profile:

Terminal window
ovld setup

You can also prepare one connector directly:

Terminal window
ovld agent-setup codex
ovld agent-setup claude
ovld agent-setup all

See Agents and connectors for what connector setup does.

From the repository you want agents to work in, create a project and link the current checkout:

Terminal window
ovld create-project --name "My app"

If the project already exists, link the current folder instead:

Terminal window
ovld add-cwd --project-id <project-id>

Create a draft mission when you want to inspect it before running it:

Terminal window
ovld create "Add a loading state to the account page"

Or create and queue it in one step:

Terminal window
ovld prompt "Add a loading state to the account page" --agent codex

The desktop app and runner can launch queued objectives. To launch a mission from your terminal, use:

Terminal window
ovld launch codex --mission-id <mission-id>

When the agent finishes, open the mission in Overlord to review its objective, activity, delivery summary, artifacts, changed files, and rationale. Continue the same mission with a follow-up objective when more work is needed.

Next: Missions and objectives