Remote control for coding agents
Your coding agent, in your pocket. And in the cloud when you close the lid.
Jaywin drives Claude Code or Codex on your Mac from your phone. Approve a tool from a push, take over a session from anywhere, and send it to a cloud machine when you need to leave. It comes back when you do.
- PhoneApprove, take over, start
- Your MacRuns the agent
- CloudKeeps going while you are away
It stays quiet until something needs you
Approve from a push
A permission arrives as a notification on your phone or your watch. Allow, allow for the session, or deny, without opening a laptop. The rest of the time Jaywin stays quiet.
Take over from anywhere
A session you started in the terminal shows up on your phone. Tap Take over and keep typing where you left off. The transcript stays on your Mac.
Continue on your Mac
Tap Continue on your Mac, or run rc attach in any terminal, and the session is a live Claude Code window again. A sleeping Mac leaves it waiting, never stranded.
What people ship with it
Never run a coding agent? Start with one of these.
Each card is a real prompt. Paste it into a new session, approve what the agent asks for, and the result comes back to your phone.
You
Build a waitlist page with Stripe checkout and email me when someone pays.
A SaaS, end to end
Start it from the train. Approve the Stripe key step from your phone. Review the pull request from the couch.
You
Make a dashboard of this week's signups, revenue, and churn from our Postgres.
An internal dashboard
Send it to the cloud before you leave the office. Wake up to a preview link.
You
Change the hero copy to the new tagline, bump the font size, deploy to Vercel.
A landing page fix
Twenty seconds on the phone, before the coffee cools.
You
Users report 500s on checkout. Find the cause in the logs and patch it.
A 2am production fix
The push wakes you, you take over, you approve the deploy, you go back to sleep.
You
Add dark mode and a settings screen to my Expo app.
A side project that stays alive
Twenty minutes a day, from anywhere, on a Mac that sits at home.
You
Update the pricing table on the client's site and send me a preview.
Client work, on site
Every client repo on one phone. Permission pushes go to whoever owns that project.
Your Mac stays the machine. Your phone is the remote.
- 1
Install rc on your Mac
One command. A small daemon runs under launchd and watches the Claude Code sessions you already run.
- 2
Scan a QR from the app
Pairs the phone to this machine with a per device token. Add as many Macs as you like.
- 3
Your sessions appear
Start one in any repo, watch one that is already running, open a raw shell. Push arrives when Claude needs you.
A small relay routes frames between your devices and delivers push. Transcripts and working trees stay on your machine unless you move a session to the cloud yourself.
Cloud handoff
Close the laptop. The session keeps going.
Tap Do this in cloud. Jaywin packs the working tree and the transcript, starts a machine that is yours, and resumes the same session there. Your Mac can sleep.
- The machine signs in as itself. Your Mac’s credentials never leave it.
- Everything comes back. Commits, files, screenshots, renders. If your Mac moved on meanwhile, the return lands on its own branch and never clobbers your tree.
- Same phone, same session. Approvals, takeover, and push work exactly the same on a cloud machine.
Work layer
Not just a remote. The place your agent work lives.
A task card is a prompt with a home. Tap Run with Claude, watch it work through the steps, get the result back on the same card.
Task, run with Claude
- Reproduce the flaky webhook test
- Fix the retry timer race
- Run the suite
- Push a branch and open a PR
- Report back on this card
Task board
Cards that start sessions. Tap Run with Claude, get the result back on the card.
Notes
Per repo and per session. The thing you noticed at lunch is there when you sit down.
Reminders
Time based or tied to a session finishing, delivered over the same push pipeline.
Memory
Edit a memory file on your phone. The daemon syncs it into each repo’s CLAUDE.md.
Skills
A curated library you install onto any paired machine from the app.
Prompts
Saved and curated prompts that prefill a new session in one tap.
Mac app
A native Mac app with terminals that do not forget.
Swift, not Electron. Sessions, the work layer, and a terminal per session. Leave a tab and come back later, the shell is still there with its scrollback.
Also in the box
Built for the whole day, not just the demo.
Codex too
Claude Code and Codex on the same phone, the same daemon, the same push. Pick the agent per session.
Approve from your watch
A permission lands on your Apple Watch. Allow or deny from your wrist without finding your phone.
Team sharing
Share a Mac or a cloud machine with your team. A junior starts the session, a senior gets the push and taps Allow. Every decision is logged.
10,000 screen UI library
A reference library of real app screens, searchable from your phone and attachable to any prompt or task card in one tap.
Our models or your keys
Use managed models with nothing to set up, or bring your own Claude or OpenAI key and pay nothing extra for tokens.
Persistent terminals
Every session has a shell that survives leaving the tab, on the phone and in the Mac app.
Compared
Remote control is table stakes. The rest is not.
Anthropic ships a free remote control inside the Claude app. Happy and Orca are excellent open source remotes. Jaywin is for the part of the day that starts after you leave the desk.
| Jaywin | Anthropic | Happy | Orca | |
|---|---|---|---|---|
| Native phone app with push | Yes | Yes | Yes | Yes |
| Your own Mac as the runtime | Yes | Yes | Yes | Yes |
| Native Mac app (Orca ships Electron) | Yes | No | No | Partly |
| Persistent terminals | Yes | No | No | No |
| Session moves to a cloud machine and back | Yes | No | No | No |
| Push a phone session back to the Mac (Happy: press any key) | Yes | No | Partly | No |
| Tasks, notes, reminders, memory, skills | Yes | No | No | No |
| Claude Code and Codex (Anthropic: Claude Code only) | Yes | No | Yes | Yes |
| Apple Watch approval | Yes | No | No | No |
| Team sharing with approval delegation | Yes | No | No | No |
| 10,000 screen UI reference library | Yes | No | No | No |
| Managed models or your own key (others: your own subscription only) | Yes | Partly | Partly | Partly |
| Transcripts stay on your device (Anthropic keeps them server side) | Yes | No | Yes | Yes |
As of August 2026, from public docs and repos. Tell us if something changed.
Pricing
Free on your own Mac. Pay for cloud hours when the work has to keep going without it.
A cloud hour is an hour your cloud machine is awake. It stops itself fifteen minutes after you do. Claude stays on your own plan.
Free
Run Claude Code on your Mac from your phone
- 1 Mac
- 3 open sessions
- Notes, tasks and reminders
- Skills marketplace
- Ask and Auto permission modes
- Push notifications
Standard
Take your work with you
- Everything in Free, plus
- 3 Macs, unlimited sessions
- 60 cloud hours a month
- 1 cloud machine, 8 GB
- Workspace kept 30 days after idle
- Yolo mode
- $0.15 per extra cloud hour
- Email support
Pro
Your own always on AI workstation
- Everything in Standard, plus
- Unlimited Macs
- 600 cloud hours a month
- 3 cloud machines in parallel
- Performance CPU, 16 GB
- Workspace kept 180 days
- Up to 5 seats
- $0.10 per extra cloud hour
- Priority support, one business day
Enterprise
Teams that need control
- Everything in Pro, plus
- Per seat pricing
- SSO and SAML
- Admin locked permission policy
- Audit log
- Private skill repos
- Dedicated cloud region
- Invoicing and an SLA
Free for everyone on the waitlist during the beta. Extra cloud hours are billed at the end of the month, never mid session.
Do I need a Claude or OpenAI subscription?
Bring your own Claude subscription or OpenAI key and pay nothing extra for tokens, or use our managed models, which are included in Pro. Either way Jaywin never resells tokens.
Does my code leave my Mac?
Not unless you move a session to the cloud yourself. A small relay carries chat frames between your devices and delivers push. Transcripts and working trees stay on your machine. When you tap Do this in cloud, the working tree and transcript go to a machine that is yours, and you see exactly what is packed before it leaves.
What happens when my Mac sleeps?
A session on your Mac waits. If you want it to keep going, send it to the cloud before you close the lid. A session you hand back to a sleeping Mac waits there too, it is never lost.
Which agents work with Jaywin?
Claude Code and Codex today, through the same daemon and the same app. You pick the agent when you start a session.
Which devices?
iPhone, Apple Watch for approvals, and a native Mac app. The relay and the cloud machines are hosted by us.
Is there a free plan?
Yes. Free covers one machine, three active sessions, seven day history, and push. Everyone on the waitlist uses Jaywin free during the beta.
How does pairing work?
Run rc on your Mac and scan a QR from the app. Each phone gets its own token for that machine, and you can revoke any device from settings.
Can my team share a machine?
Yes. Share a Mac or a cloud machine, decide who can start sessions, and route permission pushes to whoever should approve them. Every decision is logged.
Get an invite.
We are letting people in a few at a time while the cloud side settles. Leave your email and we will write when it is your turn.