Agent runtimes
Compare Claude Code, Codex CLI, and the DeepSeek Harness bundled with Soloco.
Soloco is the orchestration layer. The selected agent runtime supplies the model connection and executes each agent run on your machine. You can use an existing Claude Code or Codex CLI account, or enter your own DeepSeek API key to use the DeepSeek Harness (DSH) bundled with Soloco.
| Runtime | Setup and authentication | Platforms | Network and model controls | Current limitations |
|---|---|---|---|---|
| Claude Code | Install Claude Code locally and sign in with an existing Claude account or subscription. No DeepSeek API key is entered in Soloco. | macOS, Windows, and Linux, subject to Claude Code support | Follows Claude Code's network and sandbox policies. Supported Soloco model selection is available. | Availability depends on the installed CLI version and account access. |
| Codex CLI | Install Codex CLI locally and use an existing ChatGPT/Codex account or another authentication method supported by the CLI. No DeepSeek API key is entered in Soloco. | macOS, Windows, and Linux, subject to Codex CLI support | Follows Codex CLI's network and sandbox policies. Supported Soloco model and reasoning controls are available. | Availability depends on the installed CLI version and account access. |
| DeepSeek Harness (DSH) | A compatible DSH build is bundled with Soloco. Enter your own DeepSeek API key in Soloco; no separate DSH installation is required. DeepSeek bills the associated usage. | macOS and Linux. Windows is not currently supported. | DSH requires outbound network access, and Soloco does not currently provide network isolation for DSH. It uses the bundled runtime's default DeepSeek model. | DSH is never selected automatically or as a fallback. Model and reasoning overrides, AMA, runtime session resume/fork, Browser, MCP, and Skills are not currently supported. |
DeepSeek Harness boundaries
- DeepSeek only. DSH is a local agent runtime that uses the verified DeepSeek route. It is not a generic OpenAI-compatible API connector.
- Explicit selection. Because DSH runs need outbound network access, you must select it yourself for a mission; Soloco will not choose it as a default or fallback.
- Runtime defaults. Soloco follows the default DeepSeek model provided by its bundled DSH build. There is no separate DSH model or reasoning selector.
- Provider billing. Your DeepSeek API key authenticates requests made by the bundled DSH runtime to DeepSeek. DeepSeek accounts for that usage under your provider account.
- Compatibility. Soloco's current validated DSH compatibility baseline is
@deepseek-ai/dsh@0.1.0-rc.6. The compatible build is maintained with the Soloco release; do not install or upgrade it separately.
Your workspace and orchestration state remain local by default. Whichever runtime you choose still communicates with its model provider to perform inference under that provider's terms.
Next: Install Soloco or follow the Quickstart.