Saeta is in development and has no public release yet. This page describes the current development build and our plans.
Start with the nearest part
No request in the inbox
Run saeta status, check the daemon and connected integration, and restart the agent after connection changes. In advisory MCP mode, the model may not have called the approval tool. A connected server alone does not prove interception.
The sign-in link does not work
Request a new link from the browser where you will open it. Links expire after 15 minutes and work once. A link opened in another browser is refused without spending it. Production sign-in requires HTTPS for the Secure session cookies.
The phone is offline
Check desktop and phone connectivity, the gateway health and the account entitlement. Foreground delivery uses a WebSocket; background delivery depends on configured push and operating-system behavior. Local resolution remains available according to your daemon settings.
Pairing is waiting
Bring the desktop online and open its Devices surface. Compare the desktop and phone verification codes before confirming. Pairing starts from the desktop's own QR; the account page cannot start one.
Saeta reports a configuration change
Review agent settings and the daemon configuration. A same-user process can modify these files; Saeta is a guardrail, not containment. Do not blindly restore or overwrite unrelated settings to resolve a connection warning.