Manage Claude Science on devices changedclaude-science/manage-on-devices
Nearest release: v2.1.301, published 5 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:17 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 20:37 UTC.
Upstream edited
Recorded here
Lines+27added
Lines−7removed
From line
2
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
## Macs where Claude Science opens in its own window
The whole hunk
from line 2, old and new numbered
/
from line 2
22
33> Claude Science is a desktop application that stores member content locally.
44
5Claude Science is a desktop application that stores member content locally. This page covers what IT and endpoint teams need to know: where the app writes data, how to deploy configuration with device management, what telemetry is sent, and what members see when Anthropic requires an update.
5Claude Science is a desktop application that stores member content locally. This page covers what IT and endpoint teams need to know: where the app writes data, how to deploy configuration with device management, what changes when Claude Science opens in its own window on a Mac, what telemetry is sent, and what members see when Anthropic requires an update.
66
77## Where the app stores data
88
9The app writes to two locations on each member's computer:
9The app writes to these locations on each member's computer:
1010
1111Configuration: config.toml in the app's default data folder (`~/.claude-science/config.toml` on macOS and Linux, `%USERPROFILE%\.claude-science\config.toml` on Windows) holds all app settings. Every key is optional; the app starts with no file present. This is the file to deploy through device management.\
1212Data: the app's data directory holds conversations, generated artifacts, delegation configurations, and workspace files in a per-organization subfolder (orgs/`<organization-id>`/), stored as a local database plus files.
from line 13
1313
1414Authentication tokens and the shared package environment live under the default data folder (`~/.claude-science/`, or `%USERPROFILE%\.claude-science\` on Windows) regardless of the data directory, so endpoint backup or wipe policies that target the data directory don't affect sign-in state.
1515
16On Windows, the program itself installs per user to `%LOCALAPPDATA%\Programs\ClaudeScience` and registers under the signed-in user's **Settings** > **Apps** > **Installed apps** rather than machine-wide. The app also writes launch logs and state to `%LOCALAPPDATA%\ClaudeScience` and keeps a sandbox state folder under `%LOCALAPPDATA%`, and it unpacks components it runs, such as the app window engine and the sandbox launcher, under the data folder, so allow-listing by path needs both the program folder and the data folder. Uninstalling removes the program and sandbox state; `claude-science uninstall --purge` also removes the data and state folders.
16On Windows and macOS, the program is in these places:
1717
18* **Windows**: the program itself installs per user to `%LOCALAPPDATA%\Programs\ClaudeScience` and registers under the signed-in user's **Settings** > **Apps** > **Installed apps** rather than machine-wide. The app also writes launch logs and state to `%LOCALAPPDATA%\ClaudeScience` and keeps a sandbox state folder under `%LOCALAPPDATA%`, and it unpacks components it runs, such as the app window engine and the sandbox launcher, under the data folder, so allow-listing by path needs both the program folder and the data folder. Uninstalling removes the program and sandbox state; `claude-science uninstall --purge` also removes the data and state folders.
19* **macOS**: the app is **Claude Science** in the **Applications** folder, or in the **Applications** folder inside the member's home folder. When Claude Science opens in a browser tab, it runs its program from a copy at `~/.claude-science/bin/claude-science`. When it opens in its own window, it runs the program from inside the app. In its own window, Claude Science also keeps window settings, logs, and the window's page storage, which includes unsent message drafts, in `~/Library/Application Support/Claude Science` (see [Macs where Claude Science opens in its own window](#macs-where-claude-science-opens-in-its-own-window)).
20
1821Your endpoint tooling governs these folders the same way it governs any other local application data. Anthropic doesn't host a copy of these folders, so Custom Data Retention and Org Data Export don't reach them. [How Claude Science works with your data](/docs/claude-science/how-claude-science-works-with-your-data) covers what Anthropic does receive from the app, including the session transcripts available to Enterprise organizations with the Compliance API enabled.
1922
2023## Deploy configuration with device management
from line 26
2326
2427| Key | Effect |
2528| - | - |
26| disable\_telemetry = true | Stops the app from sending product-usage telemetry and error reports to Anthropic. |
27| data\_dir = "`<path>`" | Moves conversations, artifacts, and workspaces to a managed location (for example, a volume your backup tooling covers). |
28| \[update] auto\_update = false | Prevents the app from updating itself; pair with your own distribution channel. |
29| \[sandbox.network] enabled = false | Blocks network access from the app's local code-execution sandbox. The similarly named \[sandbox] network\_isolated key does not control this. |
29| `disable_telemetry = true` | Stops the app from sending product-usage telemetry and error reports to Anthropic. |
30| `data_dir = "<path>"` | Moves conversations, artifacts, and workspaces to a managed location (for example, a volume your backup tooling covers). |
31| `auto_update = false` under `[update]` | Turns off the background check for updates on Windows, on Linux, and on a Mac where Claude Science opens in a browser tab; pair with your own distribution channel. A member can still check for and install an update from inside Claude Science. |
32| `enabled = false` under `[sandbox.network]` | Blocks network access from the app's local code-execution sandbox. The similarly named `network_isolated` key under `[sandbox]` doesn't control this. |
3033
3134The [configuration file reference](/docs/claude-science/configuration-file-reference) documents the network-related keys and their defaults, and [Use Claude Science on a corporate network](/docs/claude-science/corporate-networks) covers the proxy, TLS-inspection, and mirror settings.
35
36## Macs where Claude Science opens in its own window
37
38On a Mac, Claude Science opens either in a browser tab or in its own window. When a member installs an update from inside Claude Science, the update can switch Claude Science to its own window. It switches only if the member's account owns the installed app and can replace it, so a copy that device management installed as root never switches. When the account that owns the app switches it, Claude Science opens in its own window for every account that opens that copy.
39
40Claude Science in its own window has the bundle identifier `com.anthropic.claudescience`, so macOS treats it as a different app from Claude Science in a browser tab. Add an entry for `com.anthropic.claudescience` to any Privacy Preferences Policy Control (PPPC) profile that grants Claude Science access. An allow-list rule on the Apple Team ID `Q6L2SF6YDW` covers both apps, and also the app's helper programs, which are signed with identifiers such as `com.anthropic.claudescience.helper`.
41
42Claude Science in a browser tab and in its own window get updates in different ways:
43
44| What differs | In a browser tab | In its own window |
45| - | - | - |
46| Updates | Checks in the background and shows **Update available** | Downloads updates by itself and installs them when the app quits |
47| Connections for updates | Use the app's proxy settings | Use the proxy in macOS network settings and the certificates that macOS trusts (see [Proxy and certificates for updates in the Mac app window](/docs/claude-science/corporate-networks#proxy-and-certificates-for-updates-in-the-mac-app-window)) |
48
49If the member's account can't write to the app or its folder, Claude Science in its own window doesn't check for updates in the background. The member can still choose **Claude Science > Check for App Updates…**, and macOS then asks for an administrator's password to install the update.
50
51Setting `auto_update = false` under `[update]` doesn't stop Claude Science from switching to its own window, because a member can still install an update from inside Claude Science.
3252
3353## Telemetry
3454
No line in this hunk matches that.