Core concepts

Soloco turns a single goal into a small organization of cooperating agents. You direct it; the agents do the work on your machine.

The organization

When you give Soloco a goal, it plans the goal into a multi-node organization — a structured team of agents, each with a job — rather than a single chat thread. The organization has a CEO and employees: an employee is an organizational identity that persists across missions, with its own track record and reviewed memory; related work can also be grouped into departments (rolling out progressively). On the canvas you can see what each of them is doing.

Roles

Every run is carried out by one of four roles:

• CEO (conductor) — understands the goal, breaks down the work, maintains the plan, writes clear acceptance criteria, and replans when needed.
• Executor — does the actual work by driving your local CLI agents, producing results and artifacts.
• Reviewer — independently examines artifacts and execution records before a result counts as done, looking specifically for what's wrong.
• Evaluator — at each stage of a mission, gives an independent progress assessment: is this really moving forward, is it ready to wrap up, and what should the next round focus on.

Task tree

Work is organized as a task tree: a goal breaks into tasks, tasks produce runs, and runs produce verifiable results and artifacts. The tree is auditable (you can see what happened) and resumable (long work survives interruptions).

A goal nearing the end does not quietly declare itself complete: it first waits for your review, and you archive it or let it continue. When execution hits something only you can decide, Soloco pauses and hands it to you — you confirm item by item and it resumes — rather than silently cutting scope.

Standing missions and heartbeats

Beyond one-off goals, you can set up standing missions — long-running work that keeps making progress on a rhythm. Missions are driven by a heartbeat: describe the rhythm in plain language (daily, weekly, every few hours, or a one-time schedule), and the mission wakes itself up to work; it can also schedule its own next beat as it wraps up a round. A mission that keeps spinning without progress is automatically paused with a notice to you — it won't burn quietly.

SOPs (reusable playbooks)

When a run succeeds, Soloco can distill it into a reusable SOP — a playbook that lets the same kind of goal be executed again without starting from scratch. This is how a small team compounds into the execution power of a much larger one.

Local-first boundary

The orchestrator and the agents run on your machine, and your goals, data, files, and outputs stay local by default. The cloud's role has exactly three layers:

• Account and billing live on Soloco's servers.
• Anonymized aggregate statistics and diagnostic data (aggregated locally, stripped of identity, never used to identify you, never containing your goals or outputs) are on by default to improve the product, and can be turned off.
• Anything identifying or content-bearing (such as syncing artifacts to the cloud) happens only with your explicit consent. Full details in the privacy policy.