Remote Control

Remote Control links a live Syntic Code session to another device, most often your phone, so you can watch a long-running task and respond to it without staying at your desk. Amara frequently pauses to ask for a decision, confirm a risky action, or report that it is finished. With Remote Control those prompts arrive on your paired device, and you can approve, redirect, or answer them from anywhere.

Pairing a device

Start Remote Control from inside a session and scan the pairing code with your device. The link is bound to that specific session and expires when the session ends, so there is no standing connection to manage.

# In an interactive session
/remote
 
# Or start a session with remote control enabled
syntic --remote

Once paired, your device shows the live transcript. When Amara needs input, the pending question appears with the same choices you would see in the terminal.

What you can do remotely

From a paired device you can read the ongoing transcript, approve or deny permission prompts, send follow-up instructions, and stop the session. Actions taken remotely are reflected in the terminal immediately, and vice versa, so you can hand control back and forth. This is especially useful for tasks that run for many minutes, such as a large refactor or a test suite the agent is iterating on, where you want to step away but still unblock the agent the moment it asks.

Security and scope

The pairing link is short-lived and scoped to a single session; it grants no access to your filesystem beyond what that session already has. All traffic flows through api.syntic.ai over an encrypted channel, and closing the session or ending the pairing immediately revokes remote access. For shared or sensitive work, end pairing as soon as you no longer need it, and avoid pairing on devices you do not control.