Cursor Cloud Agents
Cloud agents authenticate as the Cursor team that owns them.
Cloud agents authenticate as the Cursor team that owns them.
Identity proof
The token has to come from https://api.cursor.com, and its team_id claim has to match the workload you named. We compare that claim byte for byte, with no wildcards.
team_id is matched rather than sub, which on this platform does not name the workload in a form you can pin.
Every token also has to name your workspace as its audience. Ask for this audience and no other. A token requested for two audiences fails every exchange.
Console fields
| Field | Example | Advanced | What it pins |
|---|---|---|---|
| Team ID | 123456 | no | A number. The snippet's decode line prints it from a real token. Every agent of the team matches. |
The console also asks which project and environment this identity reaches and which role it gets, with the credential lifetime behind Advanced.
Trust
Built from the example answers above:
| What | Value |
|---|---|
| Issuer | https://api.cursor.com |
| Claim compared | team_id |
| Subject | 123456 |
| Identity name | cursor-123456 |
We name the identity for you, so the form never asks for one.
Console snippet
T=$(curl -sS --unix-socket "$CURSOR_AGENT_SOCKET" \
-H 'Content-Type: application/json' -d '{"aud":"YOUR_WORKSPACE_ID"}' \
http://cursor-agent/v1/tokens/oidc | jq -r .token)
# Run this line once and paste what it prints into penv's Team ID field.
echo "$T" | jq -rR 'split(".")[1] | gsub("-";"+") | gsub("_";"/") | @base64d | fromjson | .team_id'
C=$(curl -sS "https://penv.cloud/api/v1/auth/oidc" \
-H 'content-type: application/json' \
-d "{\"token\":\"$T\"}" | jq -r .credential)
PENV_TOKEN="$C" penv pullThe snippet finishes with penv pull, which writes a file. We recommend penv run for a process; penv pull is for a host that needs a file on disk. Connect your CI has the wrapped step.
Related
- Machine identity
- Connect a Platform in the console
- Cursor Cloud Agents documentation: the subject is the value most often set wrong