Skip to main content
Guides

Cloud Mode

--remote mode lets your Qoder CN CLI tasks run directly on cloud virtual machines managed by Qoder, without keeping your local computer powered on or active. The entire flow from issuing instructions to producing results is hosted in the cloud, with the local terminal acting only as an entry point. Complementary to the existing Remote Control mode.

Use Cases

  • Long-running tasks: Training, batch refactoring, large-scale code review — cases where it is inconvenient to occupy your local computer for a long time.
  • Offline kickoff: Write a prompt on a plane or subway, and check the results when you get back.
  • Consistent environment: Team members share a consistent set of dependencies and tools, avoiding "it works on my machine."
  • Resource isolation: Cloud VMs provide independent CPU / memory / network quotas that do not compete with your local machine.

Quick Start

1. Kick off a task in the cloud

Pass the --remote argument directly in the terminal: 
qoderclicn --remote "review the auth middleware in src/middleware and suggest improvements"
If you get a Cannot find package error during execution, switch to the HTTP API Quick Start and call the Cloud Agents API directly via curl. After execution, the CLI will:
  1. Create a new cloud session (Cloud Session) in the selected remote environment.
  2. Send the task description to the cloud Agent.
  3. Stream the cloud Agent's output (thinking, tool calls, final results) to the local terminal in real time.
  4. After the task completes, print the session URL in the local terminal so you can continue tracking it on the web:
Cloud remote session created.
Session ID: qs_01krxhzz******351vhya
Environment: Default (env_01kqs75n******6x6hmj53ds)
URL: https://qoder.cn/agents/session/qs_01krxhzz******351vhya
Even if you close the local terminal after starting the task, the cloud Agent keeps running; you can resume progress the next time you reopen the CLI or visit the web console.

2. Use /remote-env to select the cloud execution environment

In an existing qoderclicn interactive session, enter: 
/remote-env
The CLI will pop up an environment selector: 
Remote Environment

Select the default cloud environment.

❯ 1. Default
  2. Sessions: test · Network: trusted
Once selected, it is written to the user-level configuration ~/.qoder-cn/settings.json: 
{
  "remote": {
    "defaultCloudEnvironmentId": "env_01kq********hmj53ds"
  }
}
After that, all --remote calls reuse this default environment, with no need to reselect each time.

Command Reference

qoderclicn --remote "<task>"

ItemDescription
PurposeKick off a cloud session from the CLI and run the task on a VM managed by Qoder
ContextDoes not depend on the local working directory; all reads and writes happen in the cloud environment
Interrupt behaviorPressing Ctrl+C locally only disconnects the terminal subscription; the cloud task keeps running
Login requiredYes (first use triggers qoderclicn login)
GitHub authorization requiredRequires authorizing Qoder's access to the corresponding GitHub repository (Qoder website > Service Integrations > GitHub Integration)
Example: 
# Basic usage
qoderclicn --remote "summarize the latest 50 PRs in this repo"

/remote-env

ItemDescription
Trigger locationAvailable only in a qoderclicn interactive session (enter / then select)
PurposeSelect / switch / create the cloud execution environment as the default for --remote
ScopeUser-level (written to ~/.qoderclicn/config.json), shared across terminals

FAQ

Q: Can --remote mode read my unsaved local changes? No. --remote tasks run on an independent cloud VM and access the project in the Remote GitHub corresponding to the current environment. Q: Can I run multiple --remote tasks at once on a single computer? Yes. Each --remote call creates an independent cloud Session, and they do not affect one another. You can view the task list in the Cloud Agents console (https://qoder.cn/agents).
Overview
Guides