Pasted once, used at call time.

Secrets

• A secret belongs to one environment and has a name like GITHUB_TOKEN. Names are upper-cased and normalized.
• Values are encrypted under the environment's own data key (AES-256-GCM) and never returned by any screen or API.
• A server references a secret; at call time the gateway decrypts it, adds the header, forwards the call and forgets the value.
• Rotate a secret and every server using it picks up the new value on the next call. Deleting a secret still used by a server is refused.
• Deleting an environment destroys its data key: its secrets become unreadable instantly.

OAuth servers

Linear, Notion, Sentry and the other OAuth servers are authorized from the dashboard. Exorails discovers the server's authorization server (RFC 9728, RFC 8414), registers itself as a client (a hosted Client ID Metadata Document, or dynamic registration when the server prefers it) and runs an authorization-code flow with PKCE. The tokens go into the environment's vault and are refreshed automatically before they expire.

When a refresh fails, the server switches to “needs authorization”, the agent gets a readable error, and the owners receive one email. Authorize again from the Tools tab.

What is logged

The call log keeps the tool name, the agent, the status, latencies and sizes. Arguments and results are not stored unless you turn on argument logging for an environment, and even then a secret-pattern redactor runs first. See the Security page for the full picture.