Give your agent accesswith a sealed secret

Let your agent use your secrets without seeing them.

Secrets for
one session.

Give your agent the secrets a task needs, without setting up a vault or password manager. Approve their use, then forget them when you’re done.

Interactive example
Your private window

Confirm this export?

Agent’s reason“Confirm the report export.”

Allowed request
api.example.com
POST /v1/exports/confirm

From your phone.
To your agent.

Coming soon. Phone and remote handoffs are paused while we complete the independent protocol review. Local handoffs are available now.

From your phone

Check the pairing codes. Your phone encrypts the secret for the requesting tool.

For a remote agent

The remote tool holds the secret in memory. You confirm the handoff before use.

Know where
the secret goes.

The local tool holds your secrets in memory and applies them to approved requests, keeping their values out of the AI’s context.

Control where the secret is used.

You approve the API host, method, and path.

In memory, for the session.

Forget secrets at any time. Closing the tool clears them.

No secrets in the chat.

Your agent gets a reference and redacted results. The secret stays out of its context.

Security boundaries

The approved API receives the credential and may retain it. Forgetting it in Secret Handoff does not revoke it at the provider.

Unfilled requests and one-time links expire. A secret held by the local tool has no automatic time limit after filling. It remains until explicitly forgotten or the tool process ends.

This is not a hard boundary against processes running as you. Separately approved commands receive the value and can leak it. Ordinary one-time links let their recipient read the value.

Let your agent
handle setup.

One prompt to get set up.

Send this to your agent