ACP fusion
Connect ACP-compatible agents through a shared session so Claude Code, Codex, Copilot, Grok, OpenCode, and future peers can hand work across the same context.
ACP agent workspace
Built on its own Agent Runtime, Caelis coordinates ACP-compatible agents in one shared terminal session and can run as a caelis acp server for clients such as Zed.
Why Caelis
Caelis treats ACP as the bridge between agent clients instead of locking work into one assistant UI.
Connect ACP-compatible agents through a shared session so Claude Code, Codex, Copilot, Grok, OpenCode, and future peers can hand work across the same context.
Drive the workspace from the TUI, a headless one-shot CLI, or expose it through caelis acp to ACP clients such as Zed.
Ask one agent to implement, another to inspect, and keep decisions, command output, and approval traces attached to the session.
Caelis is not just an ACP TUI shell. It includes a reusable Agent Runtime for sessions, tools, sandboxing, permissions, and future memory or GUI surfaces.
FAQ
Caelis is an ACP-native terminal workspace backed by its own Agent Runtime for coordinating multiple coding agents in one shared session.
No. Caelis includes a full Agent Runtime with session orchestration, tools, sandbox-aware execution, permissions, and reusable runtime boundaries.
No. Caelis is designed to connect ACP-compatible agents and let them collaborate through shared context, delegation, and review.
ACP is the connection layer Caelis uses to normalize agent sessions, messages, command context, and future external-agent bridges.
Yes. Caelis can run caelis acp so ACP-compatible clients can use the Caelis runtime and session layer from their own interface.
Use the install command above for macOS, Linux, or Windows, or install the scoped npm package when you prefer a Node-based workflow.
Caelis is still early. The project favors clean ACP boundaries, reusable runtime pieces, and fast iteration before a v1.0 contract.