subgentic/coralDokumentacja

Coral: the Inbox for your agents.

Your coding agents do the work. Anything that needs you — a question, a permission, a file to review — lands in one Inbox, on your laptop or your phone, and the agent carries on the moment you answer.

macOS (.dmg) • Windows (.msi) • Windows portable (.zip) • Linux x86-64 • Linux ARM64 · all releases
Apache-2.0 · no account, nothing to sign up for · you keep your own keys and subscriptions · works with Claude Code, Codex, Antigravity, Pi, OpenCode and Hermes (experimental)

The Inbox • Chief • Teams • Quick Start • Documentation • Discord

_{A document lands in the Inbox, you comment, the agent answers and updates it. (Sample data; staged with scripted agents.)}

_{A file an agent made, waiting for your review: read it, Approve or Request changes. (Sample data.)}

_{A file an agent made, waiting for your review: read it, Approve or Request changes.}

Install on macOS or Linux with one command:

curl -fsSL \
  https://raw.githubusercontent.com/subgentic/coral/main/install.sh \
  | bash

_{Compare with the earlier version: what changed, marked. (Sample data.)}

Coral wraps the agent CLIs you already use (Claude Code, Codex, Antigravity, Pi and OpenCode, and Hermes, which is experimental). It calls no AI API itself: your keys, your subscriptions, your tools. It runs as one Go binary on your laptop or a remote box.

Running agents is easy. Knowing when one of them needs you is the part that goes wrong: a permission prompt sits for an hour in a terminal you closed, a question waits behind a tab you forgot, a finished file never gets looked at. Coral puts all of that in one place.

• Needs you. Every agent that is waiting for a permission, a question or a decision, and every file an agent asks you to review, in one list. One tap answers it; the agent carries on. The number on the Inbox tab is what is waiting, and you can turn on desktop alerts. While the tab is in the background its title carries the total too.

• A question to you is an item like a review. It says who asked and about which goal and task, shows its words rendered, and takes your reply with pictures if you want them; a question whose wait ran out while you were away is kept, not lost.

• Comments come back to you. When an agent answers a comment on a file or a goal, the file is back in Needs you, and the goal page has its own Comments tab.

• Review that keeps its history. Open a file the agent made, read it, Approve or Request changes. A new version of the same file arrives as the next version with Compare, so you see what changed. Comment on the whole document or a passage, and add a picture you have marked up (pen, arrow, box); the agent is told, and the original is kept. A file that is almost right can be approved with a note, and a row you do not want to act on can be dismissed (with Undo).

• Goals as high level direction. Give a team a goal, watch its tasks and files, and Close goal when it is true. Coral tells you when files for a goal are still waiting for you before you close it, and an active goal whose tasks are all done shows up in Needs you as "looks done" for you to close.

• A compact file viewer. The file first, with its controls on one header row (version chip and Compare, Approve, Request changes, a menu for the rest); on a phone, two thin rows.

• A record of what you decided. An Activity folder lists your decisions in Needs you, each row chained to the one before it.

• Versioned Artifacts Artifacts are versioned so you can see what the agents have changed between turns

• Every chat and every board, searchable. The Inbox also holds the history of every agent CLI's conversations and each team's message board.

• Detailed Analytics Analytics from token spend, cache read/writes broken down by provider, model thinking level, tasks, commits. etc. Coral is able to provide incredibly detailed data across your workloads to help you monitor for drift in your agentic system. Use it to figure out where the bottlenecks are in your agents.

