Home Docs Claude Documentation 21 Oct 2026

One change · claude-docs

Available settings changedgovernment/config/settings

Nearest release: v2.1.307, published an hour after 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 21 Oct 2026 18:58 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 22 Oct 2026 18:07 UTC.

Upstream edited 21 Oct 2026 18:58 UTC

Recorded here 22 Oct 2026 18:07 UTC

Lines+32added

Lines−32removed

From line 4 where the diff opens

First seen 14 Aug 2026 this site's first read of the page

Recorded edits36to this page, all time

The whole hunk

from line 4, old and new numbered

lines

from line 4

55> **Who this is for:** Tenant administrators and organization owners who set product behavior for the people they manage.

7Find each setting on the **Config** page in the admin portal under its category in that page's sidebar. Each setting can be set at both the tenant and organization level unless noted otherwise. To set a value for a directory group, see [Group-specific settings](/docs/government/config/overview#group-specific-settings). For how the levels combine, what locking does, when a change reaches members, and how to compare and preview, see [How Config works](/docs/government/config/overview).

7Find each setting on the **Config** page in the admin portal under its category in that page's sidebar. Each setting can be set at both the tenant and organization level unless noted otherwise. To set a value for a directory group, see [Group-specific settings](/docs/government/config/overview.md#group-specific-settings). For how the levels combine, what locking does, when a change reaches members, and how to compare and preview, see [How Config works](/docs/government/config/overview.md).

99Where **Applies to** gives a version, earlier versions ignore the setting. The **Config** page can show settings that are not listed here.

1010

from line 20

2020| **Advanced file analysis in Chat** | Lets Claude run code in a sandbox for data analysis in Chat. Only takes effect where **Shell commands** and **Chat in Claude Desktop** are both on. Without this setting, Claude cannot read Word, Excel, or PowerPoint files that members attach in Chat. | On | Claude Desktop |

2121| **Cowork in Claude Desktop** | Lets members give Claude longer tasks, such as research, analysis, and drafting documents, which it works through on its own in Claude Desktop. Without Cowork, members cannot continue their Cowork tasks. | On | Claude Desktop |

