Saeta is in development and has no public release yet. This page describes the current development build and our plans.

Connect an agent deliberately

Different integration modes have different boundaries. A successful connection does not prove that every action is intercepted.

AgentCurrent connectionWhat to check
Claude CodeApproval hookControlled allow and deny, then settings restoration
CursorSupported hook flowReal desktop-client acceptance is still pending
CodexNative hooks; advisory MCP for builds without hooksTrust Saeta's hooks in Codex's /hooks; after an allow, Codex's own approval and sandbox settings still apply
Qwen CodeNative hooksNot yet run against a live Qwen Code; a call nobody answers within 50 seconds goes to its own prompt
OpenCodeNative integrationSupported tool gate; restart the agent after connecting
PiNative extensionSupported tool gate; cancellation and restart acceptance
Gemini CLIAdvisory MCPThe model must choose to call the approval tool
Other MCP clientsAdvisory MCPThe model must choose to call the approval tool

Hook and native integrations

For Claude Code, the installed CLI uses:

saeta install claude-code
saeta status

The other hook and native connections use saeta install cursor, saeta install codex, saeta install qwen-code, saeta install opencode and saeta install pi. Restart the agent after changing the connection, and inspect its reported health in Saeta.

Advisory MCP

Advisory MCP exposes an approval tool and relies on the model using it. It is not a hook that blocks every shell command or file edit. Gemini CLI connects with saeta mcp install gemini-cli. The compatibility guide explains each agent's limits. Do not infer gating from an MCP server appearing connected.

Prove your connection

Use a harmless action first. Check that it reaches the inbox, that your answer returns to the agent, and that a denied gated action does not execute. Test timeout and daemon restart behavior with the settings you intend to use.