Configuration reference changedthird-party/claude-desktop/configuration
Nearest release: v2.1.252, published 3 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+7added
Lines−7removed
From line
191
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits50to this page, all time
The whole hunk
from line 191, old and new numbered
/
from line 191
191191
192192 **The gateway MUST validate `iss` AND `aud`, not just the signature.** Signature + issuer alone accepts *any* token from the same tenant, including tokens issued to unrelated apps. In `id_token` mode the audience is the `clientId`:
193193
194 ```yaml theme={null} theme={null}
194 ```yaml theme={null}
195195 # LiteLLM example — `audience` is REQUIRED, not optional
196196 general_settings:
197197 litellm_jwtauth:
from line 247
247247
248248 **Extended context** (`supports1m`) is a capability assertion you make about your deployment; only set it for models you've confirmed support the 1M-token window:
249249
250 ```json theme={null} theme={null}
250 ```json theme={null}
251251 [{"name": "claude-sonnet-5", "supports1m": true}, "claude-opus-4-8"]
252252 ```
253253
from line 255
255255
256256 **Default to 1M context** (`prefer1m`) makes the 1M-context variant the default picker selection when this entry is the default model (the first entry); users can still switch to the standard variant, and an explicit user pick is always kept. No effect without `supports1m`. Under dynamic discovery (no explicit list), the equivalent flat key in the **Models** group applies instead:
257257
258 ```json theme={null} theme={null}
258 ```json theme={null}
259259 [{"name": "claude-opus-4-8", "supports1m": true, "prefer1m": true}]
260260 ```
261261
262262 **Display label** (`labelOverride`) is for IDs the picker can't derive a friendly name from (Bedrock ARNs, gateway routing aliases). Display-only; `name` is still what the app sends:
263263
264 ```json theme={null} theme={null}
264 ```json theme={null}
265265 [{"name": "arn:aws:bedrock:us-east-1:123:application-inference-profile/abc", "labelOverride": "Claude Opus (Prod)"}]
266266 ```
267267
268268 **Tier mapping** (`anthropicFamilyTier`) tells the app which Claude tier (`haiku`/`sonnet`/`opus`/`fable`/`mythos`) an entry stands in for, so bare tier aliases (e.g. in Code sessions) resolve to your model. `isFamilyDefault: true` picks the winner when several entries share a tier:
269269
270 ```json theme={null} theme={null}
270 ```json theme={null}
271271 [{"name": "us.anthropic.claude-opus-4-8", "anthropicFamilyTier": "opus"}]
272272 ```
273273
from line 292
292292 <Accordion title="inferenceModelPricing details">
293293 Each row replaces Anthropic list price for one model in the Usage page's estimate, in USD per million tokens (`inputPerMtok`, `outputPerMtok`, `cacheReadPerMtok`, `cacheWritePerMtok` — all four required; `cacheWritePerMtok` prices both 5-minute and 1-hour cache writes); any row also turns the estimate on. Mirrors Claude Code's managed `modelPricing.overrides`, and `name` is matched the same way: a built-in Claude model ID (e.g. `claude-sonnet-4-6`, or its Bedrock, Vertex, or Foundry ID) covers every dated and provider spelling of that model; any other value — a gateway alias, an inference-profile ARN — matches that exact ID only (case-insensitive) and wins over a built-in row. An ID Claude Code cannot map to a Claude model at all gets no estimate until a row here prices it. `inferenceModelPricingMultiplier` still applies on top of a row.
294294
295 ```json theme={null} theme={null}
295 ```json theme={null}
296296 {"inferenceModelPricingEnabled": true, "inferenceModelPricingMultiplier": 0.9, "inferenceModelPricing": [{"name": "claude-sonnet-4-6", "inputPerMtok": 2.4, "outputPerMtok": 12, "cacheReadPerMtok": 0.24, "cacheWritePerMtok": 3}]}
297297 ```
298298
from line 828
828828 <Accordion title="orgPluginSettings details">
829829 Locks per-tool permissions on MCP servers that arrive via the org-plugins directory — one entry per server name:
830830
831 ```json theme={null} theme={null}
831 ```json theme={null}
832832 [{"serverName": "internal-search", "tools": [{"toolName": "delete_document", "permission": "blocked"}]}]
833833 ```
834834
No line in this hunk matches that.