cones.

Getting started

cones runs on macOS. Each harness you want to use, such as Claude Code or Codex, is installed and signed in on its own. cones looks for it in ~/.local/bin, ~/.cargo/bin, ~/.opencode/bin, /opt/homebrew/bin, /usr/local/bin and the system folders; shell aliases and extra PATH entries are not used.

Install

brew tap YuvalSarel1/cones https://github.com/YuvalSarel1/cones
brew trust YuvalSarel1/cones
brew install cones

On Intel Macs Homebrew builds from source and needs a current Xcode. With Cargo:

cargo install --git https://github.com/YuvalSarel1/cones

A Homebrew install checks the tap once a day and upgrades in the background; the dashboard asks you to reopen it. start.update_check turns this off.

Quick start

cones
  1. Existing sessions appear automatically, grouped by folder.
  2. enter opens one in its native client. ctrl+z returns to the list.
  3. To start work, select + add folder and enter a project directory.
  4. Choose a harness with shift+tab, type an instruction and press enter.

? lists the keys for where you are. ctrl+g opens Help, which is searchable.

Sessions started from the composer skip permission prompts by default, using each harness's own flag. Run cones config set defaults.skip_permissions false to keep prompts. See permissions.

Pages

PageCovers
DashboardKeys, session states, history and search, forks, viewers, the composer.
HarnessesWhat cones can do with each harness, where each value comes from, and what is unverified.
CommandsThe cones CLI, the MCP server, comms and the coordinator.
Jobsjobs.yaml, schedules, what a scheduled run is allowed to do, and run results.
ArchitectureThe control plane, what cones owns and what stays with the harness.

These pages are summaries. The full reference lives in the repository: dashboard.md, harness.md, cli.md, jobs.md, architecture.md, harness-definitions.md, bindings.md and testing.md.