Ben Brandt 3d6eb7b5b6 fix: carry the auth detail in the ACP account label (#1573) ...

## Summary

The ACP `auth/status` account (`label`, `active`, `name`, `email`,
`organization`) has no field for the identity's `detail`: an API key's
source, a gateway's host, or "OAuth token". It was only in
`_meta.claudeCode.detail`, so a client that shows the standard fields
could not tell which API key or gateway is in use.

`toAcpAuthStatus` now appends the detail to the account's `label` in
parentheses:

- `Anthropic API key (ANTHROPIC_API_KEY)`
- `Custom model gateway (gw.example.com)`
- `Claude subscription (OAuth token)`

An identity without a detail keeps its label as it was (`Claude Max`).

## Unchanged

- `_meta.claudeCode` still carries `kind`, `detail` and `plan` on their
own.
- The `_auth/status_update` extension payload (`label` and `detail` as
separate fields).
- The mapping is shared, so v1 and v2 report the same label in
`auth/status` and `auth/status_update`.

## Testing

- `src/tests/v1/auth-status.test.ts` expectations updated for the API
key and gateway labels.
- `npm run test:run`, `npm run check` and `npm run build` pass.

2026-11-10 14:21:33 +01:00

..

air-extensions.md

fix: carry the auth detail in the ACP account label (#1573)

2026-11-10 14:21:33 +01:00

model-configuration.md

feat: narrow models to what the providers/set gateway lists (#1340)

2026-10-14 17:03:27 +02:00

RELEASES.md

feat: ship single-file executables built with bun (#1524)

2026-11-04 11:00:25 +00:00