One read of Claude Documentationclaude-docs-20261027T220709Z
7 pages moved out of 280 read.
Pages moved
7
significant first
Pages read
280
in this capture
Captured
22:07 UTC
Corpus hash
b05e754942ca
corpus-hash
What this read moved
1-7 of 7claude-science/changelog Changed · +14 / -0 lines
from line 2
22
33> Release notes for Claude Science, including new features, improvements, and bug fixes by version.
44
5**0.1.71**
6
7October 27, 2026
8
9* If usage credits are turned on at claude.ai while Claude Science is open, it now pauses at your usage limit and asks before it keeps spending them
10* When Claude's servers time out before a reply starts, Claude Science now tries again instead of stopping right away with an error
11* Fixed custom connectors failing to load behind a proxy with "unexpected end of file" when their server sends an empty reply marked as compressed
12* The sandbox now protects `.devcontainer`, `.cursor`, `.codex`, and `.gemini` folders in a folder you've granted. On a Mac, use your own terminal to clone or unpack a project that holds one; on Linux they look empty inside the sandbox, so committing all changes there (for example with `git commit -a`) records their files as deleted
13* Mac and Linux: Claude now installs pip packages into [task environments](https://claude.com/docs/claude-science/tools-and-environments.md#task-environments) only as prebuilt packages (wheels), not from a git repository, web address, or local folder or file. A package with no wheel for your computer and Python version won't install there; if an older version has one, pip may install that instead. For other ways to install a package, see [Tools and environments](https://claude.com/docs/claude-science/tools-and-environments.md#python-package-sources-for-starter-and-task-environments)
14* Linux: as in 0.1.61, Claude Science again runs bubblewrap and socat only from system folders such as `/usr/bin` and `/usr/local/bin`, not from your PATH. With your distribution's bubblewrap (0.8.0 or later) and socat, nothing changes; Ubuntu 22.04 and earlier, Debian 11 and earlier, RHEL and Rocky 8 and 9, and Amazon Linux 2 ship an older bubblewrap or none
15* Linux: if your bubblewrap or socat is your own copy (for example from conda or pixi), [approve it once](https://claude.com/docs/claude-science/run-on-remote-linux-server.md#approve-your-own-copy-of-bubblewrap-or-socat) or ask an administrator to install both. Until then, updating from the app or running the install command again keeps your current version and says what to do
16* Linux: with your own copy, don't update by typing `claude-science update`. It can replace your current version, and 0.1.71 then won't start until your copy is approved (see [Troubleshooting](https://claude.com/docs/claude-science/troubleshooting.md#not-approved))
17* Bug fixes and reliability improvements
18
519**0.1.70**
620
721October 21, 2026
claude-science/get-started Changed · +7 / -8 lines
from line 48
4848
4949**Linux**
5050
51Install the sandbox dependencies, then run the installer. The sandbox needs bubblewrap 0.8.0 or later and socat, and installing them takes administrator (root or `sudo`) access; if you don't have it, ask your system administrator to install them, or see [Run Claude Science without administrator access](https://claude.com/docs/claude-science/run-on-remote-linux-server.md#run-claude-science-without-administrator-access).
51Install the sandbox dependencies, then run the installer. The sandbox needs bubblewrap 0.8.0 or later and socat, and installing them for the whole system takes administrator (root or `sudo`) access. Claude Science runs them from system folders such as `/usr/bin` and `/usr/local/bin` and doesn't search your PATH. If you don't have administrator access, ask your system administrator to install them, or [approve a copy of your own](https://claude.com/docs/claude-science/run-on-remote-linux-server.md#approve-your-own-copy-of-bubblewrap-or-socat), such as one from conda.
5252
5353* Ubuntu or Debian: `sudo apt-get update && sudo apt-get install -y curl bubblewrap socat`
5454* Fedora or RHEL: `sudo dnf install -y curl bubblewrap socat`
5555* Arch: `sudo pacman -S curl bubblewrap socat`
5656
57Ubuntu 24.04's repositories carry a new enough bubblewrap and Ubuntu 22.04's don't; on any distribution, confirm with `bwrap --version` that the installed version is 0.8.0 or later before you start Claude Science.
57Ubuntu 24.04's repositories carry a new enough bubblewrap and Ubuntu 22.04's don't; on any distribution, confirm with `/usr/bin/bwrap --version` that the installed version is 0.8.0 or later before you start Claude Science.
5858
5959```bash theme={null}
6060curl -fsSL https://claude.ai/install-claude-science.sh | bash
from line 171
171171* A Claude Science message on Windows says the app was not installed because the file could not be confirmed: the copy you opened still runs but isn't installed. Download the installer again from [claude.com/product/claude-science](https://claude.com/product/claude-science) and open the new file. If the message persists, the PC could not verify the publisher's signature, so ask your IT team.
172172* The Windows app reports that it couldn't set up the app window engine: the first launch downloads that engine from `downloads.claude.ai`, and this usually means the app couldn't reach it. Check the internet connection, and on a corporate network ask IT to allow that domain (see [Network requirements](https://claude.com/docs/claude-science/network-requirements.md)).
173173* On Linux, the installer stops with `The download service may be unreachable, or not yet available in your region`: the installer couldn't get the latest version from `storage.googleapis.com`. Check the internet connection, and on a corporate network ask IT to allow that domain (see [Network requirements](https://claude.com/docs/claude-science/network-requirements.md#app-connections)). Claude Science is available where Anthropic offers claude.ai. See [Supported countries and regions](https://www.anthropic.com/supported-countries).
174* On Linux, the installer stops with `was NOT installed` and says the copy you already had `was left as it is`: Claude Science was already installed, so the installer first tried to check that the new version starts on this computer. The check didn't succeed, so nothing was replaced. The message and the lines under it say why and, where there is a fix, what to do. If they point to the [configuration file](https://claude.com/docs/claude-science/configuration-file-reference.md), `~/.claude-science/config.toml`, fix what they report in that file, then run the installer again from the Linux tab of [Install](#install). Otherwise, keep using the copy you already had.
174* On Linux, the installer stops with `was NOT installed` and says the copy you already had `was left as it is`: Claude Science was already installed, so the installer first tried to check that the new version starts on this computer. The check didn't succeed, so nothing was replaced. The message and the lines under it say why and, where there is a fix, what to do. If they point to the [configuration file](https://claude.com/docs/claude-science/configuration-file-reference.md), `~/.claude-science/config.toml`, fix what they report in that file, then run the installer again from the Linux tab of [Install](#install). If they give no fix, keep using the copy you already had.
175175* On Linux, the shell reports `command not found` for `claude-science`: `~/.local/bin` isn't on your PATH. Add the PATH line that the installer printed to your shell profile, then open a new terminal.
176* On Linux, `claude-science serve` stops with a `Sandbox unavailable:` message that mentions `bwrap was found on PATH at`, `is not where Claude Science runs it from`, `(PATH is not searched)`, or `is deliberately not used`: version 0.1.61 prints these messages, because it needs bubblewrap and socat installed for the whole system. If you updated to it from inside the app, the "Update available" notice shows "restart aborted" instead of these messages. Version 0.1.62 withdraws that requirement. Run `claude-science update` in a terminal, then start Claude Science again.
177* On Linux, `claude-science serve` stops with `Sandbox unavailable: bwrap not found on PATH`: bubblewrap isn't installed, or isn't on your PATH. Install bubblewrap and socat with the command for your distribution in the Linux tab of [Install](#install).
178* On Linux, `claude-science serve` stops with `Sandbox unavailable: bwrap too old`: the installed bubblewrap is older than 0.8.0. Check the version with `bwrap --version`, then upgrade bubblewrap. Ubuntu 24.04's repositories carry a new enough version and Ubuntu 22.04's don't.
176* On Linux, `claude-science serve` stops with a `Sandbox unavailable:` message that says `bwrap not found in` a list of folders, or `bwrap was found on PATH at` a path: bubblewrap isn't installed in a system folder. In version 0.1.71 and later, Claude Science runs bubblewrap and socat only from the system folders that the message lists or from a copy you've approved. It doesn't search your PATH. Install both with the command for your distribution in the Linux tab of [Install](#install). Without administrator access, [approve a copy of your own](https://claude.com/docs/claude-science/run-on-remote-linux-server.md#approve-your-own-copy-of-bubblewrap-or-socat) with the `claude-science sandbox approve` command that the message prints. If this happened after you typed `claude-science update`, you can [go back to version 0.1.70](https://claude.com/docs/claude-science/troubleshooting.md#not-approved).
177* On Linux, `claude-science serve` stops with a `Sandbox unavailable:` message such as `/usr/bin/bwrap is too old`: the bubblewrap it names is older than 0.8.0. Check its version in a terminal with that path, for example `/usr/bin/bwrap --version`, then upgrade bubblewrap. Ubuntu 24.04's repositories carry a new enough version and Ubuntu 22.04's don't. If you can't upgrade it, [approve a newer copy of your own](https://claude.com/docs/claude-science/run-on-remote-linux-server.md#approve-your-own-copy-of-bubblewrap-or-socat).
179178* On Linux, `claude-science serve` stops with `Sandbox unavailable: bwrap cannot create unprivileged user namespaces`: the kernel or an AppArmor profile blocks the sandbox from creating user namespaces. The rest of the message names the settings to check on Ubuntu, Debian, and other distributions, and changing them takes administrator (`sudo`) access.
180* On Linux, an error says `socat is required for Linux sandbox networking but was not found in PATH`: socat isn't installed, or isn't on your PATH. Install socat with the command for your distribution in the Linux tab of [Install](#install).
181* On Linux, a line starting `[sandbox]` says `no usable socat command was found on this computer`, in the terminal where `claude-science serve` runs or in the output of `claude-science logs`: Claude Science started, but the sandbox has no network access. The sandbox runs socat only from system folders such as `/usr/bin`, and doesn't use a copy from conda, Homebrew, or a folder in your home directory. Code that Claude runs can't reach the internet, and environment setup can fail with `Package downloads are being blocked by network policy` even when your network blocks nothing. Install socat with the command for your distribution in the Linux tab of [Install](#install), or if you don't have administrator access, ask your system administrator to install it for the whole system.
179* On Linux, `claude-science serve` stops with `Sandbox unavailable: socat is required for Linux sandbox networking`: socat isn't installed in a system folder, and Claude Science doesn't search your PATH for it. Install socat with the command for your distribution in the Linux tab of [Install](#install). Without administrator access, you can [approve a copy of your own](https://claude.com/docs/claude-science/run-on-remote-linux-server.md#approve-your-own-copy-of-bubblewrap-or-socat) so that Claude Science starts. Until socat is in a system folder, environment setup fails with `Package downloads are being blocked by network policy`, because code that Claude runs has no network access. If this happened after you typed `claude-science update`, you can [go back to version 0.1.70](https://claude.com/docs/claude-science/troubleshooting.md#not-approved).
180* On Linux, a line starting `[sandbox]` says `sandboxed commands run without network access`, in the terminal where `claude-science serve` runs or in the output of `claude-science logs`: Claude Science started, but the sandbox has no network access. The sandbox runs socat only from system folders such as `/usr/bin`, and doesn't use a copy from conda, pixi, a cluster module, or your home folder, including a copy that you approved. Code that Claude runs can't reach the internet, and environment setup fails with `Package downloads are being blocked by network policy` even when your network blocks nothing. Install socat with the command for your distribution in the Linux tab of [Install](#install), or if you don't have administrator access, ask your system administrator to install it for the whole system.
182181* Projects from another computer don't appear: by design, Claude Science keeps your work on the computer where it's installed, so each computer starts with its own projects. Your earlier projects are still on the other computer. See [Use Claude Science on more than one computer](https://claude.com/docs/claude-science/multiple-computers.md).
183182* Projects you created under another sign-in on this computer don't appear automatically, for example, after you move from a personal plan to your organization's Team plan: your earlier projects are still in that sign-in's folder. Select the **Review** button on the banner at the top of the home screen, or select **Review** next to **Access previously saved Claude Science work on this computer** under **Settings** > **General** > **Account**, to access them. On Team and Enterprise plans, if there's no banner and the setting is grayed out, your admin controls it. See [Access work from another sign-in on your computer](https://claude.com/docs/claude-science/multiple-computers.md#access-work-from-another-sign-in-on-your-computer).
184183* Sign-in stops at claude.ai: your account is on the Free plan (upgrade required), the redirect couldn't return (in a browser tab or in the Windows app, use **Paste code instead**), or your Team or Enterprise organization hasn't [enabled Claude Science](https://claude.com/docs/claude-science/enable-claude-science.md) yet.
claude-science/run-on-remote-linux-server Changed · +29 / -10 lines
### Approve your own copy of bubblewrap or socat
from line 22
2222
2323> [!NOTE]
2424>
25> The sandbox requires bubblewrap 0.8.0 or later; check with `bwrap --version`. Ubuntu 24.04 ships a new enough version, and Ubuntu 22.04 doesn't. If Claude Science can't set up the sandbox, it refuses to start rather than run code unsandboxed.
25> The sandbox requires bubblewrap 0.8.0 or later; check with `/usr/bin/bwrap --version`. Ubuntu 24.04 ships a new enough version, and Ubuntu 22.04 doesn't. If Claude Science can't set up the sandbox, it refuses to start rather than run code unsandboxed.
2626
2727## Run Claude Science without administrator access
2828
2929If you don't have administrator (root or `sudo`) access to a shared server or cluster, choose one of these:
3030
31* **Ask the server's administrator** to set up what the sandbox needs: bubblewrap 0.8.0 or later, socat, and a kernel that allows unprivileged user namespaces.
31* **Ask the server's administrator** to set up what the sandbox needs: bubblewrap 0.8.0 or later and socat, installed for the whole system (from the distribution's packages, or by root in `/usr/local/bin`), and a kernel that allows unprivileged user namespaces.
32* **Approve a copy of your own.** In version 0.1.71 and later, Claude Science can run bubblewrap and socat that you installed yourself, once you [approve them](#approve-your-own-copy-of-bubblewrap-or-socat).
3233* **Use the server as an SSH host.** Install Claude Science on your own computer and add the server as an SSH host (see [Remote compute clusters](https://claude.com/docs/claude-science/remote-compute-clusters.md)), if your organization allows SSH hosts. Claude runs jobs on the server under your own account, with your approval. Jobs run outside the sandbox, so the server doesn't need bubblewrap, socat, or the kernel setting, and you don't need administrator access there.
3334
34Administrators usually install bubblewrap and socat, and only an administrator can change the kernel setting. On Ubuntu 23.10 and later, bubblewrap can also need an AppArmor profile that lets it create user namespaces. Claude Science checks for these when it starts and names the first one that's missing. Once that's fixed, the next start names the next one, if any.
35Only an administrator can install bubblewrap and socat for the whole system or change the kernel setting. On Ubuntu 23.10 and later, bubblewrap can also need an AppArmor profile that lets it create user namespaces. Claude Science checks for these when it starts and names the first one that's missing. Once that's fixed, the next start names the next one, if any.
3536
3637Installing Claude Science itself doesn't need root or `sudo`. The installer puts the `claude-science` command in `~/.local/bin`, or in another folder you own if you export `CLAUDE_SCIENCE_INSTALL_DIR` with that folder's path before you run it.
3738
from line 43
4243* If the cluster's address sends you to one of several login nodes, connect the tunnel to the node where Claude Science is running. Running `hostname` on that node prints its name.
4344* Claude Science needs about 10 GB free in your home folder for its first launch, and more for each environment Claude creates, even if you keep your projects elsewhere.
4445
46### Approve your own copy of bubblewrap or socat
47
48In version 0.1.71 and later, Claude Science runs a copy of bubblewrap or socat that isn't in `/usr/bin`, `/usr/local/bin`, or `/bin` only after you approve it. That includes copies from conda, pixi, a cluster module, or your home folder. An approval can't get around user namespaces that the kernel or AppArmor blocks. Claude Science ignores approvals where your organization [manages the network allowlist](https://claude.com/docs/claude-science/admin-controls.md#network-allowlist), and inside a container or sandbox that remaps user accounts.
49
50An approved socat lets Claude Science start, but code that Claude runs has no network access until an administrator installs socat in a system folder. On a new install, Claude Science then can't set up its starter Python and R environments. It reports "Package downloads are being blocked by network policy" even when the network blocks nothing, and the package mirror it suggests won't help.
51
52To install both tools with conda and approve them on 0.1.71 and later, [install Claude Science](#install-claude-science), stop it with `claude-science stop` if it's running, and run these commands in a terminal:
53
54```bash theme={null}
55conda create -y --copy --override-channels -p ~/claude-science-tools -c conda-forge bubblewrap socat
56claude-science sandbox approve --bwrap ~/claude-science-tools/bin/bwrap --socat ~/claude-science-tools/bin/socat
57```
58
59Type `y` at "Approve? \[y/N]". When it prints "Approved bubblewrap" and "Approved socat", start Claude Science again. Claude Science runs a private copy of each program, so run the second command again whenever you update yours.
60
61On 0.1.70 and earlier, which have no `sandbox approve`, run only the first command, then the [install command](#install-claude-science). In the approval steps that it prints, give the two paths from the second command, then start Claude Science again.
62
63To approve copies you installed yourself, put the path of each program in the second command, not the path of a launcher. For example, after `pixi global install bubblewrap socat`, `command -v bwrap socat` shows launchers in `~/.pixi/bin`, and the programs are `~/.pixi/envs/bubblewrap/bin/bwrap` and `~/.pixi/envs/socat/bin/socat`. If the command says "not approved", see [not approved](https://claude.com/docs/claude-science/troubleshooting.md#not-approved).
64
4565## Install Claude Science
4666
4767```bash theme={null}
from line 109
89109
90110## Keep it up to date
91111
92`claude-science update` checks for and installs updates. See [Command line settings](https://claude.com/docs/claude-science/command-line-settings.md) for the command reference, including `logs` and the `serve` flags.
112`claude-science update` checks for and installs updates. If your bubblewrap or socat isn't in a system folder, see [Update Claude Science](https://claude.com/docs/claude-science/update-claude-science.md#from-a-terminal-or-on-a-server) first. See [Command line settings](https://claude.com/docs/claude-science/command-line-settings.md) for the command reference, including `logs` and the `serve` flags.
93113
94114## Troubleshooting
95115
from line 116
96116| Symptom | What it means |
97117| - | - |
98118| `command not found: claude-science` | `~/.local/bin` isn't on your PATH yet. Run `. ~/.profile` or open a new terminal. |
99| An error mentioning `bwrap was found on PATH at`, `is not where Claude Science runs it from`, `(PATH is not searched)`, or `is deliberately not used` | Version 0.1.61 prints these messages, because it needs bubblewrap and socat installed for the whole system. If you updated to it from inside the app, the "Update available" notice shows "restart aborted" instead. Version 0.1.62 withdraws that requirement. On the server, run `claude-science update`, then start Claude Science again. |
100| An error mentioning `bwrap not found on PATH` | bubblewrap isn't installed, or isn't on your PATH. Install it as shown in [Install dependencies](#install-dependencies), or ask the server's administrator. |
101| An error mentioning `socat is required` | socat isn't installed, or isn't on your PATH. Install it as shown in [Install dependencies](#install-dependencies), or ask the server's administrator. |
102| A line starting `[sandbox]` that says `no usable socat command was found on this computer`, in the terminal where `claude-science serve` runs or in its log (`claude-science logs`) | Claude Science started, but the sandbox has no network access. The sandbox runs socat only from system folders such as `/usr/bin`, and doesn't use a copy from conda, Homebrew, or a folder in your home directory. Code that Claude runs can't reach the internet, and environment setup can fail with `Package downloads are being blocked by network policy` even when the network blocks nothing. Install socat as shown in [Install dependencies](#install-dependencies), or ask the server's administrator to install it for the whole system. |
103| An error mentioning `bwrap too old` | The server's bubblewrap is older than 0.8.0. Upgrade it, or use a distribution that ships a newer version, such as Ubuntu 24.04 or later. |
119| An error mentioning `bwrap not found in` or `bwrap was found on PATH at` | bubblewrap isn't installed in a system folder. In version 0.1.71 and later, Claude Science doesn't search your PATH, so it doesn't use a copy from conda, pixi, a cluster module, or your home folder until you approve it. Install it as shown in [Install dependencies](#install-dependencies), ask the server's administrator, or [approve a copy of your own](#approve-your-own-copy-of-bubblewrap-or-socat). If this happened after you typed `claude-science update`, you can [go back to version 0.1.70](https://claude.com/docs/claude-science/troubleshooting.md#not-approved). |
120| An error mentioning `socat is required` | socat isn't installed in a system folder, and Claude Science doesn't use a copy that's only elsewhere on your PATH. Install it as shown in [Install dependencies](#install-dependencies), or ask the server's administrator. If you can't do either, you can [approve a copy of your own](#approve-your-own-copy-of-bubblewrap-or-socat) so that Claude Science starts. Until socat is in a system folder, environment setup fails with `Package downloads are being blocked by network policy`, because code that Claude runs has no network access. If this happened after you typed `claude-science update`, you can [go back to version 0.1.70](https://claude.com/docs/claude-science/troubleshooting.md#not-approved). |
121| A line starting `[sandbox]` that says `sandboxed commands run without network access`, in the terminal where `claude-science serve` runs or in its log (`claude-science logs`) | Claude Science started, but the sandbox has no network access. The sandbox runs socat only from system folders such as `/usr/bin`, and doesn't use a copy from conda, pixi, a cluster module, or your home folder, including a copy that you approved. Code that Claude runs can't reach the internet, and environment setup fails with `Package downloads are being blocked by network policy` even when the network blocks nothing. Install socat as shown in [Install dependencies](#install-dependencies), or ask the server's administrator to install it for the whole system. |
122| An error mentioning `too old` | The copy of bubblewrap that the message names is older than 0.8.0. Upgrade it, or use a distribution that ships a newer version, such as Ubuntu 24.04 or later. If you can't upgrade it, [approve a newer copy of your own](#approve-your-own-copy-of-bubblewrap-or-socat). |
104123| An error mentioning `cannot create unprivileged user namespaces` | The kernel or an AppArmor profile blocks the sandbox from creating user namespaces; some Ubuntu 24.04 images restrict this. The error message names the settings to check on Ubuntu, Debian, and other distributions. |
105124| An error mentioning `port 8765 is already in use by another app` | Another program is using the port you chose with `--port`. Quit that program, or choose a different port. After you start Claude Science, `claude-science url` prints both ports to forward. |
106125| An error mentioning `port 8765 is already in use by another Claude Science daemon` | Another copy of Claude Science, probably one using a different data folder, holds the port. Run `claude-science stop` where that copy was started, or choose a different port. |
from line 130
111130| Interactive HTML previews render as static snapshots after a short delay (charts don't respond) | The tunnel isn't forwarding the preview port. Add the second `-L` forward for the preview port that `claude-science url` prints (8001 by default), with that number on both sides. |
112131| The browser can't reach `localhost:8000` | The tunnel isn't up; rerun the `ssh -L` command. If the tunnel is up, confirm Claude Science is running on the server with `claude-science status`. |
113132| The installer reports no binary for your platform | Claude Science on Linux needs x64 with glibc. arm64 servers and musl-based distributions such as Alpine aren't supported. |
114| The installer stops with a message mentioning `was NOT installed` | Claude Science was already installed on the server, so the installer first tried to check that the new version starts there. The check didn't succeed, so nothing was replaced. The message and the lines under it say why and, where there is a fix, what to do. If they point to the [configuration file](https://claude.com/docs/claude-science/configuration-file-reference.md), `~/.claude-science/config.toml`, fix what they report in that file, then run the installer again as shown in [Install Claude Science](#install-claude-science). Otherwise, keep using the copy you already had. |
133| The installer stops with a message mentioning `was NOT installed` | Claude Science was already installed on the server, so the installer first tried to check that the new version starts there. The check didn't succeed, so nothing was replaced. The message and the lines under it say why and, where there is a fix, what to do. If they point to the [configuration file](https://claude.com/docs/claude-science/configuration-file-reference.md), `~/.claude-science/config.toml`, fix what they report in that file, then run the installer again as shown in [Install Claude Science](#install-claude-science). If they give no fix, keep using the copy you already had. |
115134
claude-science/tools-and-environments Changed · +9 / -1 lines
### Python package sources for starter and task environments
from line 25
2525
2626To have conda and pip download packages from an internal mirror instead, see [Point package installs at an internal mirror](https://claude.com/docs/claude-science/corporate-networks.md#point-package-installs-at-an-internal-mirror).
2727
28A package installed into an environment is permanent and available in every session and project using that environment. A package installed inline in a code cell (`pip install` or `install.packages()`) lasts only until the kernel restarts. To keep a package, ask Claude to install it into the environment.
28A package installed into an environment is permanent and available in every session and project using that environment. A package installed inline in a code cell (`pip install` or `install.packages()`) lasts only until the kernel restarts. To keep a package, ask Claude to install it into the environment. For a Python package Claude can't install there with pip, see [Python package sources for starter and task environments](#python-package-sources-for-starter-and-task-environments).
2929
3030For tools without a package, Claude downloads source, builds it in the sandbox with compilers from conda-forge, and saves the build as an artifact for reuse.
3131
3232The sandbox has no root access or system package manager. `apt` and `sudo` aren't available; Claude uses conda-forge or builds from source instead.
33
34### Python package sources for starter and task environments
35
36When Claude uses pip to install a Python package into a [starter](#starter-environments) or [task environment](#task-environments), it installs only prebuilt packages (wheels) from PyPI or, if one is set up, your [internal mirror](https://claude.com/docs/claude-science/corporate-networks.md#point-package-installs-at-an-internal-mirror). It doesn't install a package from a git repository, a web address, a local folder, or a local file. If the package, or a package it depends on, has no wheel for your computer and Python version, the install fails. That includes a package published only as source code.
37
38When the newest version of a package has no wheel for your computer and Python version but an older version does, pip installs the older version. To find out which version you have, ask Claude. If you need the newest version, use one of the ways below.
39
40To use a package Claude can't install this way, ask Claude to install it into the environment with conda if conda-forge has it. Otherwise, ask Claude to install it with pip in a code cell, where it lasts only until the kernel restarts.
3341
3442### Environments in granted folders
3543
claude-science/troubleshooting Changed · +35 / -2 lines
### Not updated; the current version still works ### not approved
from line 89
8989
9090On the "Update available" notice, this means the new version was downloaded but didn't start. On a Mac or Linux, if the message says "restart aborted" and you started Claude Science from a terminal, follow [the terminal steps](https://claude.com/docs/claude-science/update-claude-science.md#from-a-terminal-or-on-a-server). Otherwise, if Claude Science is still running, it's the version you had, and you can try again: select **Check for updates** under **Settings > General > About**, then select **Restart to update** there. On Windows, if trying again fails, leave Claude Science open and follow [the Windows steps](https://claude.com/docs/claude-science/update-claude-science.md#if-the-update-still-fails). If Claude Science has stopped, start it again.
9191
92On Linux, an update to version 0.1.61 ends this way on a computer where bubblewrap or socat came from conda, Homebrew, or a folder in your home directory, because version 0.1.61 needs both installed for the whole system. Version 0.1.62 withdraws that requirement, so updating again now gets a version that starts. If Claude Science won't start at all, run `claude-science update` in a terminal, then start it again.
93
9492In version 0.1.67 and later, the notice can show one of these two sentences, with the new version's error on a **Reason** line when there is one:
9593
9694* "Update failed: the new version couldn't start. You're still on version …" (Linux only) means Claude Science went back to the version you had.
9795* "The update is installed, but the restart failed. The next start will run the new version." means the new version is in place but didn't start; the steps for "restart aborted" still apply.
9896
97### Not updated; the current version still works
98
99On Linux, the "Update available" notice shows these words on its **Reason** line when the new version checked your computer before it was installed and couldn't confirm that it would start there. Claude Science keeps running the version you had. The rest of the line says what the new version needs. If it names bubblewrap or socat, version 0.1.71 and later run both only from system folders or a copy you've approved. Install them with the command for your distribution in the Linux tab of [Install](https://claude.com/docs/claude-science/get-started.md#install). Without administrator access, [get a copy of your own](https://claude.com/docs/claude-science/run-on-remote-linux-server.md#approve-your-own-copy-of-bubblewrap-or-socat) first, then run the install command from that tab again: it keeps the version you have and prints the steps to approve that copy.
100
99101### Couldn't check for updates
100102
101103On a Mac where Claude Science opens in its own window, the **Updates** window shows this message when Claude Science couldn't get update information from Anthropic's update server. The same steps apply when it says "Couldn't download the update":
from line 106
104106* If you cancelled a request from macOS for an administrator's password, select **Try again**.
105107* Otherwise, such as when it says "Updates aren't available right now", wait a few minutes, then select **Try again**.
106108* On a corporate network, ask your IT team to allow `storage.googleapis.com` (see [Proxy and certificates for updates in the Mac app window](https://claude.com/docs/claude-science/corporate-networks.md#proxy-and-certificates-for-updates-in-the-mac-app-window)).
109
110### not approved
111
112On Linux, version 0.1.71 can refuse to start after you type `claude-science update` if your bubblewrap or socat isn't in `/usr/bin`, `/usr/local/bin`, or `/bin`. That includes copies from conda, pixi, a cluster module, or your home folder. The refusal includes "Sandbox unavailable:". The `claude-science sandbox approve` command that it suggests then says "not approved", for example if your copy needs a library "which this system does not have".
113
114To go back to version 0.1.70, run this command in a terminal on the computer where Claude Science runs. The flag is safe only in this command, because version 0.1.70 stores sessions the same way as version 0.1.71:
115
116```bash theme={null}
117claude-science update --to f866abff --accept-layout-downgrade
118```
119
120When it prints "Updated" and `f866abff`, start Claude Science again.
121
122Claude Science then offers 0.1.71 again. Don't type `claude-science update` until you've approved copies that work. [Updating from the app](https://claude.com/docs/claude-science/update-claude-science.md#update-from-the-app) or with the Linux command under [Install Claude Science again](https://claude.com/docs/claude-science/update-claude-science.md#install-claude-science-again) is safe, because you keep your version if the new one can't start.
123
124Instead of going back, run the commands for your case in a terminal, type `y` at "Approve? \[y/N]", and start Claude Science again. If only one of the two tools is your own copy, give only that tool's option, `--bwrap` or `--socat`. If you installed the tools with `pixi global install`, approve pixi's real programs, because its launchers in `~/.pixi/bin`, which `command -v bwrap socat` shows, can't be approved:
125
126```bash theme={null}
127claude-science sandbox approve --bwrap ~/.pixi/envs/bubblewrap/bin/bwrap --socat ~/.pixi/envs/socat/bin/socat
128```
129
130If those paths don't exist, `ls ~/.pixi/envs/*/bin/bwrap ~/.pixi/envs/*/bin/socat` shows where pixi put the programs.
131
132If you have conda and a network connection, install both tools into a folder of their own and approve those copies:
133
134```bash theme={null}
135conda create -y --copy --override-channels -p ~/claude-science-tools -c conda-forge bubblewrap socat
136claude-science sandbox approve --bwrap ~/claude-science-tools/bin/bwrap --socat ~/claude-science-tools/bin/socat
137```
138
139On 0.1.70, which has no `sandbox approve`, these approve commands don't work. Run the `conda create` line if you use conda, then the Linux install command. In the approval steps that it prints, give the paths of copies that work, such as `~/claude-science-tools/bin/bwrap` and `~/claude-science-tools/bin/socat` or pixi's real programs, not what `command -v bwrap socat` shows, which would be refused. If you have neither conda nor pixi, stay on 0.1.70 and ask your administrator to install bubblewrap 0.8.0 or later and socat in `/usr/local/bin`.
107140
claude-science/update-claude-science Changed · +5 / -1 lines
from line 26
2626
2727## From a terminal or on a server
2828
29Run these commands in a terminal on the computer where Claude Science runs. The second one stops running sessions.
29Run these commands in a terminal on the computer where Claude Science runs. The second one stops running sessions. On Linux, if `command -v bwrap` or `command -v socat` prints a path that isn't in `/usr/bin`, `/usr/local/bin`, or `/bin`, [update from the app](#update-from-the-app) or [install Claude Science again](#install-claude-science-again) instead, and see [not approved](https://claude.com/docs/claude-science/troubleshooting.md#not-approved).
3030
3131```bash theme={null}
3232claude-science update
from line 54
5454* **Claude Science still asks you to update**: on Windows, if an update said "restart aborted" or "The update is installed", follow the entry above instead. On a Mac where Claude Science opens in its own window, quit it with Command-Q, wait ten seconds, then open it from your **Applications** folder. Anywhere else, run `claude-science stop` in a terminal (on a Mac or Linux, if the command isn't found, type `~/.local/bin/claude-science stop`), quit Claude Science if you're on a Mac, then open it again. If `claude-science stop` says "Not killing pid", follow [the terminal steps](#from-a-terminal-or-on-a-server).
5555* **The message says "restart aborted" or "The update is installed"**: on a Mac or Linux, if you started Claude Science from a terminal, follow [the terminal steps](#from-a-terminal-or-on-a-server). Otherwise, follow [restart aborted](https://claude.com/docs/claude-science/troubleshooting.md#restart-aborted).
5656* **The message says "the new version couldn't start"**: you're still on the version you had. Updating again, even from a terminal, gets the same version until a newer one is released, so contact [Claude support](https://support.claude.com/en/articles/9015913-how-to-get-support) with the exact words you see.
57* **On Linux, version 0.1.71 won't start after you typed `claude-science update`**: see [not approved](https://claude.com/docs/claude-science/troubleshooting.md#not-approved) before you try 0.1.71 again. To go back to version 0.1.70, run this command in a terminal on the computer where Claude Science runs, then start Claude Science again (the flag is safe only in this command):
58 ```bash theme={null}
59 claude-science update --to f866abff --accept-layout-downgrade
60 ```
5761* **Anything else**: on a Mac where Claude Science opens in its own window, contact [Claude support](https://support.claude.com/en/articles/9015913-how-to-get-support) with your version and the exact words you see. Anywhere else, [install Claude Science again](#install-claude-science-again), and contact support if that doesn't work.
5862
claude-science/command-line-settings Changed · +2 / -0 lines
from line 17
1717| `claude-science stop` | Stop the program cleanly. |
1818| `claude-science update` | Check for and install an update. `--check` only reports; `--to <build>` installs a specific build, which is also how you roll back (see [Roll back to an earlier build](#roll-back-to-an-earlier-build)). Updates are signature-verified and replace the binary atomically. On a Mac where Claude Science opens in its own window, update the app with **Claude Science > Check for App Updates…** in the menu bar. |
1919| `claude-science import` `<path>` | Merge another data directory, or its database file, into this one. |
20| `claude-science sandbox approve` | Linux only, version 0.1.71 or later. Approve your own copy of bubblewrap or socat for the sandbox. `--bwrap <path>` and `--socat <path>` name the programs, `--yes` skips the confirmation and is required when no terminal is attached, and `--remove` (alone, or with `--bwrap` or `--socat` and no path) removes the approval. Stop Claude Science first. See [Approve your own copy of bubblewrap or socat](https://claude.com/docs/claude-science/run-on-remote-linux-server.md#approve-your-own-copy-of-bubblewrap-or-socat). |
21| `claude-science sandbox status` | On Linux, version 0.1.71 or later, print which bubblewrap and socat the next start would try, the system's first, then yours. |
2022| `claude-science install` | Windows only. Install the app for your user account, with a PATH entry, a Start menu shortcut, and an uninstall entry under Windows **Settings > Apps > Installed apps**. Run it again to repair them. |
2123| `claude-science uninstall` | Windows only. Remove the app, its shortcuts, and its PATH entry while keeping your data; `--purge` also deletes the data directory. Quit Claude Science first. |
2224| `claude-science --version` | Print the version. |