cones.

Commands

Plain cones opens the dashboard. Every control-plane verb is also a command, usable by you, a script or an agent. A few actions are dashboard-only: hand reordering, the fork into another harness and take-over. Flags, JSON shapes and exit codes: cli.md.

Command list

CommandEffect
cones lsLive sessions and runs. --dir scopes to a folder, --json for scripts.
cones show IDPrint a conversation. Starts nothing.
cones search QUERYSearch conversation history, archived ones included.
cones launch --dir PATH [PROMPT]Start a session detached and print its id.
cones resume ID, cones fork IDReopen or fork a conversation, detached.
cones send ID TEXTSend one note to a live session.
cones wait ID...Block until sessions settle; print ID<TAB>STATE.
cones btw ID QUESTIONAsk a side question in a read-only fork that is not kept.
cones rename, compact, stop, rmThe harness's own rename, compaction and stop; rm does what ctrl+x twice does.
cones mcpServe the same verbs over MCP stdio.
cones run JOB, catchupRun a configured job; recover missed schedules at login.
cones config [set KEY VALUE]Print the configuration reference, or set one setting.
cones skill [NAME]Print a bundled skill.

Ids are full ids as cones ls prints them; a prefix is an error that names the matches. Which verbs reach which harness: capabilities.

Starting a session

cones launch --dir ~/src/app "fix the flaky test"
cones launch --dir ~/src/app --harness codex "rebase onto main"
cones launch --dir ~/src/app --harness claude --model opus --effort high

The session runs detached, needs no terminal and appears in the dashboard. --parent self lists it beneath the agent that launched it. --print-command prints the folder, environment and command without launching. Codex needs a prompt, since it keeps no thread before a first turn. A client that exits within three seconds fails the launch with its last screen and first line of stderr. A printed id means the client started, not that it took the prompt: a client waiting on a sign-in or trust screen is named too.

Reading and searching

cones show 4f0c2b1e-8d31-4a55-9f0c-6b2a17e4d900 --tail 5
cones show 4f0c2b1e-8d31-4a55-9f0c-6b2a17e4d900 --follow
cones search "permission decision" --dir ~/src/app --json
cones search "why did we change the parser" --mode meaning --json

show prints the last 40 messages by default, labelled user, assistant or output with the harness's timestamps and tool calls. Terminal control sequences are stripped. Reading attaches to nothing and writes no native state. A session with no saved conversation in a terminal cones hosts is printed as its current screen, and says so.

search uses word search by default. --mode meaning uses the local model. --when recent|month|old ranks matches from that period higher without removing others; --since filters.

cones over MCP

Configure a stdio server with command cones and arguments ["mcp"]. No network listener or daemon is needed.

ToolCommand
cones_search, cones_showHistory search and read
cones_lsls --json
cones_launch, cones_resume, cones_forklaunch, resume, fork
cones_send, cones_waitsend, wait (up to 600 s)
cones_rename, cones_btw, cones_compactrename, btw, compact
cones_stop, cones_rmstop, rm

None of the tools can change harness permissions or edit native configuration.

Comms

For dispatching work to the agents in one folder, with or without a coordinator. The folder's roster is every live session in the folder or under it in the same repository.

cones comms --dir ~/src/app send SESSION_ID "text" [--greet]
cones comms --dir ~/src/app mail [--ack N]
cones comms --dir ~/src/app wait [--id SESSION_ID]... [--timeout SECONDS]
CommandBehavior
sendDeliver through the recipient harness's message channel. Missing channels fail. Notes name their sender and tell the recipient how to reply.
mailRead pending replies. Only --ack N marks them handled.
waitBlock for new sessions or mail. With --id, watch named workers for input requests, failure or departure.

Commands make no model calls, though a delivered note can start a turn in the recipient. Delivery does not show that a worker read or answered.

Coordinator

cones coordinator --dir ~/src/app start

Starts a background Claude Code session with the bundled start-coordinator skill, which handles overlaps, relevant findings and integration in one folder. Dashboard ctrl+d does the same for the selected folder. A second live coordinator is refused. Workers hand over checked commits; the coordinator integrates them in order. Tell it stop coordinator to release the role.

The cones skill

The dashboard installs a cones skill into skills/cones/SKILL.md under your Claude Code home and into ~/.agents/skills, which Codex, pi and OpenCode read. It tells an agent what cones can do for it and to start other agents with cones launch, so you can open them from the dashboard. A copy you edited or deleted is left alone. cones skill cones prints it.