Question 1

Does Soloco run its own hosted agents?

Accepted Answer

No — Soloco does not run any hosted agents. It coordinates the agent runtimes already installed on your machine (such as Claude Code and Codex), turning your goal into scoped tasks those runtimes execute under your own subscription. See Run AI agents locally for why that model matters.

Question 2

Do I need an API key?

Accepted Answer

No. Soloco uses the agent runtime already installed and logged in on your machine (e.g. Claude Code) and your existing subscription. There is no separate API key to manage.

Question 3

Which agent runtimes are supported?

Accepted Answer

Currently Claude Code and Codex. More runtimes (Kimi, Qwen Code, OpenCode, and others) are in development. Run soloco runtimes to see what was detected on your machine and its login state.

Question 4

Where does my data live?

Accepted Answer

On your machine, by default. Soloco is local-first: the orchestrator and the agents run locally, and your goals, files, and outputs stay on your device. The cloud holds exactly three things: your account and billing; anonymized aggregate statistics and diagnostic data (aggregated locally, stripped of identity, never used to identify you, never containing your goals or outputs — on by default, can be turned off); and content you explicitly consent to sync. Full details in the privacy policy.

Question 5

What does it cost?

Accepted Answer

Registration is open and Soloco is currently free to use. Paid plans will be announced on the Pricing page when they launch — that page is the source of truth.

Question 6

Is Soloco open source?

Accepted Answer

Soloco's V2 core is closed-source; registration is open and it is currently free to use. The agent runtimes it orchestrates are independent products with their own licenses — several of the runtimes on our adapter roadmap are open source. If licensing matters for your evaluation, the machine-readable facts page at /agent always states the current status.

Question 7

How is a mission different from a workflow?

Accepted Answer

A workflow executes a predefined sequence of steps; a mission is a long-lived goal that Soloco keeps planning, executing, verifying, and re-planning in cycles until the goal is achieved. You describe the destination, not the route: the task tree is derived, audited, and revised as results come in — including while you are away. Core concepts explains standing missions and heartbeats in detail.

Question 8

What do I need to run it?

Accepted Answer

Node.js ≥ 22.5, a supported platform (macOS / Windows / Linux), and a logged-in local agent runtime. See Install.

Question 9

Does work continue when I step away?

Accepted Answer

Yes — that is the point of Soloco. Once a goal is running it doesn't need you watching; come back to collect deliverables on the results page, and the canvas briefs you on what happened since you last looked. You can also set up standing missions that make progress on a rhythm — see Core concepts.

Question 10

Will Soloco send email or touch my accounts on its own?

Accepted Answer

No. Every outward-facing capability stays under your control: with email connected, agents can only draft — each draft goes out only after you approve it; browser capability has a master switch, is granted per mission, and can be revoked in one click; credentials are stored centrally and handed out only as needed. Any step that needs your account or payment is done by you.

Question 11

How do I update?

Accepted Answer

Or reinstall the latest version: npm i -g @soloco/client@latest.

Question 12

Something's wrong — how do I debug it?

Accepted Answer

Start with soloco doctor — it checks your Node version, daemon state, and runtime logins item by item, each with a next step. You can also generate a context-rich problem report from the local UI and paste it to your AI assistant, or send it to us.

Question 13

How do I uninstall?

Accepted Answer

Question 14

Is Claude an AI agent?

Accepted Answer

Claude itself is a large language model, not an agent — an AI agent is what you get when a model like Claude is given tools, memory, and a goal loop. That is exactly what Claude Code does: it wraps Claude with a terminal, file access, and an execution loop, turning it into a capable coding agent on your machine. Soloco sits one level above: it coordinates runtimes like Claude Code so that model-turned-agent can pursue long-running missions.

Question 15

What makes an AI agent different from a chatbot?

Accepted Answer

A chatbot answers you turn by turn; an AI agent takes a goal and works toward it — planning steps, using tools, checking its own results, and continuing without being prompted at every step. The practical test: if you can leave and come back to finished work, it is an agent; if it waits for your next message, it is a chatbot.

Question 16

What is an AI agent OS?

Accepted Answer

An AI agent OS is the organizing layer that turns individual AI agents into a system that can carry long-running work: it plans goals into task trees, dispatches work to agent runtimes, verifies results, persists state so work survives interruptions, and controls what agents are allowed to touch. The analogy is deliberate — an operating system turns raw hardware into something programs can rely on; an agent OS turns raw agent capability into organized, auditable, resumable work. Soloco is a local-first take on this idea: runtimes like Claude Code and Codex supply the intelligence, and Soloco supplies the organization — missions, verification, memory, and control.

Question 17

What are real AI agent use cases?

Accepted Answer

The use cases that hold up in practice are recurring, verifiable work: research and monitoring briefs, repository chores (tests, refactors, dependency upgrades), content pipelines with review gates, competitive tracking, and operations reports. Agents do worst on one-shot tasks with fuzzy success criteria — and best when the goal can be checked. That is why Soloco structures everything as verifiable task trees with review built in.

Question 18

What are the best AI agents for personal use?

Accepted Answer

The honest answer depends on what you already pay for. If you have a Claude or ChatGPT subscription, the strongest general-purpose agents you can run today are the local runtimes those subscriptions unlock — Claude Code and Codex CLI — because they use your real environment and have no separate API bill. Agent frameworks (LangChain, CrewAI and friends) suit developers building agent products. Soloco is for the layer above: organizing the runtimes you already have into missions that keep progressing while you are away.

FAQ

About Soloco

About AI agents in general

Still have questions?

Table of Contents

FAQ

About Soloco

About AI agents in general

Still have questions?

Table of Contents