/connectChoose the right backend
Connect a model provider or a local ACP agent. Both become consistent Model Profiles instead of leaking backend details into your work.
TERMINAL-FIRST AGENT RUNTIME
Connect model providers and ACP agents, bind specialists, and run every turn inside one guarded, resumable workspace.
curl -fsSL https://caelis.dev/install.sh | sh
Copied
type / for commands
The current responsive welcome surface — connect, resume, or start typing.
ONE WORKSPACE, THREE MOVES
Caelis turns a collection of models, local agents, and tools into one intentional terminal workflow.
/connectConnect a model provider or a local ACP agent. Both become consistent Model Profiles instead of leaking backend details into your work.
/subagentUse Breeze for bounded work, Orbit for implementation, and Zenith for deep or high-risk analysis — each with an explicit profile and reasoning effort.
/reviewGuardian reviews tool access; Reviewer inspects the result. Sandbox boundaries and approval prompts stay part of the same session.
CONTROL WITHOUT LOCK-IN
Provider models and external ACP agents enter through the same Control layer. Roles stay stable even when the backend changes.
Read the architecture →One guarded, resumable Session
/zenith Audit @docs/architecture.mdTHE TERMINAL IS THE PRODUCT
The new TUI keeps command and Skill discovery under /, file references under @, and long tasks in stable semantic states instead of noisy control traces.
ONE RUNTIME, THREE SURFACES
Start with caelis for the full interactive workspace, command discovery, approvals, and session control.
Use caelis -p for one-shot prompts with text or JSON output in scripts and automation.
Run caelis acp and expose the same runtime to compatible editors and external agent clients.
BRING YOUR STACK
Use subscription sign-in, API providers, local models, ACP agents, MCP servers, Skills, and Plugins without rebuilding your workflow around one vendor.
LOCAL-FIRST BY DEFAULT
Sessions, execution history, configuration, and workspace context live on your machine. Native sandbox backends constrain tools; Guardian and explicit approvals handle the edges.
FAQ
A terminal-first agent runtime with an interactive TUI, a headless CLI, and an ACP stdio server. It owns the local workspace, Session, tool, sandbox, and approval boundaries around your agents.
No. Caelis includes its own local runtime. ACP is an additional interoperability path for connecting local agents and external clients.
The guided flow currently includes Codex, Claude Code, OpenCode, CodeFree-O, and Grok, plus custom ACP stdio commands.
Caelis supports guided browser or device sign-in for eligible ChatGPT Codex and Grok subscriptions, alongside API-key and local provider paths.
Under ~/.caelis by default, with an override available through -store-dir.
START IN YOUR TERMINAL