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

The workflow

A pause before the action.

A local daemon connects your agents to one approval inbox. You decide where supported requests go next.

Connect, review, decide

A supported integration sends a proposed action to Saeta. The daemon checks your trust list, and requests that need a person appear in the inbox. A decision resolves the request and returns to the integration.

  1. Agent integration
  2. Local daemon & trust list
  3. Your inbox
  4. Your decision

Understand your integration

Hooks and native integrations can gate supported actions. Advisory MCP relies on the model calling the approval tool; it does not intercept every shell command or file edit. Check the integration guide before relying on a connection.

Take the inbox with you

Sign in on your desktop, pair a phone and compare the verification codes on trusted devices. The desktop seals each remote request for the paired phone. The phone decrypts it and returns a sealed, signed decision.

When the network goes away

Local resolution and configured timeouts remain available. The desktop shows remote availability. Gateway restarts keep account and pairing records, but pending relay caches are held in memory and need reconciliation with the desktop.

Read the setup guide →