Available settings changedgovernment/config/settings
Nearest release: v2.1.301, published 6 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 15 Oct 2026 20:39 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 15 Oct 2026 21:07 UTC.
Upstream edited
Recorded here
Lines+12added
Lines−7removed
From line
56
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits35to this page, all time
The whole hunk
from line 56, old and new numbered
/
from line 56
5656
5757Point this address at a receiver that accepts OTLP over HTTP in both its protobuf and JSON encodings. An [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) does this by default and conventionally listens for OTLP over HTTP on port 4318. If your logging or SIEM platform accepts only its own HTTP ingestion format, run an OpenTelemetry Collector that receives OTLP and forwards to that platform, and enter the collector's address here.
5858
59Claude Desktop on each member's device connects to this address itself rather than through the Claude for Government service. The collector must therefore be reachable from your members' networks and must present a TLS certificate that their operating system trusts.
59Each application connects to this address from the member's device rather than through the Claude for Government service. The collector must therefore be reachable from your members' networks and must present a TLS certificate that their operating system trusts.
6060
61Members pick up a new or changed endpoint the next time they start Claude Desktop. Once a member has signed in and the app has loaded their configuration from Claude for Government, it takes its telemetry settings from that configuration alone and ignores telemetry keys set on the device itself, such as the `otlp*` keys in the Claude Desktop [configuration reference](/docs/third-party/claude-desktop/configuration). From then on your collector receives OpenTelemetry logs and metrics for each member's activity under three `service.name` values:
61Members pick up a new or changed endpoint the next time they start Claude Desktop. Once a member has signed in and the app has loaded their configuration from Claude for Government, it takes its telemetry settings from that configuration alone and ignores telemetry keys set on the device itself, such as the `otlp*` keys in the Claude Desktop [configuration reference](/docs/third-party/claude-desktop/configuration). From then on your collector receives OpenTelemetry logs and metrics for each member's Claude Desktop activity under three `service.name` values:
6262
6363* `cowork` for Chat and Cowork activity
6464* `claude-code-desktop` for Code sessions
from line 68
6868
6969Claude Desktop keeps working when the collector refuses requests or cannot be reached, and members see no error. To confirm telemetry is arriving, check your collector's own request logs or metrics for requests to `/v1/logs` after a member has restarted Claude Desktop and sent a message.
7070
71Claude for Microsoft 365 and the Claude Code command-line tool send their records to the same collector, each under its own `service.name`, and identify the member by their sign-in email address as `user.email`:
72
73* `office-agent` for Claude for Microsoft 365. The add-in sends its telemetry from the add-in pane, a web page loaded from your Claude for Government host, so the collector must also accept [cross-origin requests from that host](/docs/government/deploy-microsoft-365/configure#before-you-begin). See [What the collector receives](/docs/office-agents/opentelemetry#what-the-collector-receives) for the add-in's records and their attributes.
74* `claude-code` for the Claude Code command-line tool. See [Monitoring](https://code.claude.com/docs/en/monitoring-usage) in the Claude Code documentation for its records and their attributes.
75
7176### Telemetry headers
7277
7378Headers sent with every telemetry request, typically the credential your collector requires. Each member's app receives these headers and sends its telemetry directly, so use a credential that can only send data to your collector. Leave the setting empty if your collector does not require one. Because the value may contain a secret, it is never displayed after you save it; you see only that it is set.
from line 95
9095
9196### Telemetry traces
9297
93Sends a trace for each request in Cowork and Code sessions to the `/v1/traces` path of the address in **Telemetry endpoint**, so your monitoring tools can follow the events of one request together. The setting is off by default and is in beta. Traces carry message and tool content only for the categories selected in **Telemetry content capture**. [Traces](/docs/third-party/claude-desktop/telemetry#traces-beta) in the Claude Desktop telemetry reference describes what a trace contains.
98When on, each application also sends traces to the `/v1/traces` path of the address in **Telemetry endpoint**, so your monitoring tools can follow the events of one request together. The setting is off by default and is in beta. Traces carry message and tool content only for the categories selected in **Telemetry content capture**. For what a trace contains, see [Traces](/docs/third-party/claude-desktop/telemetry#traces-beta) for Claude Desktop and the [span reference](/docs/office-agents/opentelemetry#span-reference) for Claude for Microsoft 365.
9499
95100<Note>
96 **Telemetry traces** applies to Claude Desktop 1.22209.0 and later. Earlier versions ignore the setting.
101 In Claude Desktop, **Telemetry traces** requires version 1.22209.0 or later. Earlier versions ignore the setting.
97102</Note>
98103
99104### Block automatic updates
No line in this hunk matches that.