docs: add closed-browser notifications
Document the new viewers config section: per-kind size caps and forcing a kind
Drops can be told to forget
Dropping a file onto a session
The System screen tells you where you are, and what the proxy hides from a service
Three pages behind the code: the addresses panel, what a port's twist shows and why the link
carries its token, and the two routes underneath. Plus the part worth writing down for anybody
proxying anything — which of your credentials reach the service, and that the answer is none.
Document what the last few days added, and make every file mention a link
The wiki names files constantly and none of them were clickable: it is a separate repository, so
a relative path never reaches the code and it has to be an absolute URL. Eleven of them now are.
And the content had fallen behind the app: the workspace on the machine and what that unlocks,
the Python client and why it is one file rather than a package, the to-do list, fetching a link
into a folder (with the pasted curl), the caption under a document, sending a window behind, and
the brakes — which the page still described as six a minute, from before the fan-out of four
referees and an editor proved that wrong.
Starting an agent: a page for it, and the launchers config key
The docker line, with a variable bash will let you set
Three ways to install it, which machines it runs on, and every flag
Say where the documentation lives, in the app