Skip to main content
Revoking a session ends it before it expires. Within one poll interval (60 seconds by default), the proxy stops attaching credentials to the agent’s requests. You can’t reactivate a revoked session, so to give the agent access again, create a new session. Revoke a session when:
  • Its agent finishes, even if the agent fails
  • You think its session token leaked, because anyone with the token can call every API in the session’s access bundle until the session ends
  • The agent no longer needs access, such as a long-running agent you’re shutting down
These people and machine identities can revoke a session:
  • Admins of the Agent Vault project, for any session in the project
  • Members of the project, for their own sessions
  • A machine identity, for the sessions it created, including sessions it created on behalf of a user
  • Anyone who holds the session’s token

Revoke the session

In your Agent Vault project, go to Sessions, open the session’s menu, and select Revoke Session.If you’re an admin of the project, select All Sessions to find sessions that other users and machine identities created.

Revoked sessions

Revoking a session doesn’t remove the skills that the CLI already installed on the agent’s host. To stop agents from using those skills, delete the installed copies.

Sessions left active

If the agent’s machine shuts down mid-run, or your code exits before it revokes the session, the session keeps working until it expires. To limit how long that can last, set the session’s duration a little longer than the agent’s longest run, instead of never.

Troubleshooting

Nothing revoked the session. This happens if:
  • The machine shut down, or the CLI’s process was killed, before the CLI could revoke the session
  • Your code exited before it reached the revoke call
Revoke the session on the Sessions page, or let it expire.
The access token you sent expired. Log in again to get a new access token, then revoke the session.