Home Docs Claude Documentation

One capture · claude-docs

One read of Claude Documentationclaude-docs-20260929T070705Z

12 pages moved out of 256 read.

Pages moved 12 significant first

Pages read 256 in this capture

Captured 29 Sep 2026 07:07 UTC

Corpus hash 47cc94e6193d corpus-hash

What this read moved

1-12 of 12

claude-science/artifacts Changed · +8 / -4 lines

# Artifacts in Claude Science # Artifacts

from line 1

1# Artifacts

1# Artifacts in Claude Science

3> An artifact is a file Claude saves into the project: a figure, processed dataset, report, notebook, or other output.

3> Artifacts in Claude Science are files Claude saves into a project, such as figures, datasets, and reports. Open, version, trace, and delete them.

5An artifact is a file Claude saves into the project: a figure, processed dataset, report, notebook, or other output. Artifacts are stored on your computer in the app's data folder and persist until you delete them. Other files Claude writes during a session are temporary and are cleared a few hours after the session ends; ask Claude to save a scratch file if you want to keep it.

5In Claude Science, an artifact is a file Claude saves into the project: a figure, processed dataset, report, notebook, or other output. Artifacts are stored on your computer in the app's data folder and persist until you delete them. Other files Claude writes during a session are temporary and are cleared a few hours after the session ends; ask Claude to save a scratch file if you want to keep it.

7<Note>

