# scope_missing

> This token lacks a required scope. The token you are using does not include a scope this action needs.

**This token lacks a required scope.** The token you are using does not include a scope this action needs. Agent tokens only carry the scopes their owner chose.

- **HTTP status:** `403 Forbidden`
- **CLI exit code:** `3` (forbidden or denied by policy)
- **Retry:** not as it is; the same request will fail the same way until the cause is fixed

## How to fix it

Create a token with the {scope} scope.

Words in `{braces}` are filled in from the error response, which names the exact resource.

## If you are an AI agent

Tell the human which scope is missing (it is in the problem's `required_scopes`). Do not ask for broader access than the task needs.

## What the response looks like

```json
{
  "type": "https://guv.dev/errors/scope_missing",
  "title": "This token lacks a required scope",
  "status": 403,
  "code": "scope_missing",
  "detail": "The token you are using does not include a scope this action needs.",
  "fix": "Create a token with the {scope} scope.",
  "docs_url": "https://guv.dev/errors/scope_missing",
  "request_id": "req_01jbx2m9k7q4r8t5v6w3y0z1rq"
}
```

The `code` field is stable: match on it, not on `title` or `detail`, which may be reworded.