Sessions

Time-bound grants that let AI agents access services without holding real credentials.

A session is a time-bound grant in an Agent Vault project. It’s scoped to one access bundle, to inline services that an admin sends with the session, or to both. Infisical returns a session token that identifies the session, and the agent uses that token to authenticate to the proxy on every outbound request. The proxy then attaches the real credential from the matching service at the network boundary.

Every session expires on a schedule you set. When the session expires (or you revoke it), the proxy stops attaching credentials to the agent’s requests within one poll interval.

A session only works through a proxy in the same project as its access bundle.

​

Create a session

Anyone granted at least one access bundle in a project can create a session in that project. Admins of the project can create one with any of its access bundles.

If you want to create sessions programmatically, you can have a machine identity create a new session for each run using the CLI, the API, the Python SDK, or the Node.js SDK. A machine identity can also create sessions on behalf of users, so that each agent uses the personal values of the person it runs for and gets no more access than that person.

Dashboard

1. In your Agent Vault project, go to Sessions and select Create Session.

2. Pick the Access Bundle the agent should use, optionally enter a Label that says what the session is for, set a duration under Expires, then select Create Session.

   
3. Copy the command shown. The session token appears once and can’t be retrieved again.

   

Hand the copied command to whoever will start the agent. No Infisical login is needed on that machine.

You can also pass the token in the environment instead:

export INFISICAL_AGENT_VAULT_SESSION_TOKEN=<session-token>
infisical agent-vault run --proxy <proxy-address> -- claude

CLI

infisical agent-vault sessions create creates a session with the access bundle you name and prints the session token. Replace <project-id> with the ID of your Agent Vault project (find the project ID):

export INFISICAL_AGENT_VAULT_PROJECT_ID=<project-id>
infisical agent-vault sessions create --access-bundle <bundle-name> --ttl 8h

Set the duration with --ttl, which takes a value like 30m, 8h, 7d, or never, and defaults to never. To label the session, pass --label.

To create a session and start the agent in one command, pass the access bundle to infisical agent-vault run instead. The CLI revokes that session when the agent exits:

infisical agent-vault run --access-bundle <bundle-name> --proxy <proxy-address> -- <agent-command>

The CLI creates the session as your user by default, or as a machine identity when you pass --client-id and --client-secret (or their environment variables). For a full example, see Create sessions with the CLI.

API

Call the endpoint that creates a session with the ID of your Agent Vault project, the access bundle’s name, a ttl, and optionally a label:

curl -X POST https://app.infisical.com/api/v1/agent-vault/sessions \
  -H "Authorization: Bearer <access-token>" \
  -H "Content-Type: application/json" \
  -d '{"projectId": "<project-id>", "accessBundle": "<access-bundle-name>", "ttl": "1h", "label": "nightly deploy"}'

The response includes the session token.

Picking Never as the duration keeps the session working until someone revokes it. Only use this for long-running agents, and revoke the session once the agent has finished.

​

Label a session

A label is a short description of what a session is for, such as nightly deploy or support ticket triage. If one identity creates many sessions, the label is how you tell the sessions apart on the Sessions page, and you can search sessions by their label. A label can be up to 128 characters, and can’t contain line breaks, tabs, or invisible characters such as zero-width spaces.

You can add, change, or remove a session’s label, even after the session expires or is revoked:

• In your Agent Vault project, go to Sessions, open the session’s menu, and select Add Label or Edit Label
• From an agent or a script, call the endpoint that updates a session, for example to record what the agent is working on

​

View session logs

Session logs record every request an agent makes during a session. To view them, go to Sessions in your Agent Vault project and select View Session Logs on the session’s row. You can filter and search the requests, and while the session is active, new logs keep appearing.

​

Revoke a session

To revoke a session before it expires, go to Sessions in your Agent Vault project, open the session’s menu, and select Revoke Session. The proxy stops attaching credentials for the session within one poll interval.

The Sessions page shows each session as Active, Revoked, or Expired, and keeps expired and revoked sessions so you can audit what an agent had access to during the session:

​

Access changes

The access bundle and any inline services are chosen when you create the session and can’t be changed afterwards. However, the proxy re-checks whether the agent still gets credentials once every poll interval (60 seconds by default). Here’s how common access changes affect a session:

• If someone no longer has any grant on an access bundle, directly or through a group, their sessions for that bundle stop getting credentials
• If someone still has another grant on the bundle, such as through a group, revoking one grant doesn’t affect their sessions
• If you delete an access bundle, every session scoped to it stops getting credentials (the session still lists the bundle’s name, so you can see what it was)
• If you remove someone from the project, the proxy refuses every request on their sessions
• If the user or machine identity that created a session loses the Admin role in the project, the session stops getting credentials for its inline services

None of these changes removes the skills that the CLI already installed on the agent’s host. To stop agents from using those skills, delete the installed copies.

If a session stops getting credentials because of a lost grant, a deleted bundle, or a lost Admin role, the proxy still forwards the agent’s requests, without credentials. Whether those requests reach the upstream host depends on the proxy’s traffic policy.

​

Audit trail

When you create a session, change its label, or revoke it, Infisical writes an audit event. To review these events, open Audit Logs in your Agent Vault project, or scope an audit log stream to the Agent Vault product.

Audit events cover what you changed in Infisical. To see which requests an agent made while its session was running, view its session logs.