8 If you use artifacts in a claude.ai chat rather than the Claude Science app, see [What are artifacts and how do I use them?](https://support.claude.com/en/articles/17153992-what-are-artifacts-and-how-do-i-use-them) in the help center instead.

9</Note>

711## Working with artifacts

812

9Click a linked file or a figure in the conversation to open it in a tab beside the chat. Ctrl/Cmd-click opens it full screen. HTML artifacts have zoom controls, including fit to width; images zoom up to their native resolution. Open **Files** in the sidebar for a searchable grid of every artifact in the project. From an artifact's menu you can: Open, Open beside session, **View in context**, **Provenance**, Versions, **Copy link**, **Star**, **Rename**, **Download**, or **Delete**. Renaming doesn't break links. **Delete** removes all versions permanently.

13Click a linked file or a figure in the conversation to open it in a tab beside the chat. Ctrl/Cmd-click opens it full screen. HTML artifacts have zoom controls, including fit to width; images zoom up to their native resolution. Open **Files** in the sidebar for a searchable grid of the project's artifacts. From an artifact's menu in **Files**, you can choose **Pin**, **Hide**, **Open in Artifact Viewer**, **View in context**, **Provenance**, **Copy link**, **Rename**, **Download**, **Export Metadata**, **Export to Cloud**, or **Delete**. Renaming doesn't break links. **Delete** removes all versions permanently.

1014

1115Files you attach or drop into the composer, and images you paste into it, are listed under **Your uploads**.

1216

claude-science/comments Changed · +6 / -2 lines

from line 1

11# Comments

3> Comments let you pin notes to specific parts of an artifact instead of describing a location in prose.

3> Comments in Claude Science pin a note to a specific part of an artifact, such as selected text or a point on a figure, and send the note to Claude.

5Comments let you pin notes to specific parts of an artifact instead of describing a location in prose. Select text in a Markdown, plain-text, LaTeX, or code file; select text in a PDF; click a point on an image or figure; or turn on **Comment** and click an element in a rendered HTML report. You can also comment on session transcripts. You can't comment on tables or other artifact types.

5In Claude Science, comments let you pin notes to specific parts of an artifact instead of describing a location in prose. Select text in a Markdown, plain-text, LaTeX, or code file; select text in a PDF; click a point on an image or figure; or turn on **Comment** and click an element in a rendered HTML report. You can also comment on session transcripts. You can't comment on tables or other artifact types.

7<Note>

8 This page covers comments on [artifacts in the Claude Science app](/docs/claude-science/artifacts). For artifacts in a claude.ai chat, see [What are artifacts and how do I use them?](https://support.claude.com/en/articles/17153992-what-are-artifacts-and-how-do-i-use-them) in the help center.

9</Note>

610

711## Leaving a comment

812

claude-science/get-started Changed · +90 / -12 lines

## Uninstall Claude Science

from line 2

33> Install Claude Science on macOS, Windows, or Linux, sign in with your Claude account, and run your first analysis.

5Install Claude Science on your computer, sign in with your Claude account, and run your first analysis. You need a Claude Pro, Max, Team, or Enterprise plan, and on Team and Enterprise plans an Owner must [turn Claude Science on](/docs/claude-science/enable-claude-science) first. For what each plan includes and how usage works, see [Plans and usage](/docs/claude-science/overview#plans-and-usage).

57## Install

79<Tabs>

810 <Tab title="macOS">

9 Download the installer from [claude.com/product/claude-science](https://claude.com/product/claude-science) and double-click to install. On first launch, the app sets up its runtime and starter Python and R environments, which takes a few minutes, then opens a new tab in your default browser. If no browser tab appears, choose Open from the menu bar icon.

11 Download the installer from [claude.com/product/claude-science](https://claude.com/product/claude-science) and double-click to install. On first launch, the app sets up its runtime and starter Python and R environments, which takes a few minutes, then opens a new tab in your default browser. If no browser tab appears, click **Claude Science** in the Dock.

1012 </Tab>

1113

1214 <Tab title="Windows">

from line 20

1820

1921 **Updates.** Claude Science checks for updates in the background and shows **Update available** when one is ready; choose **Restart to update** to install it. Administrators who distribute the app themselves can turn the background check off with `[update] auto_update = false` (see [Manage Claude Science on devices](/docs/claude-science/manage-on-devices#deploy-configuration-with-device-management)). To update by hand instead, open a newer installer, which upgrades the installed copy in place and keeps your data.

2022

21 **Uninstall.** Quit Claude Science from its notification-area icon first, because the uninstaller refuses to run while the app is running. Then uninstall **Claude Science** from **Settings** > **Apps** > **Installed apps**, or run `claude-science uninstall` in a terminal. Either way your data is kept. To remove the data as well, run `claude-science uninstall --purge` in a terminal instead.

23 **Uninstall.** To remove the app, follow the Windows steps in [Uninstall Claude Science](#uninstall-claude-science).

2224

2325 **Corporate networks.** Claude Science follows the proxy configured in Windows proxy settings and trusts corporate root certificates installed for the whole computer, so most managed PCs need no Claude Science configuration. See [Use Claude Science on a corporate network](/docs/claude-science/corporate-networks).

2426

from line 31

2931 * [Custom connectors](/docs/claude-science/custom-connectors) that run a local command start with `npx`, `node`, `python`, or the full path of a program. Connectors launched through `npm` or a `.cmd`, `.bat`, or `.ps1` file aren't supported.

3032 * The **Model endpoints** section of **Settings** > **Compute** (NVIDIA BioNeMo NIM) isn't available.

3133

32 **Linux version under WSL.** The Windows app itself doesn't need WSL. The Linux command-line version of Claude Science also runs under Windows Subsystem for Linux (WSL 2) with Ubuntu 24.04 or later. Inside the Ubuntu terminal, follow the install steps in the Linux tab, then start Claude Science with `claude-science serve --port 8765 --no-browser` instead, and open the printed link in a Windows browser.

34 **Linux version under WSL.** To use Claude Science from a Linux environment on your Windows computer, run the Linux command-line version under Windows Subsystem for Linux (WSL 2, not WSL 1) with Ubuntu 24.04 or later. The Windows app itself doesn't need WSL. Inside the Ubuntu terminal, follow the install steps in the Linux tab, then start Claude Science with `claude-science serve --port 8765 --no-browser` and open the printed link, which starts with `http://127.0.0.1:8765`, in a Windows browser. Projects you create there stay in WSL, and the Windows app keeps its own.

36 If Claude Science under WSL shows one of these errors or problems, use the matching fix:

38 * `daemon already running`: Claude Science is already running. Run `claude-science url` to print a fresh link, and open it in a Windows browser.

39 * `port 8765 is already in use`: another program, or another copy of Claude Science, has that port. Start with a different one, for example `--port 8080`.

40 * The link stops working: check that Claude Science is still running with `claude-science status`. If it's still running, run `claude-science url` for a fresh link and open it in a Windows browser. Claude Science stops when WSL shuts down, for example after `wsl --shutdown`. Start it again by running `claude-science serve --port 8765 --no-browser` in the Ubuntu terminal.

41 * An SSH host can't be added: under WSL, Claude Science reads the SSH settings in Ubuntu's `~/.ssh`, not the ones in Windows. Copy the host's entry from `C:\Users\<you>\.ssh\config`, and its key file, into Ubuntu's `~/.ssh` folder, then run `chmod 600` on them.

42 * `The database is on /mnt/*`: Claude Science's data folder is on a Windows drive, which it can't use under WSL. Move the folder into your Ubuntu home folder, such as the default `~/.claude-science`, and if you set `data_dir` or `--data-dir`, point it there. If you use a folder other than the default, choose a new, empty one, because Claude Science can delete files in that folder that it didn't create.

3343 </Tab>

3444

3545 <Tab title="Linux">

36 Install the sandbox dependencies, then run the installer. The sandbox needs bubblewrap 0.8.0 or later and socat, and installing them takes administrator (`sudo`) access; if you don't have it, ask your system administrator to install them.

46 Install 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](/docs/claude-science/run-on-remote-linux-server#run-claude-science-without-administrator-access).

3747

3848 * Ubuntu or Debian: `sudo apt-get update && sudo apt-get install -y curl bubblewrap socat`

3949 * Fedora or RHEL: `sudo dnf install -y curl bubblewrap socat`

from line 64

5464</Tabs>

5565

5666<Note>

57 Claude Science is a local application, not a website, so there's no public URL to visit. On Windows it opens in its own window, and on macOS and Linux it opens in a browser tab. Open it from the application itself: the menu bar icon on macOS, the Start menu on Windows, or the `claude-science` command on Linux. On a remote server, the sign-in link reaches your browser through an SSH tunnel; see [Run on a remote Linux server](/docs/claude-science/run-on-remote-linux-server).

67 Claude Science is a local application, not a website, so there's no public URL to visit. On Windows it opens in its own window, and on macOS and Linux it opens in a browser tab. Open it from the application itself: Claude Science in Applications or the Dock on macOS, the Start menu on Windows, or the `claude-science` command on Linux. On a remote server, the sign-in link reaches your browser through an SSH tunnel; see [Run on a remote Linux server](/docs/claude-science/run-on-remote-linux-server).

5868</Note>

5969

6070## Sign in and complete setup

from line 74

6474After sign-in, a setup wizard walks you through enabling connectors and skills, setting which websites Claude can access, and choosing whether memory is on. You can change these at any time in Settings.

6575

6676<Note>

67 Claude Science keeps your data in a single folder in your home directory: `~/.claude-science` on macOS and Linux, and `%USERPROFILE%\.claude-science` on Windows. On Linux, the `claude-science` command itself installs to `~/.local/bin`, and on Windows the app installs to `%LOCALAPPDATA%\Programs\ClaudeScience` and adds that folder to your user PATH. Beyond that, it doesn't modify your existing conda installation, R libraries, or shell configuration.

77 Claude Science keeps your data in a single folder in your home directory: `~/.claude-science` on macOS and Linux, and `%USERPROFILE%\.claude-science` on Windows. On Linux, the `claude-science` command itself installs to `~/.local/bin`, and on Windows the app installs to `%LOCALAPPDATA%\Programs\ClaudeScience` and adds that folder to your user PATH. Beyond that, it doesn't modify your existing conda installation, R libraries, or shell configuration. To remove Claude Science, see [Uninstall Claude Science](#uninstall-claude-science).

6878</Note>

6979

70<Warning>

71 Deleting the data folder removes all projects, artifacts, and conversation history. Deleting the folder and the application removes Claude Science entirely; on Windows, quit the app from its notification-area icon, then uninstall it from **Settings** > **Apps** > **Installed apps**.

72</Warning>

7480## Run your first analysis

7581

7682* Open the Example project, or create a new one.

from line 85

7985* Review the code-execution card when Claude proposes running code and choose whether to allow it.

8086* Results appear as artifacts in the Files panel.

8187

88## Uninstall Claude Science

90Uninstalling removes the application and keeps your data folder. Your projects, artifacts, and conversation history stay on your computer until you delete that folder.

92<Warning>

93 Deleting the data folder (`~/.claude-science`, or `%USERPROFILE%\.claude-science` on Windows) removes all your projects, artifacts, conversation history, environments, and settings, and signs you out. Copy anything you want to keep first, with **Download** on an artifact or by copying the project's folder from inside the data folder.

95 If you moved your data to another folder, check where it is under **Settings > Storage > Data location** before you uninstall. The environments and the sign-in stay in the default folder even then, so to remove all your data, delete both folders. First check that the folder you moved your data to holds nothing else you want to keep. Files in the folders you granted Claude access to aren't affected unless they're inside the folder you moved your data to.

96</Warning>

98<Tabs>

99 <Tab title="macOS">

100 <Steps>

101 <Step title="Quit Claude Science">

102 In the Dock, Control-click the **Claude Science** icon and choose **Quit**. If you started Claude Science from Terminal with `claude-science serve`, also run `claude-science stop`.

103 </Step>

104

105 <Step title="Move the application to the Trash">

106 In Finder, open the **Applications** folder and move **Claude Science** to the Trash. If **Claude Science** isn't there, look in the **Applications** folder inside your home folder.

107 </Step>

108

109 <Step title="Remove the Terminal command">

110 The app also adds a `claude-science` command for Terminal. Remove it with `rm ~/.local/bin/claude-science`.

111 </Step>

112 </Steps>

113

114 To remove your data as well, delete the `~/.claude-science` folder.

115 </Tab>

116

117 <Tab title="Windows">

118 <Steps>

119 <Step title="Quit Claude Science">

120 Right-click the Claude Science icon in the notification area of the taskbar and choose **Quit Claude Science**. The uninstaller doesn't run while the app is running.

121 </Step>

122

123 <Step title="Uninstall the app">

124 In Windows **Settings**, go to **Apps > Installed apps** and uninstall **Claude Science**. To remove the app and your data together, run `claude-science uninstall --purge` in a terminal instead.

125

126 If you changed the data location in **Settings > Storage > Data location**, `--purge` deletes that entire folder, including any files in it that Claude Science didn't create. Move those files out first. `--purge` also leaves `%USERPROFILE%\.claude-science` behind for you to delete.

127 </Step>

128 </Steps>

129 </Tab>

130

131 <Tab title="Linux">

132 For the Linux version under Windows Subsystem for Linux (WSL), run these commands in the Ubuntu terminal.

133

134 <Steps>

135 <Step title="Stop Claude Science">

136 ```bash theme={null}

137 claude-science stop

138 ```

139 </Step>

140

141 <Step title="Delete the command">

142 ```bash theme={null}

143 rm ~/.local/bin/claude-science

144 ```

145

146 If you installed it somewhere else, `command -v claude-science` shows where.

147 </Step>

148 </Steps>

149

150 To remove your data as well, delete the `~/.claude-science` folder.

151 </Tab>

152</Tabs>

153

154To reinstall, follow [Install](#install) again. Installing doesn't replace an existing data folder.

155

82156## Troubleshooting first launch

83157

84158* macOS says the application isn't supported, or the app icon appears crossed out: the download page picked the build for the wrong processor. Return to the download page and choose Mac (Intel) or Mac (Apple Silicon) to match your Mac. To check which you have, open the Apple menu, choose About This Mac, and look at the Chip or Processor line.

85* No browser tab appeared on macOS or Linux: on macOS, choose Open from the menu bar icon. On Linux, copy the printed URL into a browser on the same machine, or run `claude-science url` to print a fresh one.

159* No browser tab appeared on macOS or Linux: on macOS, click **Claude Science** in the Dock. On Linux, copy the printed URL into a browser on the same machine, or run `claude-science url` to print a fresh one.

86160* On macOS, some of Claude's tools can't start and the error mentions the Xcode license, usually right after an Xcode update: macOS won't run the Python that comes with Apple's developer tools until the license is accepted. Open Xcode and agree to the license with an administrator account, or run `sudo xcodebuild -license accept` in Terminal, then ask Claude to try again.

87161* 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.

88162* 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](/docs/claude-science/network-requirements)).

89* Linux refuses to start: a sandbox dependency is missing (install bubblewrap and socat as shown in the Install section), too old, or blocked. Check your bubblewrap version with `bwrap --version`, then match the error message to its fix in the [Linux troubleshooting table](/docs/claude-science/run-on-remote-linux-server#troubleshooting).

163* 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.

164* 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).

165* 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.

166* 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.

167* 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).

90168* 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](/docs/claude-science/multiple-computers).

91169* 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](/docs/claude-science/multiple-computers#access-work-from-another-sign-in-on-your-computer).

92170* Sign-in stops at claude.ai: your account is on the Free plan (upgrade required), the redirect couldn't return (use Paste a code), or your Team or Enterprise organization hasn't [enabled Claude Science](/docs/claude-science/enable-claude-science) yet.

claude-science/overview Changed · +33 / -1 lines

## Use Claude Science outside the life sciences ## Plans and usage ### When you reach a usage limit

from line 2

33> Anthropic's AI workbench for rigorous science.

5Claude Science is a desktop application that pairs Claude with an analysis environment on your computer. Available in beta on macOS, Windows, and Linux.

5Claude Science is a desktop application that pairs Claude with an analysis environment on your computer. Available in beta on macOS, Windows, and Linux. You install it separately from the Claude desktop app; see [Get started](/docs/claude-science/get-started#install) for the installers.

77You describe a research task or analysis in plain language; Claude writes and runs Python, R, or shell code in a sandbox, reads the folders you grant it, pulls data from scientific databases through connectors, and saves results as versioned artifacts with a full provenance record. A background reviewer can check Claude's claims against the work that was actually run.

from line 12

1212 Claude can make mistakes. The reviewer reduces, but doesn't eliminate, errors. It checks claims against the execution record and doesn't re-run analyses. Verify results before relying on them in research, publication, or downstream decisions. Claude Science is a research tool and isn't intended for clinical or diagnostic use.

1313</Note>

1414

15## Use Claude Science outside the life sciences

17Claude Science isn't limited to the life sciences. Besides biology, chemistry, and clinical and medical research, it supports computer science and machine learning, engineering, materials science, mathematics, physics, the social sciences, and other fields. Claude Science is for anyone who works through the loop of scientific discovery: generating hypotheses, reviewing literature, designing experiments, running long and complex data analyses, and turning the results into reproducible figures and findings. Claude writes and runs code and [installs the packages](/docs/claude-science/tools-and-environments#installing-packages) an analysis needs.

19In any field, Claude Science also gives you these tools:

21* **Remote compute.** For long-running or heavy analyses, Claude can run jobs on [a workstation or Slurm cluster you reach over SSH](/docs/claude-science/remote-compute-clusters), or on cloud GPUs through [your own Modal account](/docs/claude-science/compute-providers). On Team and Enterprise plans, your organization's admin decides whether you can use SSH hosts and Modal.

22* **Credentials.** Store credentials for [licensed literature](/docs/claude-science/literature-access), [cloud storage](/docs/claude-science/cloud-storage), and other APIs in **Settings > Credentials**, where they're encrypted on your computer.

23* **Review.** [The reviewer](/docs/claude-science/the-reviewer) can check Claude's claims against the work that actually ran, and you can add review criteria for your own field in **Settings > Specialists > Reviewer**.

25Researchers in the life sciences also get specialized [Featured connectors](/docs/claude-science/connectors-and-skills#featured-connectors) to databases in their fields, and skills for specific models, such as AlphaFold2 for protein structure. Other Featured connectors and skills work in any field: for example, the Literature Graph and Research Resources connectors search scholarly literature and funding opportunities, and the literature review skill helps Claude find, verify, and synthesize papers. To give Claude a data source or method from your own field, see [When the connector you need isn't listed](/docs/claude-science/connectors-and-skills#when-the-connector-you-need-isn%E2%80%99t-listed) and [Skills](/docs/claude-science/connectors-and-skills#skills).

1527## Requirements

1628

1729* A Claude account on a Pro, Max, Team, or Enterprise plan. On Team and Enterprise plans, an Owner must [enable Claude Science for the organization](/docs/claude-science/enable-claude-science) first.

from line 30

1830* macOS 13 or later (Apple silicon or Intel), Windows 11 (x64), or Linux x64 on a glibc-based distribution.

1931* About 5 GB of free disk space for the runtime and starter environments.

2032* On Linux: socat, bubblewrap 0.8.0 or later, and unprivileged user namespaces permitted by the kernel.

34## Plans and usage

36Claude Science is included in Pro, Max, Team, and Enterprise plans, with nothing separate to buy. Team and Enterprise Owners control whether Claude Science is available to their members through [an admin setting](/docs/claude-science/enable-claude-science). Claude Science isn't available on the Free plan. Scientists at academic and nonprofit research institutions can also get it through the discounted [Claude Team plan for scientists](https://claude.com/programs/team-plan-for-scientists).

38Your Claude Science usage counts toward the same usage limits as the rest of your Claude plan, including Claude Code and Cowork. In Claude Science, **Settings > Usage** shows how much you've used and when each limit resets.

40You pay more than your plan's price only in these cases:

42* **Usage credits and extra usage.** On Pro and Max plans, you can turn on usage credits under **Settings > Usage** in Claude Science to keep working past your limits, and set a monthly spend limit there. Team plans call the same option extra usage, and your admin turns it on. In Claude Science it appears as **Usage credits**, but only Pro and Max plans can change it there. On Team and Enterprise plans, your admin sets spend limits. Some models need usage credits on some plans, and [Claude pricing](https://claude.com/pricing) lists which models each plan includes.

43* **Usage-based Enterprise plans.** Instead of fixed usage limits, your organization pays for usage on top of the seat price, within the spend limits your admin sets.

44* **Services you connect with your own account.** Services such as [Modal](/docs/claude-science/compute-providers) bill you directly. Anthropic doesn't bill for them.

46### When you reach a usage limit

48On plans with usage limits, there's a limit that resets every 5 hours and a weekly limit. As you approach one, Claude Science asks whether the session should continue. For the 5-hour limit, you can choose **Keep going** or hold the session until the limit resets. For the weekly limit, the warning offers only **Keep going**.

50* **Without usage credits or extra usage, when the reset is less than 8 hours away.** The session pauses, and the composer shows when it will resume. Your conversation, files, and artifacts are kept. As long as Claude Science stays open, the session picks up where it left off when the limit resets.

51* **Without usage credits or extra usage, when the reset is more than 8 hours away.** The session pauses for up to 8 hours, then stops and shows when the limit resets. This can happen at a weekly limit. To continue after the reset, select **Resume** or send a message.

52* **At the limit, with usage credits or extra usage turned on.** By default, Claude Science asks whether to keep going on your usage credits or extra usage. Until you answer, the session waits. If you choose not to continue, the session waits for the reset, or stops if the reset is more than 8 hours away.

2153

claude-science/remote-compute-clusters Changed · +3 / -3 lines

from line 14

1414Optionally override **User**, **Port**, or **Identity file** under **Advanced**.\

1515Click **Add**.

1616

17Adding a host runs a read-only probe that records CPUs, memory, GPUs, CUDA driver, presence of conda/modules/Apptainer, scratch directories, and whether `sbatch` exists. On SLURM clusters it reads partitions. Results are saved as editable notes on the host's detail page; re-run with **Probe**.

17Adding a host runs a probe that records CPUs, memory, GPUs, CUDA driver, presence of conda/modules/Apptainer, scratch directories, and whether `sbatch` exists. On Slurm clusters it reads partitions. Results are saved as editable notes on the host's detail page; re-run with **Probe**.

1818

1919## Running jobs

2020

21Workstations run jobs as detached processes. SLURM clusters receive jobs via `sbatch`. Jobs survive connection loss.

21On a host with Slurm's `sbatch` command, Claude Science submits jobs to Slurm by default. On a host without it, such as a workstation, jobs run as detached processes directly on the host you added. Claude Science doesn't submit jobs to other schedulers, such as PBS or LSF, so on a cluster that uses one, add a host where your site allows running jobs directly. Jobs survive connection loss.

2222

23On the host's detail page, set **Scratch directory** (must be on a shared filesystem for SLURM) and **Concurrent job limit** (default 100).

23On the host's detail page, set **Scratch directory** (must be on a shared filesystem for Slurm) and **Concurrent job limit** (default 100).

2424

2525When Claude proposes a remote job, a **Run this job on `<host>`?** card shows the command and script. Approve with **Once**, **This conversation**, **This project**, or **Global** scope. On approval, the job script and inputs are copied to a job directory under the scratch directory.

2626

claude-science/run-on-remote-linux-server Changed · +28 / -2 lines

## Run Claude Science without administrator access

from line 12

1212

1313## Install dependencies

1414

15Claude runs code inside a sandbox, and the sandbox needs two system packages: bubblewrap and socat. On Ubuntu or Debian:

15Claude runs code inside a sandbox, and the sandbox needs two system packages: bubblewrap and socat. Installing them takes administrator (`sudo`) access. Without it, see [Run Claude Science without administrator access](#run-claude-science-without-administrator-access).

1616

17On Fedora, RHEL, or Arch, use the command for your distribution from the Linux tab of [Install](/docs/claude-science/get-started#install). On Ubuntu or Debian, run:

1719```bash theme={null}

1820sudo apt-get update && sudo apt-get install -y curl bubblewrap socat

1921```

from line 24

2224 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. The sandbox isn't optional: Claude Science refuses to start rather than run code unsandboxed.

2325</Note>

2426

27## Run Claude Science without administrator access

29If you don't have administrator (root or `sudo`) access to a shared server or cluster, choose one of these:

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.

32* **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](/docs/claude-science/remote-compute-clusters)), 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.

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.

36Installing 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.

38If you run Claude Science on a cluster's login node, these points differ from a server you have to yourself:

40* Check your site's rules first. Claude runs its analysis code on the machine where Claude Science runs, and many sites limit long-running or heavy work on login nodes.

41* Choose your own port, because someone else may already be using the default port, 8000. [Start Claude Science](#start-claude-science) shows how to pass a port. After you start it, `claude-science url` prints both ports. Forward each one with that number on both sides.

42* 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.

43* Claude Science needs about 5 GB in your home folder for its environments, even if you keep your projects elsewhere.

2545## Install Claude Science

2646

2747```bash theme={null}

from line 94

7494| Symptom | What it means |

7595| - | - |

7696| `command not found: claude-science` | `~/.local/bin` isn't on your PATH yet. Run `. ~/.profile` or open a new terminal. |

97| 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. |

98| 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. |

7799| 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. |

78| 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 exact setting to change for your distribution. |

100| 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. |

101| 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. |

102| 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. |

103| A message mentioning `port 8000 is in use by another app — using port 8001 instead` | Claude Science started on the port it names. `claude-science url` prints both ports. Forward each one with that number on both sides. Or stop Claude Science and start it again with `--port`. |

104| A message mentioning `daemon already running on port 8000` | Claude Science is already running. Run `claude-science url` for a fresh sign-in link, or `claude-science stop` to stop it. |

79105| The sign-in link shows an expired-link page | Links are single-use and valid for about three minutes. Run `claude-science url` on the server and open the fresh link; restarting with `claude-science stop` then `claude-science serve --no-browser` also prints one. |

80106| Sign-in stops at claude.ai | The redirect couldn't return through the tunnel (choose **Paste code instead**), your account is on the Free plan (an upgrade is required), or your Team or Enterprise organization hasn't [enabled Claude Science](/docs/claude-science/enable-claude-science) yet. |

81107| 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; the preview port is the web app port plus one (8001 by default). |

claude-science/troubleshooting New page · 64 lines, new page

# Troubleshoot Claude Science ## Sign-in and replies ### No credentials available for Anthropic API ### Claude is at capacity — retrying ### Agent Failed ## Python, R, and connectors ### Environments failed ### failed to load 5 times in a row — automatic retries are paused ## Updates ### cannot reach the public release endpoint

A whole new page. There's nothing to diff it against, so here is what it says.

# Troubleshoot Claude Science

> Fix errors you see while using Claude Science: being signed out, capacity retries, Agent Failed, environment setup, connectors, and updates.

This page covers error messages that Claude Science shows while you work. Other problems have their own troubleshooting sections:

* Installing and signing in for the first time: [Troubleshooting first launch](/docs/claude-science/get-started#troubleshooting-first-launch).
* Running Claude Science on a Linux server: the troubleshooting table on [Run on a remote Linux server](/docs/claude-science/run-on-remote-linux-server#troubleshooting).
* Proxies, TLS inspection, and package mirrors: [Troubleshooting corporate network errors](/docs/claude-science/corporate-networks#troubleshooting-corporate-network-errors).
* A session that pauses at a usage limit: [When you reach a usage limit](/docs/claude-science/overview#when-you-reach-a-usage-limit).

## Sign-in and replies

The messages in this section appear in a conversation, in place of Claude's reply or under it.

### No credentials available for Anthropic API

Claude Science is no longer signed in to your Claude account, so it can't send your message.

* If a "You've been signed out" notice appears, select **Sign in** on it, then send your message again.
* If the whole window shows "You've been signed out." instead, follow the step that page names to continue.
* If neither appears, select the gear icon and choose **Sign out**, then confirm with **Sign out**. Signing out stops any sessions that are still running. Sign in again and send your message.

If you see "Your Claude session is no longer valid. Please sign out and sign in again." instead, sign out and sign in again the same way.

Your sign-in lasts a limited time. In the last three days before it expires, Claude Science shows a notice that says when it expires. Select **Sign in again** on that notice to renew your sign-in before it ends.

### Claude is at capacity — retrying

Claude is busy or is limiting your requests, and Claude Science is retrying. Claude Science keeps retrying on its own, and once a retry goes through, Claude's reply starts again. Select **Check service status** to see whether there's an incident. To stop waiting, select the stop button in the composer. If your plan's usage limit runs out while Claude Science is retrying, the session pauses instead, as described in [When you reach a usage limit](/docs/claude-science/overview#when-you-reach-a-usage-limit).

These other retry messages can appear in the same place:

* "Claude is temporarily unavailable — retrying" means Claude returned a server error and Claude Science is retrying. This message also has a **Check service status** link.
* "Connection issue — retrying" means Claude Science couldn't reach Claude and is retrying. Check your internet connection.

### Agent Failed

An "Agent Failed" box ends a reply when Claude Science hits an error it has no specific explanation for. The box shows the error's own text, and the line under it can show an HTTP status and a request ID. If the box's text is one of the messages on this page, such as "No credentials available for Anthropic API", follow that section instead. To get help, contact [Claude support](https://support.claude.com/en/articles/9015913-how-to-get-support) and include the request ID.

## Python, R, and connectors

Claude Science sets up Python and R environments on your computer so Claude can run code, and it starts the Featured connectors that run on your computer. The messages in this section appear when an environment can't be set up or one of those connectors can't start.

### Environments failed

A notice such as "2 environments failed" means Claude Science couldn't set up one or more of the environments Claude uses to run code, and it names them. Select **Details** to see each environment's status and, for any that failed, the error.

* If setup failed because of your organization's network, the dialog that **Details** opens links to settings for a package mirror, a CA bundle, or mirror credentials. When you save any of these settings, Claude Science retries the failed setups automatically. See also [Troubleshooting corporate network errors](/docs/claude-science/corporate-networks#troubleshooting-corporate-network-errors).
* To retry the environments that failed, select **Retry builds**.

If the notice reads "Analysis is unavailable" instead, no Python or R code can run until Claude Science restarts. Fix the cause the notice names, then quit and reopen Claude Science. On Windows, closing the window leaves Claude Science running, so right-click its icon in the notification area of the taskbar and choose **Quit Claude Science**.

### failed to load 5 times in a row — automatic retries are paused

This message appears in **Settings > Connectors** on a Featured connector marked **Failed** (hold the pointer over **Failed**) and on the connector's own page. The connector runs on your computer and failed to start five times in a row, so Claude Science stopped trying. Turn the connector off and on again in **Settings > Connectors**, or restart Claude Science.

## Updates

When an update is ready, Claude Science shows an "Update available" notice. If installing the update fails, that notice shows the error.

### cannot reach the public release endpoint

Claude Science couldn't reach the update server. Check your internet connection, then select **Restart to update** on the "Update available" notice to try again, or run `claude-science update` again. On a corporate network, see [Network requirements](/docs/claude-science/network-requirements#app-connections) for the domains Claude Science connects to.

claude-science/admin-controls Changed · +1 / -1 lines

from line 241

241241

242242| Setting in claude.ai | Status for Claude Science | Note |

243243| - | - | - |

244| Usage > Extra usage and Spend limits | Supported in Claude Science | Claude Science usage counts toward each member's 5-hour and weekly usage limits, in the same pool as Claude Code and Cowork. |

244| Usage > Extra usage and Spend limits | Supported in Claude Science | Claude Science usage counts the same way as Claude Code and Cowork usage. See [Plans and usage](/docs/claude-science/overview#plans-and-usage). |

245245| Billing | Supported in Claude Science | Claude Science uses the same seat as the rest of claude.ai, so there is nothing separate to purchase. |

246246| Models > Model access and Default model (Enterprise) | Supported in Claude Science | Claude Science follows your **Models** page. Turning a model off, for the whole organization or for a custom role, removes it from those members' model picker in the app within a few minutes, and requests for that model are refused. Your **Default model** setting applies in the app as it does in claude.ai. Team plans don't have the **Models** page. |

247247| Analytics (from the user menu) | Supported in Claude Science | Analytics has a **Claude Science** tab with adoption and session metrics, and the spend charts on the **Overview** tab can be filtered to Claude Science (see [Monitor usage](/docs/claude-science/monitor-usage)). |

claude-science/compute-providers Changed · +1 / -1 lines

from line 10

1010

1111### Workspace restrictions set by your organization

1212

13On Team and Enterprise plans, your organization's admin can limit Modal to specific workspaces. When Claude uses your Modal token, the app checks the workspace that Modal reports for that token, not the label in your `~/.modal.toml`. If that workspace isn't on your organization's list, the app tells you that this Modal workspace is not allowed by your admin, and Claude can't run jobs there until you connect a token from an allowed workspace. Your admin can also turn Modal off for the organization (see [Modal](/docs/claude-science/admin-controls#modal)).

13On Team and Enterprise plans, your organization's admin can limit Modal to specific workspaces. When Claude uses your Modal token, the app checks the workspace that Modal reports for that token, not the label in your `~/.modal.toml`. If that workspace isn't on your organization's list, the app tells you that this Modal workspace is not allowed by your admin, and Claude can't run jobs there until you connect a token from an allowed workspace. Your admin can also turn Modal on or off for the organization (see [Modal](/docs/claude-science/admin-controls#modal)).

1414

1515If your organization manages the network allowlist, set **Network restrictions** on the Modal page under **Settings** > **Compute** to **Allowlist** or **No network** before you run jobs. Jobs from a Modal setup with unrestricted network access are refused while your organization manages the list (see [Network allowlist](/docs/claude-science/admin-controls#network-allowlist)).

1616

claude-science/connectors-and-skills Changed · +1 / -1 lines

from line 6

77## Featured connectors

9Claude Science includes Featured connectors to public life-sciences databases. They're on by default and can be turned off individually in **Settings > Connectors**. On Team and Enterprise plans, your organization can also turn individual Featured connectors off for everyone, and in organizations with HIPAA compliance enabled they start off until an admin turns them on. A connector your organization has off stays listed, grayed, and Claude can't use it (see [Featured connectors and skills](/docs/claude-science/admin-controls#featured-connectors-and-skills)). Featured connectors are read-only and don't require an account or key. Some underlying databases have non-commercial or attribution terms; review each source's license for your use case.

9Claude Science includes Featured connectors to public research databases, most of them in the life sciences. They're on by default and can be turned off individually in **Settings > Connectors**. On Team and Enterprise plans, your organization can also turn individual Featured connectors off for everyone, and in organizations with HIPAA compliance enabled they start off until an admin turns them on. A connector your organization has off stays listed, grayed, and Claude can't use it (see [Featured connectors and skills](/docs/claude-science/admin-controls#featured-connectors-and-skills)). Featured connectors are read-only and don't require an account or key, except that the Literature Graph needs a free OpenAlex API key to search OpenAlex (see [Available credentials](/docs/claude-science/literature-access#available-credentials)). Some underlying databases have non-commercial or attribution terms; review each source's license for your use case.

1010

1111| Connector | Sources |

1212| - | - |

claude-science/corporate-networks Changed · +1 / -1 lines

from line 134

134134

135135How the variables reach the app depends on the operating system:

136136

137* On macOS, the menu-bar app reads `~/.claude-science/env`, a file of `KEY=VALUE` lines (`export KEY=VALUE` also works), when it launches. Put the three variables there, then quit and reopen the app; an app started from the Dock or Finder does not see variables exported in a terminal. The file's `NO_PROXY` entries merge with the other sources rather than replacing them.

137* On macOS, the Claude Science app reads a file named `env` in its data folder (`~/.claude-science/env` unless you moved the data folder) when it launches. The file holds `KEY=VALUE` lines (`export KEY=VALUE` also works). Put the three variables there, then quit and reopen the app; an app started from the Dock or Finder does not see variables exported in a terminal. The file's `NO_PROXY` entries merge with the other sources rather than replacing them.

138138* On Windows, the app reads the variables from the user's environment when it starts, so set them as user environment variables, then quit Claude Science from its notification-area icon and open it again; variables typed into an open Command Prompt or PowerShell window do not reach an app started from the Start menu. Because Claude Science already follows Windows proxy settings, most PCs need no variables, and `[network] proxy` in `config.toml` is the form to deploy.

139139* On Linux, export the variables in the shell or service unit that starts `claude-science serve`. The `env` file is read only by the macOS app.

140140

claude-science/monitor-usage Changed · +2 / -2 lines

from line 1

11# Monitor Claude Science usage

3> Claude Science usage counts against each member's standard weekly quota and uses the same seat as the rest of claude.ai.

3> Claude Science uses the same seat as the rest of claude.ai. Track its adoption and usage in Analytics and through the Admin API.

5Claude Science usage counts against each member's standard weekly quota and uses the same seat as the rest of claude.ai. You can track adoption in Analytics and through the Admin API.

5Claude Science uses the same seat as the rest of claude.ai, and its usage counts the same way as Claude Code and Cowork usage (see [Plans and usage](/docs/claude-science/overview#plans-and-usage)). You can track adoption in Analytics and through the Admin API.

77## Analytics