Keyboard and mouse

Plans and replies open in the Thread view. Open Keybinds from the menu to see this list in the terminal.

Two modes: type and nav

The thread has two modes, and the footer always says which one you are in.

• Type is the default. A letter opens a comment on the mark, or on the word under the caret. This is the primary act, so it needs no key to reach.
• Nav is where the structural commands live. Press esc to enter it; the footer switches to the nav commands. Now a bare letter runs a command instead of typing. Press c (or just start typing) to return to type mode.

esc always heads toward nav, so it never strands you: from typing it enters nav, and in nav it drops the mark or a focused comment without leaving. There is no leader chord and no modifier - a plain letter reaches cueloop through any terminal, so there is no setup.

The footer lists only the commands the surface under the caret can run. The Welcome tab and a file opened from the Project tree have no review behind them, so their nav mode offers c comment and z fold; any other letter types.

Marking text

A mark is a character-precise stretch of text. It can start in the middle of a word and run across wrapped lines and across blocks - from the tail of a paragraph into the bullets under it.

Input	What it does
click	place the caret
drag	mark from the press to the pointer, across blocks
double-click	mark the word under the pointer
← / →	move the caret by word; it flows across blocks
shift+← / shift+→	hold a mark from the caret
↑ / ↓	move the caret by block
esc	enter nav mode; in nav, drop the mark

Commenting

Input	What it does
type	open a comment on the mark, or on the word under the caret
enter	reply to the comment under the caret
esc	enter nav mode

Inside a comment:

Input	What it does
cmd+enter	send (ctrl+enter works where the terminal keeps cmd)
enter	new line, kept as typed
backspace on an empty draft	dismiss the draft; the mark stays
/	the actions palette
esc	dismiss the draft
click away	save the draft

A comment on a mark that spans blocks anchors to the whole stretch: its quote carries the text of every block it covers, and the card sits under the last one.

Nav mode commands

Press esc first (the footer switches to the nav commands), then a bare letter.

Input	What it does
c	comment on the mark (returns to type)
e	edit the plan body in the inline editor
s	share the plan
enter	open the submit card
n / p	focus the next or previous comment
x	cut the block under the caret
u	restore the last cut
r	rename a collaborator
backspace	delete the focused comment
z	fold or unfold the comment under the caret

The session commands also have Ctrl accelerators you can press without leaving type mode: cmd+enter (or ctrl+enter) opens the submit card, ctrl+e edits, and ctrl+s shares. Nav mode is the discoverable path; these are the shortcut.

Panes and focus

The workbench has four panes: Threads, Thread, Changes, and Project. One pane owns the keyboard at a time; click a pane to focus it, or press tab (shift+tab for the previous) to cycle. Only the focused pane responds to its keys, so moving through the Threads sidebar never moves the caret in the editor. While a comment composer is open, tab belongs to the composer (it accepts the highlighted / palette entry); save or dismiss the draft to cycle panes again.

Diff reviews

A diff review reads the diff sheet in the Thread pane. Enter nav mode with esc, then act on the row or file under the caret.

Input	What it does
x	reject the change under the caret
u	restore the last rejection
c	collapse the file to its band
d	split or stacked layout (when wide)
k	start the guided walk

In the guided walk, ] and [ step through the files and esc leaves it.

Session history

The session's history - revisions, checkpoints, and branches - is carried behind these nav-mode commands. They act on the current path:

Input	What it does
g	go to the entry: switch to its branch, or move back
b	start a branch at the tip
l	label the tip as a checkpoint
f	fork the path into a new session
h	fork and hand off: share the fork

These are the owner's; a collaborator reads.

Quit

ctrl+q quits from anywhere - the one chord cueloop keeps, since terminals deliver it reliably and it never collides with a multiplexer prefix.