Architecture
cones is one binary in two layers. The control plane finds sessions from native records, reads their conversations, and starts, messages, renames and stops them, for a person or an agent alike. Three clients sit on it: the dashboard, the coordinator and scheduled jobs. Components and the coordinator's wake loop: architecture.md.
The boundary
| cones owns | The harness owns |
|---|---|
Scheduling and timeout_min | Execution and permissions |
| Supervision, ledger and captured output | Native session identity and reports |
| Discovery, display and navigation | Native session operations |
cones never intercepts tool calls or adds a permission engine. A policy the harness cannot enforce is a validation error. State, context and usage come from native reports; missing values stay absent. Cost estimates carry their source and coverage.
The control plane
| Verb | Command | Notes |
|---|---|---|
| Find | ls | Live sessions and runs, by folder |
| Read | show, search | Starts nothing |
| Launch | launch | Detached; prints the id |
| Resume, fork | resume, fork | Detached; prints the id |
| Message | send | Through the harness's own channel |
| Wait | wait | Until a session settles |
| Rename | rename | The harness's own rename |
| Ask | btw | A read-only fork that is not kept |
| Compact | compact | The harness's own compaction |
| Stop | stop | Keeps the conversation |
| Remove | rm | Also closes jobs and folders |
The dashboard and the commands build the same native commands. The dashboard opens resumes and forks in its own pane; the commands host them detached. cones mcp serves every verb as an MCP tool.
Harness definitions
Embedded YAML files declare each harness's paths, reports, native arguments and viewer policies. Registered native adapters interpret protocols and authorize supported operations; a YAML declaration alone cannot create support. Schema and integration requirements.
Observation cost
Each background refresh shares one process-table read and one read of each native index among its consumers. Native SQLite reads are in process and read-only, with no migrations. Liveness is checked against the kernel before cones signals a process.