23| **Scheduled tasks** | Lets members set up [tasks that Claude runs on a schedule](/docs/third-party/claude-desktop/configuration#scheduledtasksenabled). Turning it off also turns off scheduling in Claude Code, such as `/loop`. | On | Claude Desktop 2.110.0 or later, Claude Code |

23| **Scheduled tasks** | Lets members set up [tasks that Claude runs on a schedule](/docs/third-party/claude-desktop/configuration.md#scheduledtasksenabled). Turning it off also turns off scheduling in Claude Code, such as `/loop`. | On | Claude Desktop 2.110.0 or later, Claude Code |

2626

27Turning off **Claude Desktop**, **Claude Code**, or **Claude for Microsoft 365** stops the members the setting applies to from using that application. An organization cannot turn on a product that the tenant has turned off. These switches turn applications off, not accounts, and are not a security boundary: to cut one member off from everything at once, deactivate their account (see [Deactivated users](/docs/government/org-admin/users#deactivated-users)).

2828

2929The **Claude Desktop home** row appears once your agency has access to it, and it then holds the Chat, Advanced file analysis, and Cowork switches. A choice other than **Separate settings** overrides those switches, unless a level above has locked one. If you choose **Off**, keep Code turned on, or Claude Desktop has nothing to open. Under **Separate settings**, if Chat, Cowork, and Code are all turned off, Claude Desktop keeps Cowork on.

3030

from line 37

3737| **Session idle timeout** | How long a member can stay inactive before being signed out, from 15 to 5,760 minutes (96 hours). Organizations and groups can only set a shorter timeout than the tenant. | 1,440 minutes (24 hours) | All products |

3838| **Maximum session length** | The longest a member can stay signed in, even while active, before they have to sign in again, from 60 to 525,600 minutes (365 days). Each level can set or shorten the maximum but not lengthen it past what the level above allows. | No maximum | All products |

3939| [**Allowed network hosts**](#allowed-network-hosts) | A list of hostnames that tools in Claude Desktop may reach, for example to install packages or fetch web pages. | **Claude connection only** | Claude Desktop |

40| **IPv6 in the sandbox** | Lets tools in the sandbox [reach IPv6-only hosts](/docs/third-party/claude-desktop/configuration#coworkvmipv6enabled) through the computer's own IPv6 connection. **Allowed network hosts** still applies. | Off | Claude Desktop 1.52386.0 or later on macOS and Windows |

40| **IPv6 in the sandbox** | Lets tools in the sandbox [reach IPv6-only hosts](/docs/third-party/claude-desktop/configuration.md#coworkvmipv6enabled) through the computer's own IPv6 connection. **Allowed network hosts** still applies. | Off | Claude Desktop 1.52386.0 or later on macOS and Windows |

42| **Block reads outside workspace folders** | Stops Claude's file tools in Code sessions in Claude Desktop from reading files outside the session's project folder and any folders listed in **Allowed workspace folders**. Its effect on the shell commands Claude runs [differs by operating system](/docs/third-party/claude-desktop/code#applied-as-managed-policy). | Off | Claude Desktop 1.46388.1 or later |

42| **Block reads outside workspace folders** | Stops Claude's file tools in Code sessions in Claude Desktop from reading files outside the session's project folder and any folders listed in **Allowed workspace folders**. Its effect on the shell commands Claude runs [differs by operating system](/docs/third-party/claude-desktop/code.md#applied-as-managed-policy). | Off | Claude Desktop 1.46388.1 or later |

4444| **Accept all edits**, on the **Microsoft 365 features** card | Lets members switch to **Accept all edits**, where Claude makes most edits to the open file without asking. Turning it off also turns off **Skip all permissions**. | On | Claude for Microsoft 365 |

4545| **File access rules (Microsoft 365)** | Rules that block Claude on files with chosen Microsoft sensitivity labels, or block attaching them. A rule can **Block** matching files or **Allow only matching files**. If the add-in cannot read a file's label, the file counts as blocked for every feature that has a rule covering it. | None | Claude for Microsoft 365 |

4646| **Request headers (Claude for Microsoft 365)** | Extra headers Claude for Microsoft 365 sends with each request to Claude. Each member's add-in receives them. Headers are hidden after you save them. | None | Claude for Microsoft 365 |

4747

48**Maximum session length** always counts from when the member originally signed in, so a session that is already older than the new maximum ends when it [picks up the change](/docs/government/config/overview#when-changes-take-effect) and the member is prompted to sign in again. Your identity provider decides whether that sign-in asks the member to authenticate again or passes them straight through.

48**Maximum session length** always counts from when the member originally signed in, so a session that is already older than the new maximum ends when it [picks up the change](/docs/government/config/overview.md#when-changes-take-effect) and the member is prompted to sign in again. Your identity provider decides whether that sign-in asks the member to authenticate again or passes them straight through.

4949

5050### Allowed network hosts

5151

52The list covers [web fetch and shell commands](/docs/third-party/claude-desktop/configuration#coworkegressallowedhosts) in Chat and Cowork, and the [sandboxed shell commands](/docs/government/security/security-and-data-handling#code-in-claude-desktop) of Code sessions on macOS and Linux. Web search, connectors, and the app's own connections do not use this list.

52The list covers [web fetch and shell commands](/docs/third-party/claude-desktop/configuration.md#coworkegressallowedhosts) in Chat and Cowork, and the [sandboxed shell commands](/docs/government/security/security-and-data-handling.md#code-in-claude-desktop) of Code sessions on macOS and Linux. Web search, connectors, and the app's own connections do not use this list.

5353

5454Entries are hostnames or wildcard patterns such as `*.example.com`, and match by name, not by the address a name resolves to.

5555

5656### Allowed workspace folders

5757

58Check **Block all workspace folders** to allow none, in which case Claude can still work in Chat and Cowork in folders it creates inside its own sandbox. Subfolders of a listed folder are included. The setting does not stop the shell commands Claude runs in a Code session from reading files elsewhere on the device, and [Code in Claude Desktop](/docs/government/security/security-and-data-handling#code-in-claude-desktop) describes what confines those commands on each operating system.

58Check **Block all workspace folders** to allow none, in which case Claude can still work in Chat and Cowork in folders it creates inside its own sandbox. Subfolders of a listed folder are included. The setting does not stop the shell commands Claude runs in a Code session from reading files elsewhere on the device, and [Code in Claude Desktop](/docs/government/security/security-and-data-handling.md#code-in-claude-desktop) describes what confines those commands on each operating system.

5959

6060* **Windows and Mac**: a list with only Windows entries leaves Mac users with no allowed folder, so include a Mac path as well, or one that starts with `~`, which stands for each member's home folder on both Windows and Mac.

61* **Synced folders**: on Windows, `~/Documents` refers to the local Documents folder in the user profile, not one redirected to OneDrive. For that one, use [a variable](/docs/third-party/claude-desktop/configuration#allowedworkspacefolders) such as `%OneDriveCommercial%` or `%OneDrive%`. For Code sessions and other work that creates many files, consider listing a local folder that is not synced, such as `~/ClaudeWork`.

61* **Synced folders**: on Windows, `~/Documents` refers to the local Documents folder in the user profile, not one redirected to OneDrive. For that one, use [a variable](/docs/third-party/claude-desktop/configuration.md#allowedworkspacefolders) such as `%OneDriveCommercial%` or `%OneDrive%`. For Code sessions and other work that creates many files, consider listing a local folder that is not synced, such as `~/ClaudeWork`.

6262

6363## Claude Code

6464

65Claude for Government delivers these settings to the command-line tool after a member signs in, and in Claude Desktop 2.9939.2 or later they can also reach Code sessions. While Claude Code is in [early access](/docs/government/deploy-claude-code/configure), the section appears once your agency has access.

65Claude for Government delivers these settings to the command-line tool after a member signs in, and in Claude Desktop 2.9939.2 or later they can also reach Code sessions. While Claude Code is in [early access](/docs/government/deploy-claude-code/configure.md), the section appears once your agency has access.

6666

6868| - | - | - | - |

from line 74

77| **Shell command sandbox** | Lets you turn off [Claude Code's sandbox](/docs/government/security/security-and-data-handling#code-in-claude-desktop) for workspaces where it cannot start, such as containers. | **Claude Code default**, which leaves that to Claude Code's own settings | Claude Code |

77| **Shell command sandbox** | Lets you turn off [Claude Code's sandbox](/docs/government/security/security-and-data-handling.md#code-in-claude-desktop) for workspaces where it cannot start, such as containers. | **Claude Code default**, which leaves that to Claude Code's own settings | Claude Code |

7878

7979Two switches under [Integrations](#integrations) narrow **Any source**: while **Let members add plugin marketplaces** is off, members install only from the **Approved plugin sources** list, and while **Let members add their own plugins** is off, they cannot add a source of their own from a file or folder on their machine.

8080

from line 97

9898| - | - | - | - |

100| **Show the Claude for Government Web import banner** | Shows a banner on Claude Desktop's home screen inviting members to [import their conversations and projects from Claude for Government Web](/docs/government/desktop/import). Members see the banner only in organizations where Anthropic has enabled the import. | Off | Claude Desktop 2.9939.2 or later |

100| **Show the Claude for Government Web import banner** | Shows a banner on Claude Desktop's home screen inviting members to [import their conversations and projects from Claude for Government Web](/docs/government/desktop/import.md). Members see the banner only in organizations where Anthropic has enabled the import. | Off | Claude Desktop 2.9939.2 or later |

101101

102102The system-use notification shown at sign-in is separate from the **Claude Desktop banner**. It is fixed text and cannot be edited.

103103

from line 107

107107

109109| - | - | - | - |

110| **Web search** | Lets Claude search the web. Turning it on asks you to acknowledge a short description of [how search works](/docs/government/security/security-and-data-handling#web-search-and-web-fetch). | Off | Claude Desktop, Claude Code |

110| **Web search** | Lets Claude search the web. Turning it on asks you to acknowledge a short description of [how search works](/docs/government/security/security-and-data-handling.md#web-search-and-web-fetch). | Off | Claude Desktop, Claude Code |

111111| **Require approval for each search** | Asks the member to approve every search before it runs. When this is off, each member chooses whether to approve each search or allow searches automatically. | On | Claude Desktop, Claude Code |

112| **Microsoft 365** | The Microsoft 365 connector, which is separate from the Claude for Microsoft 365 add-in, lets members reach [your agency's Microsoft 365 content](/docs/government/connectors/microsoft-365), including SharePoint, OneDrive, Outlook, and Teams, from Claude Desktop. Each member signs in with their own Microsoft account. | Off until you enter a **Tenant ID** and **Client ID** | Claude Desktop |

112| **Microsoft 365** | The Microsoft 365 connector, which is separate from the Claude for Microsoft 365 add-in, lets members reach [your agency's Microsoft 365 content](/docs/government/connectors/microsoft-365.md), including SharePoint, OneDrive, Outlook, and Teams, from Claude Desktop. Each member signs in with their own Microsoft account. | Off until you enter a **Tenant ID** and **Client ID** | Claude Desktop |

114114| **Member-added connectors**, on the **Connectors** card | Which other connectors members can use in Claude Code, beyond web search and the ones you add: **None**, **Only these**, or **Any connector**. | **None** | Claude Code, Claude Desktop 2.2553.0 or later |

115115| **Blocked connectors**, under **Any connector** | Connectors that Claude Code does not connect. Entries by server URL also block plugins' servers in Claude Desktop. An entry by **Server name** matches [the name a connector is given](https://code.claude.com/docs/en/managed-mcp#how-servername-entries-match), not the server it reaches. | None | Claude Code, Claude Desktop 2.16120.0 or later |

117117| **Let members add plugin marketplaces** | Lets members add plugin marketplaces and install plugins from them. While it is off, it also narrows [**Plugin sources**](#plugin-sources) in Claude Code. Marketplaces that members added earlier are hidden while it is off, which needs Claude Desktop 2.16120.0 or later. | Off | Claude Desktop, Claude Code |

118118| **Let members add their own plugins** | Lets members upload plugin files or have Claude create a plugin for them. While it is off, it also narrows [**Plugin sources**](#plugin-sources) in Claude Code. Plugins that members uploaded or created earlier stay installed. | Off | Claude Desktop, Claude Code |

119119| **Let members add their own connectors** | Lets members add connectors of their own in Claude Desktop, as local MCP servers under **Settings**, then **Developer**. While the switch is off, Claude Desktop ignores connectors that members already added under **Developer**. | Off | Claude Desktop |

120| **Let members create skills** | Lets members [create or upload skills](/docs/third-party/claude-desktop/configuration#skillcreationenabled) of their own. Skills that members already made keep working. | On | Claude Desktop, Claude for Microsoft 365 |

120| **Let members create skills** | Lets members [create or upload skills](/docs/third-party/claude-desktop/configuration.md#skillcreationenabled) of their own. Skills that members already made keep working. | On | Claude Desktop, Claude for Microsoft 365 |

122122| **Require approval for each fetch** | Asks the member to approve every page fetch before it runs. When this is off, fetches in Chat and Cowork run without asking, and Code sessions follow [Claude Code's usual permission rules](https://code.claude.com/docs/en/permissions). | Off | Claude Desktop, Claude Code |

124| **Require approval for each command** | In Claude Desktop, asks the member to approve every shell command before it runs. When this is off, commands [can run without asking](/docs/government/security/security-and-data-handling#approvals-and-auto-mode). | Off | Claude Desktop, Claude Code |

125| **Terminal panel tools** | Lets Claude run commands in the Code tab's Terminal panel in Claude Desktop. These commands [run as the user outside of Claude's sandbox](/docs/government/security/security-and-data-handling#code-in-claude-desktop). Turning off **Shell commands** turns these tools off as well. | On | Claude Desktop |

124| **Require approval for each command** | In Claude Desktop, asks the member to approve every shell command before it runs. When this is off, commands [can run without asking](/docs/government/security/security-and-data-handling.md#approvals-and-auto-mode). | Off | Claude Desktop, Claude Code |

125| **Terminal panel tools** | Lets Claude run commands in the Code tab's Terminal panel in Claude Desktop. These commands [run as the user outside of Claude's sandbox](/docs/government/security/security-and-data-handling.md#code-in-claude-desktop). Turning off **Shell commands** turns these tools off as well. | On | Claude Desktop |

126126| **Bypass-permissions mode** | Whether members can use the mode that skips permission prompts: bypass-permissions mode in Claude Code, **Skip all permissions** in Claude for Microsoft 365. | **Blocked** | Claude Code, Claude for Microsoft 365 |

127| **Auto mode** | Whether members can switch to [Auto mode](https://code.claude.com/docs/en/permission-modes). [Approvals and Auto mode](/docs/government/security/security-and-data-handling#approvals-and-auto-mode) says which sessions start in it. | **Blocked** | Claude Code, Claude Desktop |

127| **Auto mode** | Whether members can switch to [Auto mode](https://code.claude.com/docs/en/permission-modes). [Approvals and Auto mode](/docs/government/security/security-and-data-handling.md#approvals-and-auto-mode) says which sessions start in it. | **Blocked** | Claude Code, Claude Desktop |

128128

129129* **Member-added connectors**: in Claude Desktop it also governs connectors delivered inside plugins. A plugin's connector can connect only under **Any connector** or when listed under **Only these**.

130130* **Member-added connectors**, **Bypass-permissions mode**, and **Auto mode**: these take effect once your agency has the [**Claude Code**](#claude-code) section. In Claude for Microsoft 365, **Bypass-permissions mode** instead takes effect once your agency has the [**Microsoft 365 features**](#microsoft-365-features) card.

from line 137

137137| - | - | - | - |

138138| [**Telemetry endpoint**](#telemetry-endpoint) | The base address of your [OpenTelemetry](https://opentelemetry.io/) collector, such as `https://otel-collector.example.gov:4318`. Each product adds its own paths and sends its telemetry directly from members' devices, so the collector must be reachable from their networks. | Empty, which turns telemetry off | All products |

139139| **Telemetry headers** | Headers each product sends with every telemetry request, such as an Authorization header carrying your collector's token. Each member's app receives these headers and sends its telemetry directly, so use a credential that can only send data to your collector. | None | All products |

140| **Telemetry content capture** | [Content](/docs/third-party/claude-desktop/telemetry#content-capture) each product adds to the telemetry it sends to your collector: **Prompts**, **Claude's responses**, **Tool inputs**, **Tool results**, and **Full requests and responses**. Captured content goes only to your collector and is never sent to Anthropic. | No content captured | All products |

141| **Application event level (Claude Desktop)** | How much of [Claude Desktop's own event log](/docs/third-party/claude-desktop/configuration#otlpdesktoploglevel) is sent to your collector, in addition to usage telemetry: **Off**, **Errors only**, **Warnings and errors**, **Informational**, or **Debug**. | **Errors only** | Claude Desktop |

140| **Telemetry content capture** | [Content](/docs/third-party/claude-desktop/telemetry.md#content-capture) each product adds to the telemetry it sends to your collector: **Prompts**, **Claude's responses**, **Tool inputs**, **Tool results**, and **Full requests and responses**. Captured content goes only to your collector and is never sent to Anthropic. | No content captured | All products |

141| **Application event level (Claude Desktop)** | How much of [Claude Desktop's own event log](/docs/third-party/claude-desktop/configuration.md#otlpdesktoploglevel) is sent to your collector, in addition to usage telemetry: **Off**, **Errors only**, **Warnings and errors**, **Informational**, or **Debug**. | **Errors only** | Claude Desktop |

142142| **Telemetry resource attributes** | Labels added to every telemetry record each product sends, such as your agency or environment name, so your collector can tell where each record comes from. | Not set | All products |

143| **Telemetry traces** (beta) | Adds [traces](/docs/third-party/claude-desktop/telemetry#traces-beta), so that the events of one request can be followed together. Traces carry message and tool content only for the categories selected in **Telemetry content capture**. | Off | All products; Claude Desktop 1.22209.0 or later |

144| **Block automatic updates** | Stops Claude Desktop from downloading and installing updates automatically. Turn this on only if your organization distributes Claude Desktop updates itself. For devices where no member is signed in, and for Linux, see [Automatic updates](/docs/government/deploy-desktop/configure#automatic-updates). | Off | Claude Desktop on macOS and Windows |

145| **Restart deadline for updates** | How long a member can put off restarting Claude Desktop to install a downloaded update, from 1 to 72 hours. | [Claude Desktop's default](/docs/third-party/claude-desktop/configuration#autoupdaterenforcementhours) | Claude Desktop |

146| **Restart deadline for configuration changes** | How long a member can put off restarting Claude Desktop after the app detects a configuration change, from 0 to 336 hours (14 days). | [Claude Desktop's default](/docs/third-party/claude-desktop/configuration#relaunchenforcementhours) | Claude Desktop |

143| **Telemetry traces** (beta) | Adds [traces](/docs/third-party/claude-desktop/telemetry.md#traces-beta), so that the events of one request can be followed together. Traces carry message and tool content only for the categories selected in **Telemetry content capture**. | Off | All products; Claude Desktop 1.22209.0 or later |

144| **Block automatic updates** | Stops Claude Desktop from downloading and installing updates automatically. Turn this on only if your organization distributes Claude Desktop updates itself. For devices where no member is signed in, and for Linux, see [Automatic updates](/docs/government/deploy-desktop/configure.md#automatic-updates). | Off | Claude Desktop on macOS and Windows |

147147

148148* **Telemetry headers**: the headers you enter replace all of the saved ones when you save, so enter every header again when you add or change one.

149149* **Telemetry content capture**: **Tool results** adds tool output only while **Telemetry traces** is on. **Full requests and responses** can carry tool output with traces on or off.

from line 152

152152

153153### Telemetry endpoint

154154

155Once 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 any set on the device itself. Claude Desktop keeps working when the collector refuses requests or cannot be reached, and members see no error. For what the collector must accept, and how to confirm that telemetry is arriving, see [Collector endpoint and headers](/docs/third-party/claude-desktop/telemetry#collector-endpoint-and-headers). For Claude for Microsoft 365, the collector must also accept [cross-origin requests from your Claude for Government host](/docs/government/deploy-microsoft-365/configure#before-you-begin).

155Once 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 any set on the device itself. Claude Desktop keeps working when the collector refuses requests or cannot be reached, and members see no error. For what the collector must accept, and how to confirm that telemetry is arriving, see [Collector endpoint and headers](/docs/third-party/claude-desktop/telemetry.md#collector-endpoint-and-headers). For Claude for Microsoft 365, the collector must also accept [cross-origin requests from your Claude for Government host](/docs/government/deploy-microsoft-365/configure.md#before-you-begin).

156156

157Each record [identifies the member](/docs/third-party/claude-desktop/telemetry#user-attribution). See what [Claude Desktop](/docs/cowork/monitoring#events), [Claude for Microsoft 365](/docs/office-agents/opentelemetry#what-the-collector-receives), and [Claude Code](https://code.claude.com/docs/en/monitoring-usage) send.

157Each record [identifies the member](/docs/third-party/claude-desktop/telemetry.md#user-attribution). See what [Claude Desktop](/docs/cowork/monitoring.md#events), [Claude for Microsoft 365](/docs/office-agents/opentelemetry.md#what-the-collector-receives), and [Claude Code](https://code.claude.com/docs/en/monitoring-usage) send.

158158

159159## Admin Console

160160

from line 162

162162

164164| - | - | - | - |

165| **Let organizations manage their own seat tiers** | Lets organization owners create and edit self-managed seat tiers on the [Tiers](/docs/government/org-admin/seat-tiers) page, in addition to the Anthropic-managed ones. When it is off, the **Reset usage limits** action on the [Users](/docs/government/org-admin/users) page is also unavailable. | On | Admin Console |

166| **Compliance API** | Controls whether the [Compliance API](/docs/government/org-admin/compliance-api) is available. When this is off, requests are refused and existing keys stay listed so you can revoke them. | On | Admin Console |

165| **Let organizations manage their own seat tiers** | Lets organization owners create and edit self-managed seat tiers on the [Tiers](/docs/government/org-admin/seat-tiers.md) page, in addition to the Anthropic-managed ones. When it is off, the **Reset usage limits** action on the [Users](/docs/government/org-admin/users.md) page is also unavailable. | On | Admin Console |

166| **Compliance API** | Controls whether the [Compliance API](/docs/government/org-admin/compliance-api.md) is available. When this is off, requests are refused and existing keys stay listed so you can revoke them. | On | Admin Console |

168168

This page’s history 36 edits

21 Oct 2026 +32 −32 · this one
21 Oct 2026 +137 −242
20 Oct 2026 +39 −39
20 Oct 2026 +8 −6
19 Oct 2026 +5 −1
15 Oct 2026 +12 −7

The page’s own history →

Where it came from

The captureclaude-docs
Upstream pageclaude.com

Around it

Every changethe ledger
That day21 Oct 2026