Lists the agent tokens you may see: all of them with a team-wide agent token or a person who manages members, your own otherwise. Secrets are never shown after creation.
Usage
overlane token list [--service URL] [--team TENANT_ID]Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--service |
string | no | The service address (default: OVERLANE_SERVICE_URL, then the project’s binding, then the hosted service) | |
--team |
string | no | The team (tenant) to act on (default: the one your token belongs to) |
Examples
overlane token listBehavior
- Effect:
read(changes nothing). - Needs credentials: yes. Uses the network: yes.
- Supports
--dry-run: no. Accepts--force: no. - Machine-readable description:
overlane schema token list.
Result
With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.
{
"type": "object",
"properties": {
"tenantId": {
"type": "string"
},
"tokens": {
"type": "array",
"items": {
"type": "object",
"properties": {
"tokenId": {
"type": "string"
},
"label": {
"type": "string"
},
"scope": {
"type": "string"
},
"tools": {
"type": "array",
"items": {
"type": "string"
}
},
"expiresAt": {
"type": "string"
},
"revokedAt": {
"type": "string"
},
"createdBy": {
"type": "string"
}
},
"required": [
"tokenId",
"label",
"scope",
"tools",
"expiresAt",
"createdBy"
],
"additionalProperties": false
}
}
},
"required": [
"tenantId",
"tokens"
],
"additionalProperties": false
}See exit codes for the status the process returns.