Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The official October 14 update lists x86_64 Linux support with AppImage, deb and RPM packages; it does not announce Linux ARM support.
- Remote Control is restricted to membership tiers that include Kimi Code benefits, and the remote device must use the same Kimi account as Desktop.
- The host must stay awake, online and running Desktop. Closing the remote page does not stop a task still running on that computer.
- Version 1.1.0 also adds File Tree. Progress updates under Lab are experimental and apply only to newly created sessions.
Linux support: check the architecture and package first
Kimi Code's official October 14, 2026 update specifies x86_64 Linux support for Desktop 1.1.0, with AppImage, deb and RPM packages. The Quick Start also lists macOS, Windows and x86_64 Linux.
Before installing, confirm your computer's architecture and choose a package suited to your system. The release entry does not provide Linux ARM support or a complete distribution and operating-system version matrix, so Linux support alone does not establish compatibility with every Linux device.
Separate model access from Remote Control eligibility
On launch, you can follow the Kimi OAuth sign-in flow. If you skipped it earlier, open the account area at the lower left. The Quick Start specifies kimi.com for mainland China and kimi.ai for other regions. Different sign-in sites do not establish identical model or service eligibility in every region.
Official Kimi models require a Kimi membership, and the available models vary by plan. After signing in, check the Composer's model picker and Settings for the models and permissions available to your account; the account area shows plan usage.
Remote Control has its own requirement: your membership tier must include Kimi Code benefits, and your account must have access to the feature. Desktop also supports configuring a third-party model provider, but that model connection does not establish Remote Control eligibility.
Connect in order: enable the host, then sign in on your phone
First, sign in to Desktop on the computer that will run your tasks and confirm that the account has Remote Control access. Keep the computer awake, connected to the network and running Desktop. Leaving your desk does not mean the host can shut down or sleep.
Second, open Settings → Remote Control and enable it. The page displays a QR code and access link for that computer. These are remote access entry points: keep them private and do not forward them to other people.
Third, scan the QR code with your phone, or open the access link in a browser on a phone, tablet or another computer. If the remote page is signed out, sign in with the same Kimi account used in Desktop, then follow the page's prompt to turn on Remote Control.
Fourth, select an existing session on that computer to watch progress, send follow-up instructions or handle approvals. You can also create a session and send a new task. For a first connection, consider a small read-only question, such as asking the Agent to summarize the project directories, before choosing the next action.
Handle approvals on your phone while project operations stay on the host
A remote session can show execution steps, expand tool inputs and outputs, and approve or deny file edits, Shell commands and other confirmation requests. Read the proposed action before approving it. The remote interface also lets you interrupt or stop a task.
Project file access and edits, Shell commands, local MCP servers and other local tools run on the computer hosting Desktop. Your phone is a control window; it does not move that development environment onto the phone, or establish that every model request and data transfer stays on the host.
Closing the page, ending access and stopping a task are different actions
Closing the remote page on your phone leaves tasks that are still running on the host in progress. To stop a task, use the session's stop control. To end remote access, disable Remote Control in Desktop settings; quitting Desktop also turns off remote access.
Under Settings → Remote Control, Remote device management lets you check device status and use an individual device's menu to rename it or take it offline. If a remote connection is unavailable, first check that the host is awake and online, Desktop is running, and both devices use the same account.
File Tree and experimental progress updates are also included
The new File Tree in the right sidebar browses, searches and refreshes workspace files, with click-to-preview. Toggle it with Cmd + Shift + E on macOS or Ctrl + Shift + E on Windows and Linux.
Experimental progress updates can be enabled under Settings → Lab, but apply only to newly created sessions. With Kimi Code CLI installed, kimi app opens a new Desktop session in the current directory, or you can pass a path for a specific workspace. This terminal route is optional for Desktop users.
Sources
Frequently Asked Questions
Can I use these packages on a Linux ARM computer?
The official update explicitly lists x86_64 Linux; it is not an ARM support announcement. Check your device architecture and the applicable download requirements. These three sources do not provide Linux ARM support or a complete distribution compatibility list.
Why might Remote Control remain unavailable after connecting a third-party model?
Third-party model configuration and Remote Control have separate requirements. The Quick Start allows adding a model provider, while the Remote Control guide requires a membership tier with Kimi Code benefits. Being able to use a model does not, by itself, establish remote access eligibility.
Does host-local tool execution mean code and conversations never pass through a cloud service?
That does not follow from these documents. They identify where project file operations, Shell, local MCP servers and other local tools execute. They do not promise that all model requests, conversation content or data transfers avoid cloud services. Check the data-processing scope of the model provider and features you actually use.