_{The same dashboard on a : the agent list, and one agent's chat. (Sample data.)}

Behind the Inbox is the part that does the work: a team of agents on one board. An Orchestrator plans and delegates; a Lead Developer writes the code; a QA Engineer checks it. They can be different vendors on the same team (a Claude orchestrator, Codex workers, an Antigravity reviewer), each in its own terminal session and, if you ask, its own git worktree. The team's board holds the messages and a task queue whose dependencies are conditioned on outcomes and artifacts, not just "done".

_{The team's board beside one agent's chat: the Orchestrator and its workers at work. (Sample data.)}

• Mixed-vendor teams. Permissions are written once and translated into each CLI's native format, so a read-only QA agent is read-only whether it is Claude or Codex.

• Idle agents sleep by themselves. An agent that has been idle for a while is put to sleep to free memory and wakes when something is sent to it; an agent mid-work stays awake. On by default, with a switch in Settings.

• A Skills Store (experimental). Import a skill, review it, approve it; approved skills appear in New agent and New team, and agents can publish and search skills themselves.

• Teams that survive closing the lid. Sleep a whole team and wake it tomorrow, or after upgrading Coral: every agent resumes its own session.

• Run it anywhere. Put Coral on a build server or a spare Mac; open it from any browser, or scan a QR code for a phone client.

Everything else is in the feature list.

Download the latest release from GitHub Releases. These links always point to the newest version:

• macOS: Coral.dmg (universal binary)
• Linux: coral-linux-amd64.tar.gz (x86-64) or coral-linux-arm64.tar.gz (ARM64, e.g. Graviton or Docker on Apple silicon)
• Windows: Coral-x64.msi (installer) or Coral-x64-portable.zip. These are currently not code-signed, so Windows SmartScreen warns that the publisher is unknown. Verify the file with the attestation check below before you run it.

First install and sign in to at least one agent CLI: Claude Code, Codex, Antigravity (agy), Pi, OpenCode, or Hermes (experimental). Coral runs these tools; it does not install or authenticate them.

• macOS: Open the DMG, drag Coral.app to Applications, then open Coral. The app includes tmux. For terminal commands, run /Applications/Coral.app/Contents/MacOS/install-cli.sh and add ~/.local/bin to your PATH.

• Windows: Run the MSI, then open Coral from the Start menu. For the portable ZIP, extract it, open PowerShell in that folder, and run .\coral.exe --no-browser.

• Linux: Download the archive for your architecture, then extract and start it (ARM64: replace amd64 with arm64):

  mkdir -p "$HOME/.local/share/coral"
  tar -xzf coral-linux-amd64.tar.gz -C "$HOME/.local/share/coral"
  export PATH="$HOME/.local/share/coral:$PATH"
  coral --no-browser

In the dashboard, choose New agent (then New agent again in the dialog: "One agent in a folder you choose"), choose the agent in step 1, enter an existing project folder on the computer running Coral (or use Browse), and choose Launch. In the agent's Terminal, answer any folder-trust or sign-in prompt, then send a task from Chat with Enter. Choose New team instead to start several agents together.

See Getting started for the full installation and first-agent walkthrough.

Chief is one of your running agents that you make the front door. In Settings > Chief you pick which agent it is, give it a name and an avatar (one of eight colours and a letter), and choose the team it fronts: the team whose agents Chief takes your requests to. Chief has its own page on your phone, /chief, with its own chat (you turn the page on in Settings). You decide how much it may do on its own: Ask first (the default) asks before each action; Act edits without asking, and a shell command still asks; the level applies when Chief restarts. Chief has to be an agent that is already running (on a team of its own, a team of one), and Settings > Chief is on the computer itself, not through Coral Hub. Coral Hub and the Chief x

Coral Hub (app.coralhub.dev, invite-only beta) lets you reach your Coral servers from any browser without opening a port. A fresh install never connects, or asks you to, on its own: connect a server from the home screen or Settings › Coral Hub, or run coral cloud connect on it. Coral offers it at first launch (the dashboard's Connect screen and a prompt in the terminal) only when you pass a hub URL (--cloud-url https://app.coralhub.dev or CORAL_CLOUD_URL) or start it with --cloud-connect prompt (CORAL_CLOUD_CONNECT=prompt); --cloud-connect off turns that off. See Coral Hub.

Full documentation at subgentic.github.io/coral.

We welcome contributions in the form of feature requests or bug reports!

Apache 2.0 License. See LICENSE for details.

Star the repo • Join Discord • Read the docs