Ship v2.14.0, verify the numbers, tell the team.

One agent, three tools, zero standing credentials. The agent asks for each credential just in time, you approve the exact scope, and the vault injects it straight into the tool. The secret itself never reaches the agent.

The hard guarantee: the agent never sees a credential value.

Every token below is shown masked, even to you in this demo. The vault hands the real value only to the tool runtime, over a brokered connection, and the agent works with a reference, not the secret. Check the agent context inspector at any point.

0secrets exposed

0Credential requests

0Scopes approved

0Scopes denied

0Leases revoked

0 / 3Steps completed

Agent task view

What release-runner-07 is doing, in its own words.

Idle

1
Deploy checkout-api v2.14.0Production deploy, region us-east, image checkout-api:2.14.0
Queued
2
Verify revenue after deployRead-only query on revenue_daily, last 5 days
Queued
3
Post the release noticeOne message to #releases with deploy and revenue summary
Queued

Agent context inspector

{
  "agent": "release-runner-07",
  "task": "ship-release-v2.14.0",
  "credentials_in_context": 0,
  "note": "No credential has been issued yet. When one is, only its masked reference appears here."
}

Human approval console

You are Abdulsaboor, on call approver. Nothing runs until you decide.

0 awaiting

Active leases

No active leasesApproved credentials appear here with a live expiry. Revoke one at any time.

How approval works here. Each request is scoped to one tool, one action, and a short expiry. Approving mints a single-use lease that the vault injects directly into the tool. Denying does not stop the run. The agent reroutes and keeps going.

Audit trail

Every request, decision, access, and revocation. Immutable, timestamped, attributed.

Export contains masked references only. No credential values are ever written to the log.