What an agent can do: worktrees, bells, wait_for_files, actions
To-do deadlines from agents; API reference
Notes: what an agent can do with them; the client's note methods; API reference
rename_desk: the desk you are in
A desk's folder from an agent or a team
Plugin: the update dialog; update_plugin and reload_plugins as requests
What an agent can do: close_desk, as a request
Settings → Agents: any request let through without the tap; Restart closes the desk's gone windows
Files like a file manager; pinned windows; gone windows closed at once; a team's sessions in Sessions; how a team lays out its desk
Teams: Pause, Stop, Reset, Restart — and reset: in the team file
The corner: messages stacked bottom right, faded after the time set; questions wait there until answered
Requests wait over the desk; a desk made for an agent is never lost to a page's save
The audit of every page against the code: what was wrong, what was missing, the API reference generated
Six readers went through every line and checked it in the code. Corrected: capabilities (agents
request what their key cannot do), counts, ports, HTTPS (a section of its own), the journal,
Teams (gates, BLOCKED, DONE, ids, YAML keys, warnings, files on disk), the key bar, {folder},
Settings rows, Files and Documents details, the System screen, contradictions between pages.
New: API reference, every route generated from the code (scripts/apiref.py).
What an agent can do: the whole table — by itself, with your tap, not at all — and request