You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cc54abf
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix: display the selected wire provider as JetBrains Air Gateway (spacering-net#589)
### Summary
Addresses [IJAI-2956](https://youtrack.jetbrains.com/issue/IJAI-2956).
- Classify the **selected agent-owned** provider ID returned by
`getAgentConfiguredModelProvider()` as a gateway when it equals `wire`
after trimming, case-insensitively.
- Emit `kind: gateway` and the exact label `JetBrains Air Gateway`, with
no `detail` or invented account identity. Do not fetch or inspect the
provider's friendly `name`, URL, backend, or route.
- Preserve effective configuration/launch-override precedence and the
separation between authentication identity and client-owned ACP
`providers/set`; an unused wire provider does not affect auth status.
- Use the same classification for the initial status and subsequent
updates; retain existing behavior for other providers.
- Add regression coverage for case/whitespace, active selection and
overrides, friendly-name negatives, client-owned providers, exact
payloads, and source switching; update `docs/air-extensions.md`.
This is an agreed weak display heuristic, not proof that the endpoint is
a Central deployment or that the user has any particular entitlement. A
different selected provider ID does not match merely because its
friendly name contains `wire`.
### Sanitized auth status
```json
{
"kind": "gateway",
"label": "JetBrains Air Gateway"
}
```
No keys, headers, private routes, technical `wire` detail, or invented
account information is sent.
### Verification
Based on fresh upstream `main` at `ca1d971`, rechecked immediately
before publication. Changes and rebuilt `dist` are available in the main
local clone; the user confirmed the local adapters work.
```bash
npm run typecheck
npm run build
npm test
```
- Typecheck (including examples) and build passed.
- Full test suite: **1218 passed, 33 existing skipped** across 76 passed
test files and 6 skipped opt-in e2e files.
- Auth-status coverage: 33 tests passed in the targeted run and the full
suite.
- No new skip flags or disabled tests were used.
### Scope
No AIR UI, provisioning, personal configuration migration, effort/mode
changes, or new ACP protocol. Plan files and personal configurations are
not committed.
Co-authored-by: Junie <[email protected]>
Co-authored-by: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: docs/air-extensions.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -245,6 +245,18 @@ The adapter keeps them where they are.
245
245
|`quota`|`PromptResponse._meta.quota`| Token usage of the whole turn, the same counts as `PromptResponse.usage`: `token_count` and one `model_usage` entry for the current model, or `null` and `[]` when Codex reported no usage for the prompt, as for a prompt that started no turn. |
246
246
|`authStatus`|`initialize` response `agentCapabilities._meta.authStatus`| The agent pushes `_auth/status_update`. The object carries no payload. |
247
247
248
+
## Auth source display
249
+
250
+
The agent-owned provider ID comes from `getAgentConfiguredModelProvider()`: launch options take priority over the effective app-server `configRead`, and client-owned `providers/set` routing is ignored for identity reporting.
251
+
252
+
An active `model_provider` ID equal to `wire` after trimming whitespace and ignoring case is displayed as:
The configured friendly `name`, URL, host and route are not checked. An unused provider or another ID whose friendly name is `wire` does not match. This is a weak display heuristic, not proof of configuration provenance or access rights. This payload omits `detail` and `account` and contains no keys, headers or private routes. Both the initial push and subsequent status publication use the same classification and existing duplicate suppression. Other providers and gateway authentication names retain their previous presentation.
259
+
248
260
## Zed conventions
249
261
250
262
The adapter keeps these Zed conventions for every client:
0 commit comments