cones.

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.

You at the dashboard and your agents over the cli or mcp share one control plane that finds, starts, messages and stops sessions of each harness through its own commands

The boundary

cones ownsThe harness owns
Scheduling and timeout_minExecution and permissions
Supervision, ledger and captured outputNative session identity and reports
Discovery, display and navigationNative 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

VerbCommandNotes
FindlsLive sessions and runs, by folder
Readshow, searchStarts nothing
LaunchlaunchDetached; prints the id
Resume, forkresume, forkDetached; prints the id
MessagesendThrough the harness's own channel
WaitwaitUntil a session settles
RenamerenameThe harness's own rename
AskbtwA read-only fork that is not kept
CompactcompactThe harness's own compaction
StopstopKeeps the conversation
RemovermAlso 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.