ShiftStage
Not «you can check things remotely». Specific situations, each of which otherwise ends with you opening a laptop.
AI sessions
You handed it a refactor and left. Ten minutes in it wanted to touch a file it was not sure about, and asked. Nobody answered — so that is not a pause, that is the rest of the run, cancelled. Here the question reaches your phone the moment it appears, with the command and the risk spelled out, and a tap puts the run back in motion.
Git · diff
Twelve files touched. Two are exactly what you asked for. One is a rename it threw in for tidiness. One edited a test until the test passed. You read that the way you would at the desk — real diff, syntax colour kept, changed fragments marked inside the line — then stage the three that are right, discard the test edit, and send the rest back with one sentence.
Files · preview
You asked for an analysis written to a file. Reading it should not mean downloading it into a folder you will forget about — it opens rendered, with the raw source one tap away, and nothing is left on the phone unless you say so. Then: keep a copy that opens later with the Mac asleep, or send it straight out of the share sheet to whoever is waiting for it.
Files · transfer
Friday's export, a signed build, the document a colleague needs in the next ten minutes. It is in a folder you could point to with your eyes closed, and you are two hours from it.
Git · history
Something behaves differently and nobody remembers touching it. You do not need the whole repository on a phone — you need the last twenty commits on that branch, who wrote them, and the diff of the two that look guilty. Filter by author, by file, by message; open the commit; read it.
CI · notifications
Forty minutes later the phone says it failed — and says what it failed on, not just that it did. Before, that was a problem for tomorrow, or a laptop opened on a restaurant table.
Processes
A dev server that survived the tab you closed. A test run that will not end. A process that has been eating a core since lunch and is heating a machine nobody is sitting at.
CI/CD
This is the one part of ShiftStage that needs no Mac at all: the phone talks to the provider directly. A release to cut from a moving train, a nightly to kick off again, a deploy stage waiting for somebody to approve it.
CI · logs
Build logs are the worst thing to read on a small screen, and every other tool hands you a web page to pinch-zoom.
▾ Build and test 2m 14s
✓ Compile 128 targets
✓ Run 1 412 tests
▾ Package 41s
✗ notarytool: invalid credentials
→ jump to this line in the log
▸ Upload artifacts skipped
Connection
At home the phone and the Mac talk directly over the local network, with no server of ours in the path at all. Walk out, and they still connect directly whenever the networks allow it; when the networks refuse, a relay forwards a stream it cannot read. You can see which path you are on, and you can forbid the third one.
Access log
Remote access without a record is trust by assertion. The agent keeps a log on the Mac: every operation a connected device asked for, when, which device, and how it ended — with the subject named by the request itself.
Everything above is what we thought of. The list does not end there, because the terminal is a real one — a PTY on your machine, not a sandbox of ours.
Your scripts, your aliases, your build tools, your automations, the dotfiles you have been carrying between machines for a decade. If it works on your Mac, it works from your phone — and none of it passes through us on the way.
sudo, released by Face ID.It does not mirror your desktop, does not move your work to a server, and does not put a model between you and your code. The Mac stays the machine that does the work.
Eleven situations.
Seven dollars a month.