Uses your ChatGPT plan (Plus, Pro, Team…) through OpenAI's device sign-in, entirely in this tab. The tokens stay in this browser; model requests pass through the AI proxy because chatgpt.com does not accept browser origins.
An AI session sees your machines and sessions, reads screens, types commands and waits for output, all through this browser's connection to each daemon. Each AI session is its own conversation; start as many as you like from This browser in the rail (Ctrl+Shift+A). Try: “what is running in session 1?”, “start a shell on my laptop and run the tests”, “watch the build in session 3 and tell me when it fails”.
Access ·
Browsers exchange a short-lived ticket for a credential, SSH clients fetch a certificate; both are signed by this machine's key and nothing is kept there. webmux rotate-key on the machine revokes everything at once.
Browser credentials last 7 days. Save this machine to a passkey and one touch refreshes them, on any browser your password manager syncs to, without a ticket. The passkey's public key is certified by this machine; the certificates live inside the passkey (largeBlob). Nothing is stored here.
One command enrolls an SSH client: run it there within 10 minutes. It fetches a certificate for the key you connect with, through the relay, and prints what to do next. Nothing is kept here to revoke; webmux rotate-key on the machine invalidates every client.
Danger: an AI session wants to run code in this page
The AI session asks for permission to run arbitrary JavaScript inside this browser tab. Its reason:
If you allow this, that AI session can do anything this page can do, until you reload the page or revoke it:
read everything stored in this browser for webmux: your machine credentials and tickets, your ChatGPT tokens, every AI transcript, queued feedback;
type into any session on any connected machine, and create, rename or kill sessions, as you;
send anything it reads to any server on the internet;
change what you see on this page, including what other AI sessions appear to say.
This exists for debugging webmux itself. Deny unless you asked the AI to do this and you understand the risk. Every run will be shown in the transcript with its code.
Feedback
Reports queue here: an AI session files one when it runs into a bug or when you ask it to, and you can write one below. Nothing is sent until you approve the whole batch; open a report's context to see exactly what would go with it.
Where approved reports go
The broker files each report as an issue in a private repository, signing in as a GitHub App whose key lives in AWS KMS. Leave empty to only copy Markdown.