Remote Control keeps Kimi Work’s agents within reach

Remote Control lets users access Kimi Work tasks from a phone, while execution and file access remain on the computer.

A report is still being drafted, several agents are processing documents, and an approval request is blocking the next step. Users no longer need to remain at their computer to check progress. Remote Control opens Kimi Work sessions on a phone and provides a way to take back control from a distance.

The feature announced by Moonshot AI does not move the work to the phone. Kimi Work continues running on the computer where the task began. The mobile device serves as a remote interface for monitoring the session, sending new instructions, and intervening when a decision is required.

This architecture distinguishes Remote Control from a fully cloud-hosted agent. Files continue to be read and modified on the original machine, commands run there, and local tools remain available. The computer must therefore stay powered on, connected to the internet, and awake enough to maintain the session.

Closing Kimi Work, shutting down the machine, or allowing it to enter sleep mode breaks that continuity. The phone does not take over or receive an independent copy of the environment. The promise of working “anywhere, anytime” still depends on the computer left behind remaining available.

Kimi Work is Moonshot AI’s desktop agent for office and knowledge tasks. Available on macOS and Windows, it can access authorized folders, organize files, analyze data, create documents, spreadsheets, or presentations, use a browser, and run code in the background.

The application can also divide a project among multiple subagents. Moonshot advertises support for up to 300 software agents on the most complex assignments, with tasks potentially running for several hours. The longer an operation lasts, the more useful it becomes to monitor it without remaining in front of the screen.

Remote Control primarily addresses that need. A user can start an analysis at the office, leave, and check its progress from a phone. They can correct an instruction, provide clarification, or respond to a confirmation request before the agent continues.

Its value goes beyond watching a progress indicator. Remote access becomes particularly useful when a sensitive operation is waiting for approval. Kimi Work offers three permission levels that determine how much freedom the agent receives.

`Default` runs routine operations but requests approval before certain actions, such as modifying or overwriting files and executing code. `Manual approval` asks for authorization before taking action. `Fully automatic` allows the agent to proceed without requesting confirmation at every step.

The phone can prevent a task from remaining blocked for hours under the first two modes. This remote intervention preserves human supervision without forcing users to select the most permissive setting simply because they plan to leave the computer unattended.

The issue matters because Kimi Work does more than generate text in a conversation. It can write to local folders, run commands, use plugins, and operate a browser. A poor instruction can therefore have more serious consequences than an incorrect answer in a chat interface.

Moonshot warns that fully automatic mode can overwrite or delete files, change system settings, and, in extreme cases, make a device unstable. Remote Control does not remove these risks. It simply provides another place from which to monitor or interrupt execution.

The announcement is brief and does not describe every command available through Kimi Work’s mobile interface. Moonshot had, however, introduced a closely related feature in Kimi Code CLI in late August. Its documentation indicates the technical approach being used, without guaranteeing that every setting is identical in the Work application.

In Kimi Code, the machine generates a remote URL and QR code. The user then opens the page on a phone or another computer, signs in with the same Kimi account, and selects the relevant machine. Access goes through a Moonshot relay rather than exposing the computer directly over the local network.

This remote interface can send new tasks, monitor tool usage, continue a conversation, approve or deny operations, interrupt execution, and review subagent activity. Computation and file changes remain on the original machine.

The approach announced for Kimi Work follows the same separation: the computer does the work and the phone controls it. It should not be confused with remote desktop software capable of displaying the entire operating system, freely opening every folder, or controlling any installed application.

Remote Control exposes Kimi Work’s functions, not the entire Windows or macOS desktop. This restriction narrows the scope of access, but the agent retains the permissions already granted in its local session. If Kimi Work can modify a folder or control a browser, an instruction sent from the phone can trigger those same operations.

Authentication therefore becomes a central concern. In the system documented for Kimi Code, the phone must use the same account as the machine. Moonshot states that the URL contains neither session data nor a local token and that someone who is not signed in to the account cannot view the tasks.

The company still advises users not to share the address. It provides an entry point to a machine capable of accessing files and executing commands. A poorly protected account or a session left open on someone else’s phone could create a much broader risk than simply exposing a conversation.

Stronger account authentication and locking the phone therefore become as important as the permissions configured on the computer. Folders made available to the agent should be restricted to what the task actually requires, especially when Remote Control is used with a high level of autonomy.

The word “local” used to describe Kimi Work also needs clarification. File operations, browser activity, and commands run on the computer, but the service is not entirely offline. Model requests and session synchronization require access to Kimi’s services.

The