hecateAgent runtime + operator console
Connect models and coding agents, launch work with an explicit workspace and runtime posture, review approvals and diffs, and trace what happened—from one operator console.
Stable pre-1.0 · macOS Apple Silicon launch-tested · Linux and Windows experimental
Compatible by design
Hecate runs its own durable Tasks, supervises installed coding-agent CLIs through ACP, and exposes its native runtime to ACP-capable clients.
External Agent CLIs are installed separately. Their vendor accounts, billing, and internal runtime stay with them.
Operator loop
Prepare the work, run the right agent, follow what happens, and review the result without losing the execution boundary.
Connect model providers and choose the workspace. Agent Presets shape model routing, instructions, and Hecate-owned execution posture; External Agent presets select the agent and its launch options.
Start a Hecate Chat, queue a durable Hecate-native Task, or open a supervised External Agent session through ACP.
Follow streamed activity, stop work, and resolve approvals when Hecate policy or an External Agent requests them.
Inspect final output, artifacts, Git diffs, route decisions, traces, token usage, and provider-reported cost where available—then retry, resume, or hand the work off.
Change review
Keep the transcript beside its Task Run, trace, files, and Git diff. Hecate preserves the evidence needed to understand what changed and why.
Agent Client Protocol
Use Hecate as the console around external agents, or use Hecate's native runtime from another ACP-capable client.
Agents → Hecate
Codex, Claude Code, Cursor Agent, and Grok Build connect through ACP. Hecate adds session supervision, optional diagnostics, permission handling, and Git diff review without taking over their accounts or internal runtime.
Hecate → ACP clients
hecate acp serve turns ACP prompts into durable Tasks and Runs while Hecate retains routing, policy, approvals, artifacts, and observability.
Embedded Cairnline owns portable project identity, roles, work items, assignments, and handoffs. Hecate resolves that intent into presets, routes, workspaces, and execution; coordination records never grant runtime permission by themselves.
Operator control
Hecate-native Tasks keep tool posture, blocking approvals, artifacts, and run state in view. External Agent approvals appear when their ACP adapter requests permission; Hecate does not claim universal interception inside a vendor CLI.
Observability
Inspect route choices, skipped providers, timing, trace spans, token usage, and provider-reported cost where available. The trace ID stays attached to the work that produced it.
Run it where the work lives
Start with the desktop app, run Hecate on infrastructure you control, or use Hecate Cloud for hosted and authenticated remote access.
Linux and Windows bundles are CI-built but have not completed the same real-machine installation smoke tests as macOS Apple Silicon.
Execution boundary
Stable pre-1.0
Hecate is useful today while its APIs, storage, and operational behavior continue to evolve across stable v0.x releases.