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
- Kimi Code CLI v2.5.0, dated November 4, 2026, adds SSH, Docker, and custom-command environments. The official entry gives no exact release time or timezone.
- Install the target-side executor first. Its default path is ~/.kimi-code/bin/kimi, and Kimi Code CLI does not install it automatically.
- Use --environment to create a session bound to a remote environment and --environment-cwd to choose an absolute target-side directory. Resuming a session restores its original environment and directory.
- File and Shell run on the target. Model requests originate locally, and credentials and session state remain local. WebSearch and FetchURL always run locally; hooks/stdio MCP servers without a bound environment do so by default.
- A Windows target needs Git for Windows and the Windows executor; Docker containers are unsupported there. The official pages do not specify CLI membership, regional eligibility, or fees.
CLI 2.5.0 runs File and Shell tools in a remote environment
The Kimi Code CLI v2.5.0 release entry is dated November 4, 2026. It adds SSH, Docker, and custom-command environments that you can bind to a new session with --environment. The entry provides a date but no exact release time or timezone.
File operations and Shell commands run on the remote target. The CLI remains on your machine, which sends model requests and retains credentials and session state. This changes selected tools’ execution location; it does not establish that all traffic uses the target or that code never reaches a model provider.
Desktop Remote Control lets a phone control a desktop session running on your machine. CLI remote environments instead point File and Shell at another host or container. For phone control, see https://puppyip.com/en/resources/kimi-code-desktop-110-linux-remote-control-guide .
Prepare the SSH target, then declare it on your machine
Install the Kimi Code executor for the target platform on the remote machine, normally at ~/.kimi-code/bin/kimi; the CLI will not install it for you. Your client should already be able to sign in with an SSH key. Use your local ~/.ssh/config for the user, port, or jump host as needed; do not put real keys or passwords in prompts.
In your local config.toml, add [environments.dev-box] with type = "ssh", host = "dev-box", and defaultCwd = "/home/me/projects". These host and directory values are examples; defaultCwd must be an absolute path in the target environment.
If the executor is outside its default location, set remoteBin in the environment entry to its path on the target. The environment configuration lives on your machine, and SSH resolves the host and authentication through your local SSH setup.
Use a new session to choose the host and working directory
Run kimi --environment dev-box to create a remote session. To override the directory for that session, run kimi --environment dev-box --environment-cwd /home/me/another-project; --environment-cwd must be used with --environment.
--environment and --environment-cwd are creation-only flags and cannot be combined with --session or --continue. Resuming an existing session restores its original remote environment and working directory. A later /new keeps the current environment instead of applying the startup flags again.
After a disconnect, the next tool call tries to reconnect; it never silently falls back to your machine. A tool call already running when the connection drops fails and is not retried automatically. Check the network, SSH, and target executor, then decide whether to submit the task again.
Docker, custom commands, and Windows targets have different requirements
Besides SSH, you can declare a Docker-compatible container or a custom launcher with command and args; one environment entry cannot set both type and command. defaultCwd must be an absolute path on the target for every environment type. Changing the launch configuration reconnects with the new settings on next use and stops running remote commands.
For a Windows target, install Git for Windows and the Windows executor, normally at ~/.kimi-code/bin/kimi.exe. Use a native drive path such as C:\work\project for defaultCwd. Windows targets support SSH and custom commands, but not Docker containers.
Check local tools, paths, and session limits
WebSearch and FetchURL always run from your machine. Hooks and stdio MCP servers without environment_id also run locally by default. Subagents inherit their parent Agent’s remote environment, but that does not route every tool to the target.
File paths in prompts resolve on the target, so a local path cannot be read directly by the remote environment. Tower mode cannot manage remote-environment sessions, and the local Git status footer is hidden in a remote session.
The CLI remote-environment documentation does not specify membership requirements, regional availability, or fees. Do not infer CLI access from Kimi Code Desktop Remote Control rules; check the current official account and plan information.
Sources
Frequently Asked Questions
Can the CLI prompt for an SSH password, MFA, or a private-key passphrase?
An interactive CLI can prompt for an SSH password when the server supports it, but password prompts require OpenSSH 8.4 or later. Separate OTP/MFA and private-key passphrase prompts are unsupported, and non-interactive clients such as kimi -p do not prompt; configure your SSH key or ssh-agent locally first.
Why can listing a very large remote directory fail?
The official guide lists a limit: directory listing fails when a remote directory contains more than 50,000 entries. Use a smaller subdirectory. That error alone does not establish a model-quota or membership problem.