kolu
Docs

at scale

Run many, lose none.

These are the tools that keep five agents at once legible: the dock, the keys, sleep and wake, transcripts, recording, and a link to any view.

Multi-agent dock

An agent blocked on you appears in the dock’s pinned Needs-you strip, washes violet, and shows how long it has been waiting. A finished background agent can fire a toast and a desktop notification that jumps to its terminal.

Keybindings

Cmd + T opens a terminal, Cmd + Shift + Enter opens New terminal, Cmd + 1…9 jumps, and Cmd + / shows shortcuts.

Sessions, sleep & wake

Your whole workspace survives reloads, restarts and crashes. Sleep parks a tile without keeping its PTY, agent or GPU context alive, and wake resumes the exact conversation. Full page: Sessions, Sleep & Wake.

Export a transcript

Run Export agent session as HTML from the palette. It appears only when the active terminal has an agent session. Pick a chat log (just the Human and AI messages), a full transcript (reasoning, tool calls, results and edits collapsed under disclosure blocks), or both.

Each file is a self-contained .html with no external assets and no upload, so it opens in any browser offline. The command appears for Claude, Codex, OpenCode and Grok sessions. It does not appear for Xyne, whose transcript format kolu cannot yet read.

Record the workspace

Record the kolu tab, either the whole canvas or a single maximized terminal, with your mic and an optional webcam picture-in-picture, straight to a local .webm. Chromium only: it uses the File System Access API.

  • A popover on the chrome-bar record button sets it up: a mic picker, a webcam toggle, and a preview.
  • It streams to disk: chunks flow into the file as you record, so memory stays flat and a partial file survives a browser crash.
  • Cmd/Ctrl + Shift + . pauses and resumes. The capsule in the chrome bar shifts red → amber while paused.
  • It records just this tab: the browser’s picker collapses to one “share this tab” confirmation.

Every view in kolu has a URL. Anything that renders a link (a conductor board, a GitHub issue, a Slack message, a bookmark) can point into kolu with a #/… hash link. Click it and the app comes to the front showing the right host, terminal, file or dialog. Without kolu installed, the link opens in any browser.

LinkLands on
#/h/<host>that host, switched to
#/t/<host>/<id>that host and the terminal focused
#/t/<host>/<id>/code?path=<p>the Code tab, <p> open (add &line=<n> to land on a line)
#/t/<host>/<id>/inspectorthe Inspector tab
#/settingsthe settings dialog
#/work/<workId>the Conductor, with that work’s card open
#/work/<workId>/ask/<askId>the same card, scrolled to that question

<host> is the host’s key (local, or remote:<target>), and <id> is the terminal’s id. A <workId> is one segment; the ◆ mark on a dock row is that link. A link to a split lands the sub-terminal live, not just its parent tile. The right panel follows the focused pane, so a /code or /inspector link to a split opens that split’s own panel, and /code resolves <p> against the split’s own repository.

  • It is a bookmark, not a one-shot. Open it fresh and it navigates there, and the URL stays in the bar. A reload restores the view you had reached rather than re-firing the link, and the back button restores the URL quietly without replaying it.
  • It only changes what you look at. No URL creates a terminal, kills one, writes a file, or sends keys.
  • It says when it cannot land. A link to a closed terminal, or to a host that has left, names what it pointed at and lands you on the nearest surviving view. An unknown link shape says so. On a cold start, a link waits for the host’s terminals to load before deciding anything is missing.
  • It works from inside a preview. A #/… link in an HTML file previewed in the Code tab routes the surrounding app, so a previewed dashboard’s lane pills become click-to-jump. The preview stays sandboxed: the link is relayed out, and it can still only change what you are looking at.