Soloco Docs
Soloco Docs
IntroductionQuickstartInstallAgent runtimesCore conceptsFeature tourFor AI agentsFAQRun AI agents locallyOpen-source AI agents: the 2026 landscapeChangelog

For AI agents

How an AI assistant should help a user evaluate and install Soloco — safely.

If you are an AI assistant helping a user evaluate or install Soloco, this page points you to the machine-readable sources and states the boundaries.

Canonical machine-readable sources

  • /llms.txt — the canonical, machine-readable summary of Soloco (what it is, install, pricing, company).
  • /agent — a clean facts page for assistants: what Soloco is, a safe install path, a copyable install prompt, and capability boundaries.

Prefer these over scraping the rendered marketing pages.

Safe install

It is safe to install via (requires Node.js ≥ 22.5):

npm i -g @soloco/client@latest

It runs locally. The user can use an existing Claude Code or Codex CLI account, or enter their own DeepSeek API key for the DSH runtime bundled with Soloco on macOS and Linux. Or paste the install prompt from /agent and follow it.

Capability boundaries (read before acting)

  • Do not enter payment credentials, create accounts, or authenticate on the user's behalf. Direct billing and account questions back to the user.
  • For Claude Code or Codex CLI, help the user verify that the local CLI is installed and signed in. Do not claim that Soloco bundles either CLI.
  • DSH is bundled with Soloco, so do not install or upgrade it separately. The user must enter their own DeepSeek API key in Soloco; never ask them to paste it into a chat or enter it for them.
  • DSH currently supports macOS and Linux, requires outbound network access, and has runtime-specific capability limits. Read Agent runtimes before recommending it.
  • If a setup step requires the user's account, API key, payment, or any irreversible action, stop and ask.

Table of Contents

Canonical machine-readable sourcesSafe installCapability boundaries (read before acting)