Closing the lid stops the work. Nothing is lost. It resumes where it stopped.
We do not promise work continues while your machine is closed, because it does not.
The work runs on your machine. This is just the window.
Sign in here, connect a machine you own, and work. Your answers and your files are written to that machine’s disk. We keep four things: your email, your machine’s address, when you connected it, and a name you chose.
Sign in with an email code No password — so there is nothing here to steal.
Where things go
you ──▶ rig.rest your account: four things, never your work you ──▶ your machine everything else: answers, files, pictures
The second line never touches us. Nothing here forwards your work, and nothing bigger than 4 KB can be posted to this site at all — a conversation does not fit through it. Your machine never has to accept an incoming connection either; it dials out.
The technical version
The browser talks directly to your agent over your own tunnel, which forwards to a port bound on loopback (127.0.0.1:8780) on your machine. No inbound port is opened, and no flag widens that binding. The portal holds account metadata only and has no route that proxies a turn, a model call or a byte of your work.
Getting set up
- Sign in. A six-digit code by email. It lasts 24 hours, and your machine keeps it alive by checking in.
- Install it on your machine. One command. It tells you what it will do before it does it, and what it wrote afterwards.
- Choose one folder. That folder is the only one it can touch — nothing outside it is read, written or looked at.
- Add a model, with your own key. You place your key yourself. Nothing here ever sees it. It reads not connected yet until one real call proves it works — a saved key is not a connection.
- Watch your first picture draw itself. Not a sample: your own work, drawn on your machine, with no model involved. If there is almost nothing there yet, it says so and draws it anyway.
Things we would rather you heard from us
We cannot email just anyone yet
Until we finish onboarding a sending domain on a paid plan, sign-in codes only reach addresses verified on our account. If that is you, the sign-in page says so plainly instead of failing.
a limit of ours, not a fault of yoursIf access is ever cut off
Revoking access removes the portal, the tunnel and the interface immediately, and disables the agent at its next check-in (within 24 hours). It does not reach into a machine we do not own — and it never touches your files.
Code on a machine we do not own cannot be made truly unusable. A determined person can patch the check out, and we are not going to pretend otherwise.