Skip to content

Panel and keys

The panel under the conversation, then the console.

The panel lists the shells of the session you are in. A project’s shells all mixed together is how the panel stops making sense, so switching conversations changes what you see — without stopping anything. Press s in the console to widen it to the whole project and back.

A dock under the chat with a tab per shell, the selected shell’s live screen, and the health of each one at a glance. ui.dockHeight sets how tall, ui.dockOpen whether it starts open.

Full screen, one shell at a time.

KeyDoes
iType into the shell
tabSwitch between the screen and the agent’s numbered log
/Filter the log — matches highlighted, line numbers kept
?Details: command, folder, timing, watcher, log file
[ ]Previous / next shell
sThis session only, or the whole project
r · x · cRestart · stop · interrupt
nStart a new shell yourself
escBack to the conversation
240 lines down to the four that matter.

Filtering happens in the daemon, so a 40,000-line dev server costs nothing to search.

/shells-stop stops the shells you are looking at; /shells-stop-all stops every shell in the project and asks first when that includes conversations you cannot see. /shells toggles the panel, /shell opens the console, /shell-new starts one, /shells-clear forgets finished shells, /shells-restart-daemon replaces a daemon running older code. Rebind them under ui.keybinds.