One read of Claude Documentationclaude-docs-20261023T230705Z
4 pages moved out of 280 read.
Pages moved
4
significant first
Pages read
280
in this capture
Captured
23:07 UTC
Corpus hash
69c7771faae3
corpus-hash
What this read moved
1-4 of 4third-party/claude-desktop/claude-api Changed · +8 / -0 lines
## Which devices offer the Claude API account sign-in
from line 16
1616
1717[Code](https://claude.com/docs/third-party/claude-desktop/code.md) sessions also ask Anthropic for the Claude Code [server-managed settings](https://code.claude.com/docs/en/server-managed-settings) of the organization that owns the credential. See [Interaction with Claude Code's own managed settings](https://claude.com/docs/third-party/claude-desktop/code.md#interaction-with-claude-code%E2%80%99s-own-managed-settings) for how they combine with your Claude Desktop configuration.
1818
19## Which devices offer the Claude API account sign-in
20
21On a device with no Claude Desktop configuration, the standard sign-in screen in Claude Desktop 3.1623.1 or later also links to a screen titled **Use your Claude API account**. There a user can click **Sign in with Claude Console** or enter an API key, with no setup from you.
22
23Claude Desktop doesn't offer or accept that sign-in on a device where an [MDM profile or registry policy](https://claude.com/docs/third-party/claude-desktop/mdm.md#4-deploy-the-configuration), or the [root-owned configuration file on Linux](https://claude.com/docs/third-party/claude-desktop/configuration-format.md#the-linux-configuration-file), manages the configuration. To confirm that a profile manages a device's configuration, check that the [in-app configuration window](https://claude.com/docs/third-party/claude-desktop/in-app-configuration.md#open-the-configuration-window) (**Developer > Configure Third-Party Inference…**) opens read-only on that device. If the window is still editable, the profile doesn't manage the configuration, for example because it sets only [app-behavior keys](https://claude.com/docs/third-party/claude-desktop/mdm.md#update-keys-and-managed-precedence). A profile takes effect at the app's next launch, and until then a running app can still offer and accept the sign-in.
24
25Under a profile that manages the configuration, the app ignores any configuration that an earlier Claude API account sign-in saved. A profile can itself select the Claude API with no static key or credential helper. Users then sign in with **Sign in with Claude Console**, and each selects the Console organization that their usage is billed to, as described under [Choose an authentication approach](#choose-an-authentication-approach). A user who already signed in with Claude Console keeps that sign-in, and the Console organization they chose, until the app next asks them to sign in.
26
1927## Configure the app
2028
2129### Configuration keys
claude-science/changelog Changed · +1 / -0 lines
from line 12
1212
1313October 21, 2026
1414
15* As a precaution following the publicly reported compromise of several emSign (eMudhra) intermediate certificate authority (CA) keys, most of the connections Claude Science makes itself, and many of the package installs it runs itself, no longer trust emSign (eMudhra) root certificates or one other root certificate. Versions 0.1.69 and later include all of these changes; to update, see [Update Claude Science](https://claude.com/docs/claude-science/update-claude-science.md)
1516* A new **Trouble updating?** link opens [Update Claude Science](https://claude.com/docs/claude-science/update-claude-science.md), a help page with other ways to update. It shows in **Settings > General > About**, in the **Update required** box, and on the "Update available" notice while an update downloads or after one fails
1617* Cloud storage in Settings now works with Google Cloud Storage HMAC keys on computers where no AWS region is set
1718* Mac: if `config.toml` has `auto_update = false` under `[update]`, Claude Science in its own window no longer checks for updates in the background. You can still check with **Claude Science > Check for App Updates…** in the menu bar
cowork/monitoring Changed · +4 / -0 lines
from line 169
169169| `output_tokens` | Number of output tokens |
170170| `cache_read_tokens` | Number of tokens read from cache |
171171| `cache_creation_tokens` | Number of tokens used for cache creation |
172| `cache_creation_5m_tokens` | Portion of `cache_creation_tokens` written with a 5-minute cache lifetime |
173| `cache_creation_1h_tokens` | Portion of `cache_creation_tokens` written with a 1-hour cache lifetime |
172174| `speed` | `"fast"` or `"normal"` |
175
176Claude Desktop 3.1623.0 and later send `cache_creation_5m_tokens` and `cache_creation_1h_tokens`. Both are `0` when the API response doesn't report the split, even when `cache_creation_tokens` is above zero. If your deployment uses an [LLM gateway](https://claude.com/docs/third-party/claude-desktop/gateway.md), confirm that the gateway returns the `cache_creation` object in each response's `usage`.
173177
174178### API error event
175179
third-party/claude-desktop/gateway Changed · +2 / -0 lines
from line 11
1111
1212The gateway should also preserve [prompt caching](https://platform.claude.com/docs/en/build-with-claude/prompt-caching). Cowork and Code sessions send `cache_control` breakpoints with each turn so that the provider can reuse the tool definitions, system prompt, and earlier turns of the conversation instead of reprocessing them. A gateway that forwards these fields, or translates them for its upstream provider, keeps that behavior. A gateway that strips `cache_control`, or that changes the system prompt or tool list from one request to the next, makes the provider reprocess the whole conversation on every turn at full input-token cost and higher latency. To verify, check the [usage fields](https://platform.claude.com/docs/en/build-with-claude/prompt-caching#tracking-cache-performance) your gateway returns or logs for Claude Desktop traffic: after the first request of a session, `cache_read_input_tokens` should be well above zero on most requests. If it is zero on every request, review the gateway's request transformation and caching settings for the route that serves Claude models.
1313
14In each response's `usage`, return the provider's `cache_creation` object with its `ephemeral_5m_input_tokens` and `ephemeral_1h_input_tokens` fields. Without that object, the [API request event](https://claude.com/docs/cowork/monitoring.md#api-request-event) in your OpenTelemetry export reports `0` for both `cache_creation_5m_tokens` and `cache_creation_1h_tokens`.
15
1416## Choose an authentication approach
1517
1618| Scenario | Use | Notes |