Lists each use of the decision model (review risk, hostile content, agent intent) with whether it is on, the confidence threshold and the margin. Every use is off until a team switches it on. Any role may read it.
Usage
overlane decision settings [--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 decision settingsBehavior
- Effect:
read(changes nothing). - Needs credentials: yes. Uses the network: yes.
- Supports
--dry-run: no. Accepts--force: no. - Machine-readable description:
overlane schema decision settings.
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"
},
"settings": {
"type": "array",
"items": {
"type": "object",
"properties": {
"use": {
"type": "string",
"enum": [
"review_risk",
"hostile_content",
"agent_intent",
"failure_cause",
"task_signal"
]
},
"enabled": {
"type": "boolean"
},
"threshold": {
"type": "number"
},
"margin": {
"type": "number"
},
"updatedAt": {
"type": [
"string",
"null"
]
}
},
"required": [
"use",
"enabled",
"threshold",
"margin",
"updatedAt"
],
"additionalProperties": false
}
}
},
"required": [
"tenantId",
"settings"
],
"additionalProperties": false
}See exit codes for the status the process returns.