The window is not where the work lives
Coding agents that keep working after you close the laptop. A session runs on a host — your machine, or a server over ssh — and every window, browser tab and terminal is only a client of it.
The browser client drives a host you already run. If you have one, paste the link it printed and you are in; if you do not, the app says how to get one. Nothing is uploaded anywhere — the page talks to your machine, not to this site.
One process owns the work. Everything else is a view of it.
Most agent tools put the loop inside the application, which makes closing the window a decision about the work. Here the application holds no session state at all.
Closing the app mid-run, driving one session from a second machine, and resuming after a restart are not three features. They are three consequences of that one arrangement.
The run outlives the client
Quitting does not stop a turn. Two machines on one session see one transcript, and a permission prompt raised on either is answerable from the other.
Everything resumes from its log
Which agent ran, under which model, what it did, who approved each thing it needed. A moved folder, a switched provider and a restarted machine are one problem rather than three.
Sessions can work as a team
Group them and they reach each other — a short message that wakes the other session, or a read of what it has actually been doing. From the desktop or from a terminal.
Every session on every attached machine, ranked by who needs a human
One command where your work is
A host is whatever you run this on — your laptop, or a server you reach by ssh. It prints a link; that link is what the browser client wants.
agbrte web .
The link carries a token, and the socket admits nobody without it. The address still decides who can reach the host at all, which is why it binds to loopback unless you name something else.