In July we introduced cloud brains, local hands: dispatch from Aii Cloud and run the tools on a machine you own.
The next step closes the loop. You can now start the conversation in Aii CLI, open that same session in Aii Cloud, and keep talking to the same running process from the browser.
Not a copy. Not a second agent. The same session, workspace, and execution boundary.
Start the session once
On your laptop, VPS, or container:
npm i -g @aiiware/aii
aii cloud login
aii --remote-control --inference cloudAii prints a Cloud link. Open it and the terminal conversation is available in the browser. Send a follow-up there and it enters the same session queue on the connected machine.
The --inference choice is independent:
--inference clouduses AiiCloud inference, as in the example above.--inference serveruses an Aii Server you have configured.- Omit it to use the saved preference.
Remote control decides where you can continue the conversation. It does not silently decide where inference runs.
Approval follows the action
When the agent wants to run a command or write a file, the approval can appear in the browser and terminal. The first valid decision wins, and the transcript records where it came from.
A cached terminal grant does not silently authorize a new browser-originated turn. Browser approvals are serialized so two permission cards cannot race each other, while already approved tools may still execute concurrently.
Structured questions travel too. If the agent pauses on a choice—database A or B, overwrite or create, narrow or broad—you can answer from the browser and the same terminal session continues with that decision.
See what the machine made
When the local agent creates a supported HTML deliverable, Aii can show a private preview in the Cloud workspace. You can interact with it, reload the conversation, and download the result without changing the original file on the machine.
That makes remote control useful for more than watching logs. You can inspect the output, approve the next step, and ask for a revision while away from the terminal.
Stop safely, resume deliberately
Sessions are saved locally with an identity and recovery state:
aii sessions list
aii sessions info <full-id>
aii resume <full-id> --remote-controlResume from the original workspace on the original machine. A safely stopped session can restore its context and AiiCloud conversation. A turn with an uncertain execution outcome is not automatically replayed; Aii asks you to recover or inspect it instead of guessing whether a command already ran.
Inside a running session, /remote off disables browser control and /remote on enables it again. Turning it on does not upload earlier private terminal messages into AiiCloud.
The terminal is still the computer
The browser is a control surface. Filesystem access, shell execution, local credentials, and the toolchain remain on the connected machine; Aii does not upload the computer wholesale. Prompts, assistant text, and tool results needed for a turn still travel through the conversation and inference path you selected, so secrets should stay out of prompts and command output.
The process has to remain running for live control, and every action remains inside that session's normal permission model.
That is the principle behind the feature: move the conversation without pretending the computer moved with it.
The former aii cloud connect, --remote, and --local entry points were pre-GA and have been removed. Use aii --remote-control and choose inference separately.