Skip to main content
Integrations and remote

Cloud Mode

--remote mode runs your Qoder CLI CN tasks directly in a Qoder-managed cloud VM, so your local computer does not need to stay on or remain active. The entire flow from issuing the instruction to producing the result is hosted in the cloud, with your local terminal serving only as the entry point.
Complements the existing Remote Control mode.

Use cases

  • Long-running tasks: training, bulk refactoring, large-scale code review, where tying up the local machine for a long time is inconvenient.
  • Fire-and-forget while offline: write a prompt on a plane or the subway, and check the result when you're back.
  • Unified environment: team members share a consistent set of dependencies and tools, avoiding "works on my machine."
  • Resource isolation: the cloud VM provides independent CPU / memory / network quotas without competing with your local machine.

Quick start

1. Start a task in the cloud

Pass the --remote flag directly in the terminal: 
qodercn --remote "review the auth middleware in src/middleware and suggest improvements"
If you get a Cannot find package error, switch to the HTTP API quick start and call the Cloud Agents API directly via curl.
Upon execution, the CLI will:
  1. Create a new 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 result) to your local terminal in real time.
  4. Print the session URL when the task completes, so you can follow up 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
Once a task is started, the cloud Agent keeps running even if you close the local terminal; reopen the CLI or visit the Web console later to pick up the progress.

2. Choose the cloud execution environment with /remote-env

In an existing qodercn interactive session, type: 
/remote-env
The CLI pops up an environment picker: 
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"
  }
}
All subsequent --remote invocations reuse this default environment without re-selecting each time.

Command reference

qodercn --remote "<task>"

ItemDescription
PurposeStart a cloud session from the CLI, executing the task in a Qoder-managed VM
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
Sign-in requiredYes (first use triggers qodercn login)
GitHub authorization requiredRequires authorizing Qoder for the corresponding GitHub repositories (Qoder website > Service integrations > GitHub integration)
Example: 
# Basic usage
qodercn --remote "summarize the latest 50 PRs in this repo"

/remote-env

ItemDescription
Where to triggerAvailable only in a qodercn interactive session (type / and select)
PurposeSelect / switch / create a cloud execution environment as the default for --remote
ScopeUser level (written to ~/.qoder-cn/settings.json), shared across terminals

FAQ

Q: Can --remote mode read local unsaved changes? No. A --remote task runs in a separate cloud VM and accesses the Remote GitHub project associated with the current environment. Q: Can I run multiple --remote tasks on one computer at the same time? Yes. Each --remote invocation creates an independent cloud Session without affecting the others. The task list is available in the Cloud Agents console.
Getting started
Core concepts
Using Qoder CLI
Extending Qoder CLI
Integrations and remote
Configuration and security
Reference
Troubleshooting