conchv0.2.0

Getting started

Why conch

conch goes further where agent work stalls: waiting on CI, losing agents to an update, guessing what an agent is doing, and being away from the laptop.

It finishes the job without you

A failed check or CI run goes back to the branch's agent with the log, and the pull request merges once it is green — run by the server, with your laptop shut. See Sending a failure back.

  1. Agent finisheson its own branch and worktree
  2. Check runsthe project's own test command
  3. Pull requestopened when the agent is done
  4. CIwatched by the server
  5. Mergedat the commit that went green
Red? The failed check or the tail of the CI log goes back to the branch’s agent, which fixes it and finishes again — up to the limit you set, then it is yours. All of it runs in the machine’s server, so it carries on with every window closed.
The autopilot: the agent finishes, the check and CI run, a failure goes back to the agent, and the pull request merges once green

Updating never stops your agents

conch reloads its server onto a new build and keeps every terminal open. See Updating without stopping agents.

It hears from the agent, not just its screen

An agent tells conch what it is doing — working, waiting for permission, done — through OSC 7501, and conch passes that up to your terminal's tab. See Agent states.

⠋workingbusy
!waitingneeds you
✓donefinished, unseen
○idlewants a prompt
✗failedended in an error

How conch knows, most reliable first

1The agent's own reportOSC 7501
2HooksClaude Code and others
3Screen rulesthe bottom of its screen
4Foreground processis the agent running at all

Agents can run agents, and stay in their lane

An agent can start a reviewer, prompt it and read its answer, but reaches only the panes it started and its own project. See Agents together.

A native desktop on the same servers

Conch.app is a window on the same servers the TUI talks to, with panes drawn by Ghostty; close it and nothing stops.

Conch.app: the tree of machines, projects, agents and branches, a waiting agent's question answered from the sidebar, and a working agent in its tab
Answer a waiting agent from the sidebar while another works in a Ghostty pane.
Conch.app showing a branch's changes: files, a diff, a note to the agent on a line, and the pull request's checks
A branch's changes: commit single hunks, and leave the agent a note it answers in the thread.

A cloud sandbox is just another machine

A sandbox at Daytona, boat.dev or Devin Cloud shows in the tree beside your own machines. See Sandboxes.

Every conversation, from every agent, in one place

Search, resume, delete or hand off what every agent saved for a project. See Sessions.

Your phone, without anyone else's server

Answer a waiting agent over Tailscale or a relay you run yourself, with no account. See Phone.

The phone app: a waiting agent with its question and the answers to tap
A waiting agent on the phone: its question, and the answers as buttons.

Built for the terminal, and for ssh

The TUI works the same on a laptop or over ssh, and shows every machine you add in one tree. See Remote machines.

your laptop

conch

the TUI — a client you can quit any time

unix socket · NDJSON

conch server

owns panes, tracks git, PRs and agent states

⠋claude · add-health-check
!codex · fix/flaky
○zsh · dev-server
ssh · conch bridge

gpu-box (remote)

conch bridge

started over your normal ssh; no secrets stored

unix socket · NDJSON

conch server

keeps running when your laptop sleeps

⠋claude · train-eval
⠋opencode · data-loader

Ask in plain words, approve before anything runs

Tell the brain what you want; nothing runs until you press Enter.