Runtimes

A runtime is the machine or cloud worker that executes an agent's tasks. The agent decides what to do; the runtime decides where it happens — which filesystem, which toolchain, which credentials. Getting runtimes right is what separates an agent that can touch your real project from one that cannot touch anything.

The three kinds

Choosing a runtime for an agent

On the agent detail page you select the runtime the agent runs through, and inspect that runtime's online status, workload, CLI, and bound agents. An agent bound to an offline runtime simply cannot take work — check status before wondering why nothing is happening.

How local execution works

The local runtime is a daemon on your machine. It claims tasks, then invokes an AI coding tool installed on that machine to do the work. Nothing about your project — the code, the dependencies, the credentials in your shell — leaves the machine; the daemon is the only bridge.

First connection on Desktop

After signing in and creating or selecting a workspace, Desktop onboarding prepares the local daemon, connects your Wujie account, and starts the service automatically. It prefers the bundled CLI and downloads a verified copy when needed. No separate Wujie installation or login commands are required.

“Local service connected” means the daemon is ready. Continue after an online runtime from this computer appears in the selected workspace. Setup failures can be retried in place; only an expired Wujie session requires signing in again.

Prepare an Agent tool

1. Install your chosen AI coding tool on this computer using the tool's installation instructions.
2. Open the tool, complete its account sign-in or API configuration, and confirm that it works on its own.
3. Return to onboarding and refresh. Desktop rescans an idle daemon immediately; a daemon with active tasks continues running and discovers tools in the background.

Wujie sign-in and the tool's model account authorization are separate. Detecting a tool does not verify model account access. You can skip this step and connect later.

If automatic startup is disabled, “Start local service” starts it for this session without changing that preference. Desktop uses its own profile and does not overwrite manually configured CLI profiles.

Connectors reuse this path

The DingTalk and Feishu document connectors also run through a local runtime: they call the platform CLI (dws or lark-cli) on a runtime you own and that is online. See Connectors for what that enables.

Custom runtime profiles

A tool of your own — a company-wrapped CLI, an in-house gateway, a variant launched with fixed flags — can be registered as a custom runtime profile. On the runtimes page, choose "Add custom runtime":

1. Protocol family — the built-in protocol the tool is compatible with (claude, codex, cursor, and the rest); it decides which protocol the platform speaks to the tool and cannot be changed after creation.
2. Command line — the executable plus fixed arguments, e.g. company-codex --profile team-a. The first word is the command name, the rest are fixed arguments. Quotes and escapes are supported; pipes, redirection, and variable expansion are not.
3. Display name and description — the name appears in the runtime list (suffixed with the device name) for agents to bind to.

The profile belongs to the whole workspace and syncs to every connected machine. Each machine's daemon resolves the command in this order:

1. A per-machine path override (wujie runtime profile set-path) — pin the profile to a binary not on PATH, or pick one of several installs;
2. A PATH lookup on that machine.

When the command resolves, a runtime instance registers under this profile; when it does not, that machine silently skips it — other machines are unaffected. After a profile change, daemons detect the difference and re-register on their own; no restart needed.

Removal is two-layered: deleting a runtime instance from the list only removes it on the current machine, and the daemon registers it again as long as the profile exists. To remove it for good, delete the profile itself from the custom runtimes catalog.

Next

• Agents — agents bind to a runtime to execute
• Automations — unattended runs also execute on runtimes
• Connectors — the CLI read path through your local runtime