Get started changedclaude-science/get-started
Nearest release: v2.1.312, published 3 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 27 Oct 2026 21: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 27 Oct 2026 22:07 UTC.
Upstream edited
Recorded here
Lines+7added
Lines−8removed
From line
48
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits20to this page, all time
The whole hunk
from line 48, old and new numbered
/
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.
No line in this hunk matches that.