Skip to content
raven
Sign inDownload
Menu

Raven documentation.

Raven is a window for running several coding agents at once and still knowing where everything stands. These pages are about using it: what each surface shows you, and which key gets you there.

Install Raven

Choose a macOS or Linux build on the downloads page. Linux packages include the window, daemon, CLI, fonts, and local search. The page lists processor choices, runtime requirements, and installation steps.

Shortcuts in these guides use Mac notation. On Linux, open the command palette with Ctrl+Shift+K to see the shortcuts for your platform beside each action.

What you are looking at

A Raven window has four parts, and everything in these docs lives in one of them.

SpacesInboxagent panenotesfix / api-retriesblocked · 4m⌘K↩

The sidebar lists your spaces, or every agent you have running. ⌘B hides it and the spaces move to a strip across the top.

  • The sidebar down the left, in one of two modes: Spaces, a list of your threads of work, or the Inbox, every agent you have running. ⌘B hides it, and the spaces move to a strip across the top.
  • The canvas — the panes themselves. A pane is a terminal, an agent, your notes or your pull requests, and they all split, move, zoom and close the same way.
  • A status strip under each pane saying what it is and what it is doing, and a mark whose shape carries the state at a glance.
  • The command palette over all of it — ⌘K — which reaches every action in the app and prints its chord beside it.

Ninety seconds

  • ⌘D splits the focused pane. ⌘T opens a new space — one per thread of work. The sidebar names it after the branch you are on.
  • ⌘⇧T opens an agent pane. Type in the composer at the bottom, press ⏎, and a turn starts. When the agent needs a decision, the request takes the composer’s place and the keyboard — you answer it where you were already looking.
  • ⌘⇧2 switches the sidebar to the Inbox: every agent across every space, the blocked ones first, with how long they have been waiting. Click one to go straight to it.
  • ⌘K opens the palette. It is also where the shortcuts are learned — every row carries its chord — and ⌘⇧/ opens the full shortcut sheet, which fills in the keys you have actually pressed.

Then close the window. Nothing stops. Raven’s session keeps running without a window attached, so the turn that was going is still going — reopen the app and your spaces, splits, directories, scrollback and running agent sessions come back where you left them.

Where to go next

Spaces & panesThe sidebar, the space strip, splits that tile themselves, and a close you can always take back.The agent paneThe composer, approvals that take its place, Command mode, the model picker, and taking the keyboard back.The InboxEvery agent in every space in one list, blocked first, with how long it has been waiting.Worktrees & projectsThe worktree picker, per-project environments, and a space per branch.Notes & pull requestsThe two panes that draw a list instead of a terminal: your backlog, and your pull requests.AppearanceTwo palettes, the Theme Studio and its readability report, per-space themes, and the interface font.

Bring your own agent

The agent pane runs Chidori, Raven’s own agent. You do not have to use it: run claude, codex, gemini or a dozen other CLIs in an ordinary terminal pane and Raven recognizes them on sight. They get the same state mark, the same row in the Inbox, and the same three words — working, blocked, idle — with nothing to configure. An agent running inside tmux, over ssh, in a container or behind mosh counts too.

The parts that are off until you want them

Remote hosts explains how to run the daemon on a Linux server and open its panes in your Raven client through the hosted team relay.

The Fleet coordinates work you have stopped watching pane by pane, and shows up as a region inside your agent panes. Raven Teams lets a teammate answer your approvals and lets you share a single pane. Both are off until you turn them on, and signed out means nothing about your session leaves the machine.

Connect from iOS explains how to pair RavenRemote with your Mac and reach it over Wi-Fi, Tailscale, or an encrypted relay.

For scripting the window from a hook or an agent, the control CLI and the configuration file are in Reference at the foot of the sidebar.

Something missing? Help improve these docs