Introducing Coral Hub (Closed Beta)

Follow your Coral agents across machines, manage access modes, and coordinate remote workflows with browser-based pairing and local-first control.

Coral is designed to run directly on your own hardware. It executes agent commands in local processes, gives agents isolated git worktrees on your filesystem, and keeps development responsive and self-contained.

However, as your projects grow, work naturally spreads across multiple physical and virtual environments: a MacBook for day-to-day coding, a Linux desktop for heavy compilation, and cloud instances for long-running tests or continuous integration. Keeping tabs on agents running across different machines has traditionally required juggling multiple open SSH sessions and separate terminal tabs.

Today, we are introducing Coral Hub, our hosted dashboard currently in closed beta at app.coralai.ai. Coral Hub lets you follow your Coral agents across all your machines from a single browser interface, with local machine authority always taking precedence. The current beta is for one person connecting their own machines; shared human workspaces and member roles are not available.

1. Connect Machines with Browser Approval

Connecting a machine takes a one-time code you approve in your browser, and no inbound firewall port is opened on your computer.

Once approved, Coral maintains an outbound TLS status connection to the hub. Status updates and logs stream to your browser, but the hub never opens an inbound port to your computer.

2. Access Modes: The Lower Setting Always Wins

Coral Hub provides three distinct access modes for connected machines:

• View: Observe agent activity, stream read-only logs, and monitor task status. In View mode, the hub drops all terminal input.
• Interact: Send terminal input and respond to interactive agent questions from the browser.
• Launch: Start and restart agent sessions remotely from the hub dashboard.

The lower of the two settings applies: Coral Hub cannot raise a machine above the maximum its owner set in Coral Settings. If Coral Hub is set to Launch, but your local Coral Settings are set to View, the agent runs in View mode.

3. Auto-Accept and Best-Effort Safety Boundaries

When running repetitive tasks across multiple agents, approving every single routine tool call (such as viewing a source file or compiling a package) can introduce friction. Coral Hub allows operators to enable auto-accept for specific agents.

However, auto-accept comes with strict, built-in boundaries:

When auto-accept is turned on from Coral Hub:

• Local Opt-In Required: Turning auto-accept on requires Launch mode in Coral Hub and the local switch "Coral Hub can turn on auto-accept" enabled in Coral's local Settings. Coral Hub cannot enable auto-accept if the local switch is turned off.
• Scope Limit: Auto-accept answers only prompts that ask to approve a single tool call. It never answers questions or plan approvals.
• Time-Limited: Auto-accept is always bounded by a timer (1 hour default, at most 8 hours). When the timer expires, the agent returns to manual confirmation.
• Automatic Termination: Lowering the machine's access below Launch in Coral Hub makes Coral Hub tell the machine to stop it; if the machine is offline, it is stopped when it reconnects.

4. Run Your Own Hub: The Self-Hosted Alternative

Coral Hub is our hosted service at app.coralai.ai. For people who want to run the dashboard on their own machines or tailnet, Coral also provides a self-hosted option: Run your own hub.

Starting a self-hosted hub requires just one command:

$ coral --hub

One command (coral --hub) runs it on your own machine. Keep it on a trusted network, a VPN or tailnet, or use an encrypted tunnel, since it serves plain HTTP. What Coral Hub does and how it handles your content does not apply to a hub you run yourself.

Closed Beta & Requesting Access

Coral Hub is in closed beta. Request access and tell us which machines you want to connect.