conch-agent

Download it, open it, sign in with a plan you already pay for or paste a key. That is the setup. There is no account to make, no terminal to learn and no telemetry. Your chats, memories and settings live in ~/.conch on your computer, and one assistant reaches you on the web, your phone, your desktop and the chat apps you already use.

Conch is for anyone. If you have never opened a terminal, it still works for you. If you live in one, it brings every coding agent you have into one place.

Install

The app. Download it for macOS, Windows or Linux from the newest release and open it. If your computer asks first, the guide says which button to press.

One line. On macOS and Linux:

curl -fsSL https://conchagent.com/install.sh | sh

On Windows, in PowerShell:

irm https://conchagent.com/install.ps1 | iex

It installs the newest release: stable once there is one, before that the newest beta, then the newest alpha. It fetches Node.js and Git if they are missing, keeps Conch running and opens it. Run the same line again to update. Add --server on a computer with no screen, or --uninstall to remove it. Afterwards, conch help lists what the command line can do.

From a checkout, with Node 24 or newer:

corepack enable
pnpm install
pnpm start        # builds and opens http://localhost:4317

Three things it does differently

It knows what it can do. Just ask.

Ask about Friday before your calendar is connected, and Conch does not guess. The card that connects it is right under the reply. Press it, and the chat carries on by itself with the day as it is. Every app, skill and setting works this way: nothing to configure first, no file to edit, and nothing is turned on until you say so. That is how someone who has never opened a terminal gets the same assistant as someone who lives in one.

Ask for an app. It builds one.

When nothing you have does what you need, say so in your own words. Conch writes a Conch app, checks it, tries every part of it and shows it to you as a card. Its tools work with every model, its pages look like Conch, and it runs sealed off from your files. Nothing is added until you press the button, and you can share it on GitHub in one press. The same goes for a provider or a chat app Conch does not list yet: name it, and Conch reads the docs and makes it.

Something broke? It is already fixed.

Conch keeps an eye on every part of itself and mends what it can before you notice: a program that is missing, a process left behind by a crash, an app whose sign-in needed refreshing. What it fixed while you were away is a quiet list, not an alarm. When something needs you, like signing in again, you get one plain sentence and the button that does it. Daily backups and signed updates that roll back on failure come with it.

What it does

In the chat

• Every model you have, one picker. The plans you already pay for, with their own sign-in: Claude Code, Codex, GitHub Copilot, Gemini CLI, Grok. Keys from OpenRouter, Anthropic, OpenAI, Google, Mistral, DeepSeek and more. Ollama or LM Studio for a model that is private and offline. A chat can switch models without losing its thread, or when you ask ("use Opus 5.5", "something cheaper"), and when a plan hits its limit or the internet goes, the next one carries on. Providers
• It says what it is doing, in plain words. Each run of work is one line, like "Ran the tests · 241 passed", that opens into its steps. Ask Why? about any of them. Your chats
• It does not give up at the first error. Every model reads what went wrong, tries another way and checks its work before it says done. Working on a problem
• It waits without nagging. "Watch CI and fix it if it fails." The chat stays yours, and your assistant carries on when something changes.
• Big jobs in one go. For 300 emails or 40 pages it writes one short script, sealed off, shown as one line with live counts and one Undo. Scripts
• Cards you can press. Calendars, emails, files, products, songs, places, prices and charts, each a card in the chat. Cards
• Research, files and pictures. Sources with references, PDF and Office files read and made, and charts and documents that open beside the chat. Show me
• See how it did it. Replay any chat step by step, and save it as a page or as training files with keys and personal details taken out. How it did it

Your agents

• As many as you like. Each with a name, a face, a personality and instructions. Pick who answers a chat, or set one per chat app and routine. Agents
• They talk to each other. "@Researcher find options, @Writer draft it." Agents take turns in one chat and stop before they loop or run up a bill.
• Chats that know about each other. Ask what your other chats are doing. Two working in one folder keep out of each other's way, one waits for another to finish, and they send each other messages, as far as you let them. Working together
• Work in the background. Hand a job off and keep chatting, or have another provider do a part. As many run at once as there is room for, and one that waits says why. Tasks
• Memory that looks after itself. Plain Markdown you can read, edit or forget, tidied overnight and reported in a short morning note. Memory
• Skills for every model, from what worked, from a sentence or from Discover. Skills
• Bring your things. Memories, skills, routines and agents from OpenClaw or Hermes, and past chats from Claude Code, Codex, Gemini CLI, OpenCode and Copilot. Come home

Works for you

• Routines. Every weekday at 7:30, when an email arrives, before a meeting, when a page changes. [Routines](./apps/