Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
One capture · claude-docs

One read of Claude Documentation

2 pages moved out of 233 read.

claude-docs-20260911T030708Z

Pages moved 2 significant first
Pages read 233 in this capture
Captured 03:07 UTC
Corpus hash cf270e6b9dc2 corpus-hash

What this read moved

1–2 of 2

third-party/claude-desktop/feature-matrix Changed · +47 / -42 lines

from line 6
66 
77## Key differences
88 
9**Configuration.** Claude Enterprise uses a web-based admin console. Claude Desktop on 3P is configured via [MDM](/docs/third-party/claude-desktop/mdm) (Jamf, Intune, Group Policy) or a [bootstrap server](/docs/third-party/claude-desktop/bootstrap); organizations in the admin console beta can instead manage it from **Organization settings** on claude.ai.
9**Configuration.** Both are administered from the web-based [admin console](/docs/third-party/claude-desktop/admin-console) in **Organization settings** on claude.ai. Claude Desktop on 3P can also be configured through [MDM](/docs/third-party/claude-desktop/mdm) (Jamf, Intune, Group Policy) or a [bootstrap server](/docs/third-party/claude-desktop/bootstrap).
1010 
1111**Telemetry.** Claude Desktop on 3P sends usage and debugging metrics only, and these can be fully disabled via managed configuration. Claude Enterprise does not offer telemetry toggles. See [Telemetry and egress](/docs/third-party/claude-desktop/telemetry).
1212 
from line 18
1818 
1919## User features
2020 
21| Feature | Claude Enterprise | Claude Desktop on 3P |
22| --------------------------------------------------- | :---------------: | :------------------: |
23| Chat | ✓ | ✓ (admin opt-in) |
24| Cowork | ✓ | ✓ |
25| Code | ✓ | ✓ |
26| Auto mode (Code) | ✓ | ✓ (admin opt-in) |
27| Automatically approve / Skip all approvals (Cowork) | — ¶ | ✓ (admin opt-in) |
28| Projects || ✓ |
29| Code execution for analysis | ✓ | ✓ |
30| Web search | ✓ | ✓ § |
31| File access, upload, and export | ✓ | |
32| Local MCP | ✓ | ✓ |
33| Remote MCP | ✓ | ✓ |
34| Skills, plugins, and hooks | ✓ | ✓ |
35| Artifacts | ✓ | ✓ |
36| Memory | ✓ | ✓ † |
37| Scheduled tasks | ✓ | ✓ |
38| Global languages | ✓ | |
39| Project and plugin sharing | ✓ | |
40| Plugin marketplaces | ✓ | ✓ |
41| Mobile | ✓ | — |
42| claude.ai web-based access | ✓ | |
43| Voice mode | ✓ | — |
44| Claude in Chrome | ✓ | — |
45| Claude Design | ✓ | — |
46| Claude Security | ✓ | — |
47| Claude Tag | ✓ | — |
48| Computer use | | — |
21| Feature | Claude Enterprise | Claude Desktop on 3P |
22| ----------------------------------------------------------------------------------------------------------------------------------- | :---------------: | :------------------: |
23| Chat | ✓ | ✓ |
24| Cowork | ✓ | ✓ |
25| Code | ✓ | ✓ |
26| Auto mode (Code) | ✓ | ✓ |
27| [SSH remote Code sessions](/docs/third-party/claude-desktop/ssh-remote-sessions) || ✓ |
28| Automatically approve / Skip all approvals (Cowork) | — ¶ | ✓ |
29| Projects | ✓ | ✓ |
30| Code execution for analysis | ✓ | ✓ |
31| Web search | ✓ | ✓ § |
32| File access, upload, and export | ✓ | ✓ |
33| Local MCP | ✓ | ✓ |
34| Remote MCP | ✓ | ✓ |
35| [Microsoft 365](/docs/third-party/claude-desktop/connectors-m365) and [GitHub](/docs/third-party/claude-desktop/connectors-github) connectors | ✓ | ✓ |
36| Skills, plugins, and hooks | ✓ | ✓ |
37| Artifacts | ✓ | ✓ |
38| Memory | ✓ | ✓ † |
39| Scheduled tasks | ✓ | |
40| Global languages | ✓ | ✓ |
41| Project and plugin sharing | ✓ | — |
42| Plugin marketplaces | ✓ | |
43| Mobile | ✓ | — |
44| claude.ai web-based access | ✓ | — |
45| Voice mode | ✓ | — |
46| Claude in Chrome | ✓ | — |
47| Claude Design | ✓ | — |
48| Claude Security | | — |
49| Claude Tag | ✓ | — |
50| Computer use | — | — |
4951 
5052§ Amazon Bedrock deployments and gateways that do not forward Anthropic server tools need a web search provider configured first; see [Web search options](/docs/third-party/claude-desktop/web-tools#web-search-options).
5153 
from line 57
5557 
5658## Admin features
5759 
58| Feature | Claude Enterprise | Claude Desktop on 3P |
59| --------------------------------------------- | :----------------: | :------------------: |
60| Endpoint / gateway configuration | — | ✓ |
61| Skills, hooks, and plugins distribution | ✓ | ✓ |
62| MCP server allowlist | ✓ | ✓ |
63| Feature toggles (web search, local MCP, etc.) | ✓ | ✓ |
64| Auto-updates | ✓ | ✓ (configurable) |
65| Per-user spend caps | ✓ (differentiated) | ✓ (blanket only) |
66| Compliance API | ✓ | — ‡ |
67| Analytics API | ✓ | — ‡ |
68| OpenTelemetry export | ✓ | |
69| User management via UI | ✓ | |
70| RBAC | ✓ | via MDM |
60| Feature | Claude Enterprise | Claude Desktop on 3P |
61| --------------------------------------------------------------------------------------------- | :---------------: | :------------------: |
62| Endpoint / gateway configuration | — | ✓ |
63| Skills, hooks, and plugins distribution | ✓ | ✓ |
64| MCP server allowlist | ✓ | ✓ |
65| Feature toggles (web search, local MCP, etc.) | ✓ | ✓ |
66| Auto-updates | ✓ | ✓ |
67| Per-user usage caps | ✓ | ✓ |
68| [Data retention policies](/docs/third-party/claude-desktop/configuration#chatsessionretentiondays) | ✓ | |
69| Compliance API | ✓ | — ‡ |
70| Analytics API | ✓ | — ‡ |
71| OpenTelemetry export | ✓ | |
72| User management via UI | ✓ | ✓ ◊ |
73| RBAC | ✓ | ✓ ◊ |
7174 
7275‡ Many of these capabilities can be achieved via OpenTelemetry export to your own collector. See [Monitoring](/docs/cowork/monitoring).
76 
77◊ With the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console), administrators add users and groups, connect single sign-on and SCIM, assign administrator roles, and set per-group permission policies from **Organization settings** on claude.ai. Deployments configured through MDM or a bootstrap server manage access through those channels.
7378 

third-party/claude-desktop/overview Changed · +4 / -4 lines

from line 15
1515 
1616How far a deployment is separated from Anthropic depends on the provider you choose. On Google Cloud's Agent Platform and Amazon Bedrock, the cloud provider processes conversation data in the region you select. On Microsoft Foundry, Anthropic operates the Claude models, and residency follows the Foundry deployment type. Review [Data handling by provider](#data-handling-by-provider) and [Data residency and international deployment](#data-residency-and-international-deployment) before choosing a provider.
1717 
18If your organization can use Anthropic's first-party products directly, standard Claude Desktop with [Cowork](/docs/cowork/overview) on a Team or Enterprise plan is simpler to deploy, offers an in-app UI for user management, analytics, and RBAC, and releases new features more quickly than Claude Desktop on 3P. Choose Claude Desktop on 3P when routing inference through Anthropic's API is not an option.
18If your organization can use Anthropic's first-party products directly, standard Claude Desktop with [Cowork](/docs/cowork/overview) on a Team or Enterprise plan is simpler to deploy and releases new features more quickly than Claude Desktop on 3P. Choose Claude Desktop on 3P when routing inference through Anthropic's API is not an option.
1919 
2020## Architecture
2121 
from line 25
2525| ---------------------- | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
2626| Model inference | Anthropic API | Your configured provider endpoint (Google Cloud's Agent Platform, Amazon Bedrock, Microsoft Foundry, or gateway), or the Anthropic API |
2727| Web application | Loaded from claude.ai | Bundled inside the desktop app |
28| User identity | Anthropic account | Local device identity only (Anthropic account when managed from the claude.ai admin console, in beta) |
28| User identity | Anthropic account | Local device identity only (Anthropic account when managed from the claude.ai admin console) |
2929| Conversation storage | Anthropic backend | Local disk on the user's machine |
3030| Code execution sandbox | Local VM | Local VM (identical) |
31| Configuration | Admin console at claude.ai | OS-native configuration (MDM-managed or per-user), or the claude.ai admin console (beta) |
31| Configuration | Admin console at claude.ai | OS-native configuration (MDM-managed or per-user), a bootstrap server, or the claude.ai admin console |
3232 
3333The desktop app detects 3P mode at launch from the configured inference provider. When a provider and its credentials are present, the sign-in screen offers the option to skip Anthropic authentication and start the app using your inference-provider configuration instead.
3434 
from line 37
3737* **Conversation content goes only to your configured endpoint.** The app sends prompts, responses, files, and tool outputs only to your configured inference endpoint and stores them only on the local machine. What happens to that content at the endpoint depends on the provider, as described under [Data handling by provider](#data-handling-by-provider).
3838* **Sandboxed tool execution.** Shell commands run in the hardened Cowork VM; file access is scoped to your allowed folders and web fetches to your egress allowlist.
3939* **Auditable telemetry.** Crash reports and product analytics are scrubbed of conversation and user data before being sent to Anthropic, and can be fully disabled via configuration keys. Independently, you can export session activity to your own OpenTelemetry collector. The export is metadata only by default, with prompt and tool content available as an explicit opt-in.
40* **Centrally managed.** All configuration is delivered via your existing MDM (Jamf, Intune, Workspace ONE, Group Policy) and cannot be overridden by end users when an admin profile is present.
40* **Centrally managed.** Configuration is delivered through your existing MDM (Jamf, Intune, Workspace ONE, Group Policy), a [bootstrap server](/docs/third-party/claude-desktop/bootstrap), or the [admin console](/docs/third-party/claude-desktop/admin-console). End users cannot override a configuration that MDM delivers.
4141 
4242For a detailed treatment of the threat model, sandbox boundaries, and data flows, request access to the [Claude Cowork Desktop Security Architecture Overview](https://trust.anthropic.com/resources?s=2a7bbzo1lyymvdt551q7kl\&name=claude-cowork-desktop-security-architecture-overview) on Anthropic's Trust Center. For architecture, telemetry, and controls information specific to Claude Desktop on 3P, see the [Claude Desktop Security Overview (Third-party platforms)](https://trust.anthropic.com/resources?s=0c8rx4s7mm5ierz8ppetfs\&name=claude-cowork-security-overview-\(third-party-platforms\)) on the Trust Center.
4343