overnite
Join waitlist

Docs

Getting started with Overnite: sign in, create a workspace, start an agent, answer it from your phone, keys and sign-ins, connectors, schedules, and the ovn CLI.

Overnite is in a closed beta. Everything here describes the cockpit at app.overnite.dev as it is today.

1. Sign in

Go to app.overnite.dev and continue with GitHub. Overnite asks for access to your repositories so an agent can clone one and open a pull request from it.

During the closed beta, only invited accounts get in. If you are not invited yet, you are added to the waitlist and we email you when you are.

2. Give your agents something to run with

Agents call AI providers with your own credentials. In Settings → Agents, either:

  • add an API key for an agent - for example ANTHROPIC_API_KEY for Claude Code or OPENAI_API_KEY for Codex; or
  • sign the agent in inside any workspace terminal once - /login in Claude Code, "Sign in with Device Code" in Codex, /connect in opencode. The sign-in carries over to every workspace you open afterwards.

Either one is enough.

3. Create a workspace

On Workspaces, pick a repository - the list is what your GitHub account can clone, most recently pushed first - and a branch, then Create workspace. Overnite starts an isolated machine and clones the repository into it.

A workspace sleeps after a while without activity and keeps its disk. Start workspace wakes it; agents that were running pick up where they left off.

4. Start an agent

In a running workspace, choose an agent - Claude Code, Codex, opencode or Gemini CLI - type a task, for example "fix the flaky test in auth.spec.ts", and Start agent. Each agent works in its own Git worktree, so several can run side by side without stepping on each other.

Every agent shows one of four states, each a shape first and a colour second:

  • working - a filled, pulsing green dot;
  • needs input - a hollow, blinking amber ring, and a bar down the side of its row;
  • failed - a red square, and a bar down the side of its row;
  • idle - a small grey dot.

5. Answer it from anywhere

When an agent asks something - "Do you want to create hello.txt?" - its row blinks and the question appears with buttons for its answers. Turn on notifications in Settings to get the same question on your phone, and answer from the notification.

The Changes panel shows what the selected agent has changed in its worktree. Agents push branches and open pull requests as you.

6. Connectors

In Settings → Connectors, connect outside services once; each workspace and each agent chooses which ones it gets. GitHub is connected when you sign in, and Context7 - current documentation for libraries - needs nothing. Selected connectors appear to the agent as MCP servers.

7. Schedules

On Schedules, run an agent on a cron in your timezone - "every night at 02:00, update dependencies, run the tests, open a PR" - and see how each run went, with a link to the pull request it opened.

8. The ovn CLI

Inside a workspace, agents - and you, in a terminal - can drive other agents with ovn:

  • ovn list - every agent in this workspace
  • ovn spawn claude "write the migration" - start an agent
  • ovn wait <id> --until idle - block until it is done or needs input
  • ovn read <id> - its screen
  • ovn input <id> "yes" - answer it
  • ovn kill <id> - stop it

ovn help <command> explains each one. The commands are compatible with Herdr's socket API.

Help

Stuck? Email support@overnite.dev with your GitHub login and what you were doing.