resumed · 3 files in context
The retry test passes locally — the backoff was resetting on every attempt.
21:41
iPhone · macOS & Windows
It attaches to a session you already have open. Nothing is forked or copied — type on your phone and it lands in the same conversation you are looking at in VS Code, on the computer you left it running on.
you answer every approval · no VPN · no certificate · nothing in an app store
The retry test passes locally — the backoff was resetting on every attempt.
ssh staging-01 \ 'systemctl restart api'
Open a project from the train and its Claude Code tabs come back with it. Start something new and it is a tab in VS Code, waiting for you when you sit down. Nothing to turn on before you leave, and nothing to go and find afterwards.
every line above is something atdesk does — we make no claim about what other tools do or do not
Not a summary — the thing it is actually stuck on, with how much context is left so you know whether it can even finish. You read the reasoning, the command, and the diff it wants to write, then you allow it. The turn carries on where it stopped.
Bash · ssh staging-01 · 34% context left
a push, not a spinner
I need to restart the staging worker to confirm this.
ssh staging-01 \ 'systemctl restart api'
exactly what it wants to run
The next forty minutes are migrations and tests — nothing you want to approve one line at a time. Loosen it to Edit automatically so it stops asking about every file, and put it back to Manual the moment it matters again. You are still the one reading it.
Running the staging migration now — this is the long part.
You are not limited to answering the one that called you. Open a new conversation in a project that is already open, or a whole new VS Code window, on the computer at your desk — then watch it start, and steer it from the platform.
Running the staging migration now — this is the long part.
Your laptop, the machine in the office, a Windows desktop — one icon on your phone, and every conversation on each of them. Or set it to Auto and stop thinking about which one you are sitting at.
Running the staging migration now — this is the long part.
One figure in the VS Code status bar — how much context the session has left. Everything else is behind it.
payments-api
Phone: ✓ reachable through atdesk — 1 phone connected
Service: ✓ running (loopback only)
Phone typing: ✓ enabled (CDP 42211)
Click for actions
First you can see it coming — the number in the corner is how much room the session has left, counted rather than estimated. Then you can do something about it: a new session reads the old one's record and carries the reasoning across. Reading costs that session nothing — no message, no context spent, no interrupted turn — and it still works after that session has stopped.
The backoff was resetting on every attempt — the timer lived inside the catch.
Fixed, and the staging run is clean — 12 passing, 0 failing.
/atdesk-handover parks it · /atdesk-consult picks it up
vsr peerRead any other session on the machine — including one that has finished. It costs that session nothing.
vsr ask-sessionPut a question into another live session and submit it. With the atdesk skills installed, this one asks you to approve before it writes.
vsr new-sessionOpen a brand new session as a tab, in a project already open on the computer.
These are for Claude to run inside a skill, not for you to type. The commands are the small part. What atdesk actually installs is the practice: which session is which, how to tell two tabs of one project apart, and when to read the record rather than interrupt someone. /atdesk-consult and /atdesk-handover are plain markdown — read them, fork them, write your own.
There is no account to create and no password to choose, so there is no password database to leak. Your phone and your computer hold the keys between them, and your code never leaves your machine.
green: they get nothing useful · amber: they get something, and this is exactly what
No tiers, no per-seat maths, no add-ons. New features land on the plan you are already on.
card required · cancel in one click · tax at checkout
You need VS Code with Claude Code, opened at least once. There is one command, and it tells you what it is doing before it does any of it.
It appears on the next screen, and in your inbox.
We do not print it here on purpose. The command carries a digest, and a digest is only a real check if it reached you by a different route from the download — so it travels with your code, not on a public page. It checks your machine first and unpacks nothing until the digest matches.
Nothing is unpacked until it does. Then it stops and asks you — about the relay, and about the debugging port.
Your phone reads it, you check the same fingerprint appears on both, and you add atdesk to your home screen. That is the pairing done for good.
58fc 02c5 112a58fc 02c5 112aIf those two do not match, something is between you — so you stop. That check is the whole of the trust decision, and you make it once, in front of both screens.
no account · no VPN · no certificate to install
Not an editor on your phone — nobody has made that work well. It is the Claude Code panel inside the VS Code you already run, mirrored to your phone so you can read it and type into it. The editing still happens on your computer, where your files are.
Yes — Anthropic's own app has Remote Control, which continues a session you connected from your machine. atdesk is the other half: it reaches whatever is already open, opens projects and windows for you, and rejoins a conversation you had closed. Add it to your home screen and it behaves like an app, with no app store involved.
The one you have open. atdesk attaches to the session already running in VS Code, so it keeps the context that session has built up — and because it drives the editor rather than a connected process, it reaches the conversations you never set up for it, and the ones you had closed.
Yes, from anywhere. No VPN, no tunnel, no port forwarding, and nothing listening on your home network — your computer makes an outbound connection and everything between it and your phone is sealed end to end.
Yes — macOS and Windows, same install command, same phone app. One subscription covers up to five of your own computers.
No, and we will not help you to. atdesk is built so a person answers every approval — that is what keeps it inside Anthropic’s terms for your Claude subscription, and it is why there is no scheduler in here. What it removes is the need to be at your desk, not the need to be in the loop.
Yes. atdesk is an independent tool that drives Claude Code; it does not include or resell Claude.
Everything atdesk puts on your computer, and the one risk we cannot engineer away.