The workbench

One page served by the host on loopback, laid out like an editor. Nothing is fetched from the internet; no account.

devplane up           # in your browser
devplane up --window  # in its own window (the desktop app, or --features app)

? lists the keys bound where you are.

The regions

A click opens a preview tab (italic) that the next click replaces; double-click or Enter keeps it. Open tabs stay in this browser tab only. The address names what is showing, so a link or reload reopens it.

First run

With nothing set up, the workbench opens on Setup’s checklist: sessions already running, update checks, connect an agent, trust a repository, declare a check, the spec layout, and a first change. Each step reads what is true on this machine, so closing the window loses nothing. Any step can be skipped and brought back. A step that writes configuration shows the exact diff and writes only on Confirm. Trusting a repository needs the desktop window; a browser tab gives you the devplane project trust command instead.

A project with no gates says so wherever gates are shown — no gates declared — and offers Declare a check instead of Run gates.

A change

Open it from Changes, the palette, or a devplane://change/<id> link.

• Header: title, state, and the actions that apply; the rest under More. Below it, the gate standing as a sentence (check exited zero against the working tree as it stands).
• Actions: Review, Run gates, Offer as pull request (verified only); More holds Finish, Archive, Editor and Terminal.
• A weakened check leads the header — 1 check weakened · verified — and hides the green sentence until read. While a weakened row is unseen, Review is the primary action and the offer is refused, with a button to each row. Files nobody opened are named beside the offer; they never refuse it.
• Alt+1 … Alt+6 (⌥1 … ⌥6) switch the six views:

What the states and standing mean: Verified done.

The review

Every hunk of every file in one column against the merge base (uncommitted and untracked files included), with the file tree beside it. Each file’s header stays on screen while its hunks scroll: path, lines, role, test coverage, what it was asked for, and facts with the command to check each.

• Checks weakened or changed come first (the kinds). The line that made a row carries ⚠ in the gutter. A row is read when its hunks are marked seen.
• Then files in [review] roles order (path order without roles, and the view says so). By intent groups them by the run that wrote them; files nobody asked for get their own heading.
• Formatting-only hunks are collapsed and counted. The tree counts unread hunks per file.

• Seen is kept by the host, keyed by the hunk’s content: a hunk the agent rewrites is unread again. The CLI, the inbox and the offer read the same marks. Scrolling marks nothing.
• Comments: press a line number (or f). Comments wait in a pending review and survive a reload. Send N comments sends them as one turn to the change’s agent, each with its path, line and the tree it was written against, and says whether the agent reads it now, after its turn, or was resumed for it. After the agent’s next turn each sent comment says whether its hunk changed.
• devplane://review/<id> opens this view; the CLI is devplane change review <id> [--by intent].

The inbox

Each key is printed on the control it presses; one that does not apply says why. The same keys work in the desktop app’s answer window.

• An answer is held for 5 seconds before it reaches the agent, with a countdown; z takes it back with nothing sent or recorded. Answering another item sends the held one at once. Quitting the host cancels it, and the question is waiting again at the next start. devplane inbox answer sends at once.
• Snoozed items leave the list and are counted at its foot, with list them and bring back.
• The inbox badge, the status bar’s need you and the tray count are one number.

Sessions

Every session, watched or driven, in one grid; state counts are filters, grouped by project or state. What each state means: Watching sessions.

New change, the palette, the bottom panel

• New change (Alt+N): projects, optional spec, title (also the branch), first prompt, agent, and worktree or in place. It shows each project’s preflight and every refusal before creating anything.
• The palette (⌘K / Ctrl+K) finds changes, surfaces, actions and projects; > lists only actions; other text also searches every session’s tool calls, questions and errors. Over an inbox item or a change, its own actions come first.
• Activity: every session’s events, newest first.
• Sight: what this machine can and cannot see — vendors watched end to end, wired but unproved, only seen when Devplane starts them, and projects whose configuration cannot be read. An empty Sessions list is not proof that nothing runs.

Keys

No key fires while you type in a field, except Esc and the ⌘/Ctrl chords.

The window

devplane up --window adds desktop notifications when an agent asks or gives up, a tray count, and a global shortcut (⌘⇧Space; [app] shortcut) that shows the top item over whatever you are doing. Install: The window.

A permission or question can be answered from its notification:

A build run from source, a Windows build run from target/, or a desktop without a notification service gets a plain notification with no actions. devplane doctor says which you have. devplane up without a window notifies through the system notifier, plainly.

Something wrong or out of date? Edit this page.