The panes that are not terminals

Open them

• ⌘⇧EThe notes pane — your backlog
• ⌘⇧PThe pull-request pane
• ⌘FPut the caret in that pane’s own search
• ⌘⇧BDiscuss the backlog with an agent

Both are also in the palette, and both are ordinary panes: leaves of the space’s split tree that focus, move, resize, zoom and close like any terminal. A notes pane comes back a notes pane after a restart, and ⌘Z reopens one you closed.

One table, two lists

Both panes are the same table: a filter bar over one line per row, j/k or the arrows to move, g/G for the ends, ⏎/o to open the highlighted row, / to search. A click on a row’s title opens it; a click anywhere else in the row only highlights it.

Both bars carry Sort and Group beside + Filter. A chosen order or grouping reads back as a chip — Sort by Updated ↓ × — and clicking the chip puts that one choice back the way the pane opened. Over a focused list, ⌘K leads with that pane’s own actions and the categories its rows can be narrowed by.

Notes

The notes pane is the ledger’s backlog, one note per row — the things older builds called issues or tasks. Rows open under project headers in the ledger’s own order, and a note’s line ends the way a pull request’s does: the PR it rides, the checkbox, the title, whatever agent sessions are on it, and how long it has been open.

A note’s body has an activity trail: one folded revision per editing session, each attributed to its author — you, or an agent by its pane. If someone is in the body right now, the pane says so.

Pull requests

The list is the pull requests you opened, so there is no author column. A line reads number, title, repository, how long it has been open — 18h, 3d, 2mo — then its marks: mergeability, review, CI, review comments, and the note it belongs to. Sort offers attention first: what an agent is blocked on, then the repository, then the latest change.

• Opening one lands on Description, with Conversation, Commits, Checks and Files changed beside it — ←/→ or Tab walk them.
• Descriptions and comments are rendered markdown: headings, lists, task boxes, fenced code and links.
• Checks groups the run by outcome. A row carries the workflow behind it and how long it ran; opening one adds who reported it, the event that started it, the provider’s summary, and the annotations a failing job attached — the file, line and message it pointed at.
• Edit rewrites the description in place; ⌘⏎ writes it to GitHub. It needs a token with contents and pull requests write access, or the GitHub CLI signed in.
• Attach video… — or dropping a video on the open editor — commits the file to the repository’s raven-media branch and puts its URL on its own line, which is how GitHub embeds a video. GitHub has no public API for the attachments its own editor uploads; the branch is where a token can put a file.
• Write a comment, at the foot of the conversation, opens the same editor on a new comment and posts it to the thread.
• Merge and Close — or Reopen — sit under the branches and take two presses: the first turns the row into a question, and only the button answering it reaches GitHub. The merge question offers all three methods, so choosing Squash and merge is the same press as confirming. Whether the merge may happen is GitHub’s answer, and its refusal is shown in the row.

⌘U pins a pane’s pull request from a URL on the clipboard, ⌘O opens it, ⌘⇧Y copies its link, and ⌘R re-fetches an open pull-request pane. Every PR link the window opens — a ⌘click in a pane, a row in the Inbox or the Fleet, a link an agent answered with — follows Settings → GitHub → Pull request links: a pull-request pane or your default browser. Other web links always open in your default browser.