What Remote Control is
Remote Control attaches a second client to a CLI session that's already running on your workstation. The session itself stays where it lives — with your code, your environment, your secrets — and you stream the input and output to wherever you happen to be. The AI Employee continues to dispatch Agents from the same machine; you're just driving from a phone or a browser instead of a terminal in front of you.
When you'd use it
- You start a long job before stepping away. Kick off a refactor or a research run from your workstation in the morning, leave for a meeting, check progress and answer follow-up questions from your phone.
- You want a senior engineer to weigh in mid-run. Share a session link, they attach, see the same state you see, and steer or approve a step without taking over your laptop.
- You're on a flight or a different machine. Your environment stays put; the lightweight client is whatever device you have in front of you.
Setting it up
Enable Remote Control in Syntic CLI settings (it's off by default). Sign in with the same Syntic account you use locally. Start a session as you normally would — syntic in the working directory of the project — and the session is now visible to any client signed in with the same account.
Attaching from another device
On your phone or second machine, open the Remote Control surface, pick the session you want to join, and you're in. You'll see the live transcript, the Agent's current step, the files it has touched, and an input box. Anything you type is delivered to the same Employee that's been doing the work all along.
Permissions and approvals
Sensitive actions still require approval. The Agent pauses, the approval prompt appears in whichever client is currently active, and you sign off from the device in front of you. If you flip between devices, the prompt follows.
Limits to know
The session is tethered to the host machine. If your workstation goes to sleep or loses power, the run pauses until you're back. File operations, network calls, and credentials all stay local — Remote Control is a steering wheel, not an upload of the work to the cloud.
Best practices
Use Remote Control for monitoring and lightweight steering. Reserve large prompts and complex follow-ups for a real keyboard when you can — the experience is better, and the Employee's responses tend to be tighter when you've had time to type the full context. For everything else, the phone surface is plenty.