What this read moved
1–13 of 13claude-science/admin-controls Changed · +24 / -17 lines
### Previously saved Claude Science work
from line 1
11# Admin controls
22
3> Organization settings for Claude Science on Team and Enterprise plans (Featured connectors and skills, custom connectors and skills, the network allowlist, package mirror, SSH hosts, Modal, scientific model endpoints, and memory) and which other claude.ai admin controls apply to the app.
3> Organization settings for Claude Science on Team and Enterprise plans (Featured connectors and skills, custom connectors and skills, access to Claude Science work previously saved on the computer, the network allowlist, package mirror, SSH hosts, Modal, scientific model endpoints, and memory) and which other claude.ai admin controls apply to the app.
44
5Members sign in to Claude Science with their Claude account, so your identity and billing controls apply automatically. Because the app stores conversations on each member's computer, most of the data-handling controls Anthropic provides don't reach that data today. [Organization settings](#organization-settings) describes the controls on the claude.ai **Organization settings** > **Claude Science** page itself, which govern the connectors, skills, compute, network access, and memory that members can use in the Claude Science app. [How other admin settings apply to Claude Science](#how-other-admin-settings-apply-to-claude-science) lists every other claude.ai admin setting and whether it applies to Claude Science today. Status values describe Claude Science specifically; other Claude products may differ.
5Members sign in to Claude Science with their Claude account, so your identity and billing controls apply automatically. Because the app stores conversations on each member's computer, most of the data-handling controls Anthropic provides don't reach that data today. [Organization settings](#organization-settings) describes the controls on the claude.ai **Organization settings** > **Claude Science** page itself, which govern the connectors, skills, compute, network access, and memory that members can use in the Claude Science app, and whether members can access previously saved Claude Science work. [How other admin settings apply to Claude Science](#how-other-admin-settings-apply-to-claude-science) lists every other claude.ai admin setting and whether it applies to Claude Science today. Status values describe Claude Science specifically; other Claude products may differ.
66
77## Organization settings
88
from line 12
1212
1313Each control starts at a default that depends on your plan and on whether HIPAA compliance is enabled for your organization. The page always shows the value in force for your organization.
1414
15| Control | Default for Team | Default for Enterprise¹ |
16| ----------------------------------------------------------- | ------------------------------ | ------------------------------ |
17| Featured connectors and Featured skills | All on | All on |
18| Allow custom connectors | On | Off |
19| Allow custom skills | On | On |
20| Manage network allowlist | Off (members manage their own) | Off (members manage their own) |
21| Organization package mirror | Not set | Not set |
22| Allow members to connect SSH hosts | On | On |
23| Allow members to connect to Modal | On | Off |
24| Show scientific model endpoint providers on the Compute tab | On | On |
25| Turn on memory for your team | On | On |
15| Control | Default for Team | Default for Enterprise¹ |
16| ------------------------------------------------------------------------------ | ------------------------------ | ------------------------------ |
17| Featured connectors and Featured skills | All on | All on |
18| Allow custom connectors | On | Off |
19| Allow custom skills | On | On |
20| Allow members to access Claude Science work previously saved on their computer | On | Off |
21| Manage network allowlist | Off (members manage their own) | Off (members manage their own) |
22| Organization package mirror | Not set | Not set |
23| Allow members to connect SSH hosts | On | On |
24| Allow members to connect to Modal | On | Off |
25| Show scientific model endpoint providers on the Compute tab | On | On |
26| Turn on memory for your team | On | On |
2627
27¹ For HIPAA-eligible organizations, note that Claude Science (beta) is not covered under your Business Associate Agreement (BAA) and should not be used with protected health information (PHI). Administrators who enable Claude Science are responsible for ensuring their workforce uses it in compliance with applicable legal obligations. Featured and custom connectors, SSH hosts, Modal, scientific model endpoints, and memory are all off by default for HIPAA-eligible organizations.
28¹ For HIPAA-eligible organizations, note that Claude Science (beta) is not covered under your Business Associate Agreement (BAA) and should not be used with protected health information (PHI). Administrators who enable Claude Science are responsible for ensuring their workforce uses it in compliance with applicable legal obligations. Featured and custom connectors, SSH hosts, Modal, scientific model endpoints, memory, and access to previously saved Claude Science work are all off by default for HIPAA-eligible organizations.
2829
2930### How changes reach members
3031
from line 33
3233
3334The settings apply to members running version 0.1.41 or later of the Claude Science app. A member still on an earlier version isn't governed by these settings until the member updates (see [Required updates](/docs/claude-science/manage-on-devices#required-updates)). For Team and Enterprise organizations, Claude Science enforces a minimum version of 0.1.41. A member on an older version sees a notice that the version is no longer supported, with an **Update now** button. If the update doesn't complete after a second try, the member can install the current version from the [Claude Science download page](https://claude.com/product/claude-science) (on Linux, rerun the install command in [Get started](/docs/claude-science/get-started#install)); projects and settings on the computer are kept.
3435
35Each member's app also has to reach claude.ai regularly to confirm these settings. If an app can't reach claude.ai for 72 hours, it pauses memory, custom connectors, SSH hosts, Modal, model endpoints, and adding custom skills until it reconnects, and keeps applying the network allowlist, package mirror, and Featured connector and skill choices it last received.
36Each member's app also has to reach claude.ai regularly to confirm these settings. If an app can't reach claude.ai for 72 hours, it pauses memory, custom connectors, SSH hosts, Modal, model endpoints, adding custom skills, and accessing previously saved Claude Science work until it reconnects, and keeps applying the network allowlist, package mirror, and Featured connector and skill choices it last received.
3637
3738Turning a control off doesn't delete anything on the members' computers. What members set up under that control (custom connectors, SSH hosts, their Modal connection, saved memories, and their own choices) stays on their computer, and that feature cannot be used inside the Claude Science app while the control is off. The setting shows grayed out in the app with a note that an admin turned it off, and everything works again as before if you turn the control back on. A control that is off by your plan's default instead shows a note that an admin can turn it on. When the **Allow custom skills** switch is off, skills a member added earlier keep working (see [Custom skills](#custom-skills)).
3839
from line 72
7172To let members manage their own skills, host them in a GitHub repository. Put one `skills/<name>/SKILL.md` folder per skill in the repository and share the link. Members import them in the Claude Science app under **Settings** > **Skills** > **Add skill** > **Import from GitHub**. Claude Science records the commit each skill came from. **Check for updates** flags skills that are behind the repository's latest commit; each member chooses when to import again. Private repositories work after a member adds a GitHub token in the Claude Science app under **Settings** > **Credentials**.
7273
7374To stop members from adding their own skills, turn off the **Allow custom skills** switch on the **Organization settings** > **Claude Science** page (see [Custom skills](#custom-skills)).
75
76### Previously saved Claude Science work
77
78A member who used Claude Science under another sign-in on the same computer (for example, a personal plan before joining your organization) can access the projects, sessions, and artifacts from that sign-in and move it into the app's folder for your organization on that computer (see [Access work from another sign-in on your computer](/docs/claude-science/multiple-computers#access-work-from-another-sign-in-on-your-computer)). The **Allow members to access Claude Science work previously saved on their computer** switch decides whether the app offers this access. It's on by default for Team organizations and off by default for Enterprise organizations, and organizations with HIPAA compliance enabled can't turn it on.
79
80The access happens on the member's computer and uploads nothing. Claude Science work the app accesses will follow your organization's settings from then on. Content your organization doesn't allow isn't copied or moved and stays in its original folder, and credentials such as API keys and connector sign-ins are never copied or moved. When the switch is off, the app doesn't offer the access, and its **Import work on this computer** setting is grayed out with a note that it's off for your organization.
7481
7582### Network allowlist
7683
claude-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<Update label="0.1.49" description="September 16, 2026">
6 * Saved credentials now reach Claude's code only when it asks for them and you approve. They're no longer present in every cell
7 * Access Claude Science work saved on your computer from other sign-ins, from Home or Settings. Admins control it on Team and Enterprise plans
8 * Claude can send you a short message, such as a link to a file, while it keeps working on a task
9 * Mac: Apple silicon Macs with the Intel version installed can now update, and then run natively
10 * Mac: if Claude's tools can't start after an Xcode update, the error now says how to accept the Xcode license
11 * You can comment on and bookmark the short summaries of Claude's progress notes
12 * Sessions moved to a model with a smaller context window keep going instead of failing
13 * Turning Auto-review off now applies to agents that are already running; turning it back on resumes their reviews
14 * Settings > Connectors shows "Not set" for tools without a permission, and saves "Ask each time"
15 * Windows: `claude-science install` now reports the step that failed instead of reporting success
16 * Faster search of a long session's history; clearer wording in model settings
17</Update>
18
519<Update label="0.1.48" description="September 14, 2026">
620 * On Windows, environment setup now handles user folders with accented or non-Latin names, tries again if Windows briefly refuses to start the environment installer, and no longer needs the Microsoft Visual C++ Redistributable
721 * The app now warns you a few days before your sign-in expires and offers a "Sign in again" button
claude-science/literature-access Changed · +8 / -8 lines
from line 14
1414
1515Each credential in the **Literature access (journals, etc.)** form is optional and independent.
1616
17| Credential | Effect |
18| ---------------------------------------------- | ------------------------------------------------------------- |
19| **Elsevier API key** + institutional token | Enables the Elsevier route (subscription still required) |
20| **Springer Nature API key** | Enables the Springer Nature route |
21| **Semantic Scholar API key** | Speeds the Semantic Scholar step |
22| **NCBI API key** | Raises the PubMed rate limit from 3 to 10 requests per second |
23| **CORE API key** | Gives skills access to the CORE open-access aggregator |
24| Institutional **EZproxy URL** + session cookie | Retries publisher links through your library |
17| Credential | Effect |
18| ---------------------------------------------- | ----------------------------------------------------------------------------------- |
19| **Elsevier API key** + institutional token | Enables the Elsevier route (subscription still required) |
20| **Springer Nature API key** | Enables the Springer Nature route |
21| **Semantic Scholar API key** | Speeds the Semantic Scholar step |
22| **NCBI API key** | Raises the PubMed rate limit from 3 to 10 requests per second |
23| **CORE API key** | Saved with your other literature keys. Claude's full-text retrieval doesn't use it. |
24| Institutional **EZproxy URL** + session cookie | Retries publisher links through your library |
2525
2626OpenAlex has its own entry in the same **Services** list: add a free **OpenAlex API key** there (create one on the [OpenAlex API settings page](https://openalex.org/settings/api)). OpenAlex requires a key on every request, so OpenAlex-backed literature search needs one configured.
2727
claude-science/multiple-computers Changed · +8 / -2 lines
## Access work from another sign-in on your computer
from line 1
11# Use Claude Science on more than one computer
22
3> What to expect when you sign in on another computer.
3> What to expect when you sign in on another computer, or under another sign-in on the same computer.
44
5Claude Science runs on your own computer by design, and your projects, artifacts, and conversation history live there with it, under your control rather than in your Claude account. Each computer you install it on keeps its own projects, so a new or different computer starts fresh when you sign in, and your earlier work stays on the first computer.
5Claude Science runs on your own computer by design, and your projects, artifacts, and conversation history live there with it, under your control rather than in your Claude account. Each computer you install it on keeps its own projects, so a new or different computer starts fresh when you sign in, and your earlier work stays on the first computer. On one computer, Claude Science also keeps the work from each sign-in in its own folder. Signing in to a different organization or personal account starts fresh too, and you can access the earlier work (see [Access work from another sign-in on your computer](#access-work-from-another-sign-in-on-your-computer)).
66
77## Your work stays on your computer
88
from line 13
1313Because the only copy is on your computer, include the app's data folder in your regular backups. In the app, **Settings > Storage > Data location** shows where the folder is.
1414
1515To take a single result to another computer, choose **Download** from the artifact's menu. A file saved with **Export session** is for technical support and troubleshooting, and can't be loaded into Claude Science on another computer. To reach the same projects from several computers instead, you can install Claude Science once on a Linux server you control and connect to it through an SSH tunnel from the browser on each computer. See [Run on a remote Linux server](/docs/claude-science/run-on-remote-linux-server).
16
17## Access work from another sign-in on your computer
18
19Claude Science keeps the work from each sign-in in its own folder on your computer. When you sign in to a different organization or personal account on that computer (for example, a Team plan after a personal plan), a banner at the top of the home screen offers to import the earlier work. Select the **Review** button on the banner, select the folders to access, choose **Copy** (the original folder keeps the work too) or **Move** (what's accessed is then removed from the original folder), and select **Import**. To access later instead, select **Review** next to **Import work on this computer** under **Settings** > **General** > **Account**.
20
21The access happens entirely on your computer and uploads nothing. Credentials such as API keys and connector sign-ins aren't copied or moved and stay in their original folder. On Team and Enterprise plans, your admin controls whether the app offers importing (it's off by default on Enterprise plans). Content your organization doesn't allow, such as memory, isn't copied or moved and stays in its original folder (see [Previously saved Claude Science work](/docs/claude-science/admin-controls#previously-saved-claude-science-work)).
1622
claude-science/cloud-storage Changed · +2 / -2 lines
from line 6
66
77In **Settings > Credentials**, choose **AWS**, **Google Cloud**, or **Microsoft Azure**, then Connect. Provide the credential (access key, service-account JSON, HMAC key, service principal, or connection string) and list the bucket names (AWS, GCP) or **Blob containers** (Azure) this credential covers. S3-compatible stores use the AWS form with the **S3-compatible endpoint** field; you'll need to allowlist that endpoint host separately.
88
9Listing a bucket adds its address to the sandbox network allowlist so code can reach it without a per-call card. Access within the bucket is still limited to the credential's permissions. Credentials are encrypted on your computer and sent only to the provider they belong to.
9Listing a bucket adds its address to the sandbox network allowlist so code can reach it without a network permission card. Access within the bucket is still limited to the credential's permissions. Credentials are encrypted on your computer and sent only to the provider they belong to.
1010
1111Claude reads and writes objects with ordinary code using the provider's Python library (`boto3`, Azure SDK). **Settings > Storage** lists connected credentials and lets you browse and import objects (up to 100 GB) or export artifacts.
1212
from line 15
1515</Note>
1616
1717<Warning>
18 Any code Claude writes can use credentials you add here. If a bucket should never be reachable from an analysis session, don't add its credential.
18 Code that Claude writes can use a credential you add here only after you approve a **Credentials** card that names it. By default the approval lasts for the conversation. If a bucket should never be reachable from an analysis session, don't add its credential.
1919</Warning>
2020
claude-science/core-concepts Changed · +1 / -0 lines
from line 28
2828| Run code | Run Python code? / Run a shell command? / Install packages? | Once or Always |
2929| Reach a network host | Connect to `<target>`? | Persists until revoked |
3030| Use a connector tool | Use `<tool>`? | Once, This conversation, This project, or Global |
31| Use a saved credential | Credentials | Once, This conversation, This project, or Global |
3132| Run a remote job | Run this job on `<host>`? / Start a Modal job? | Once, This conversation, This project, or Global |
3233
3334All standing grants are listed in Settings > Permissions and can be revoked there.
claude-science/custom-connectors Changed · +1 / -1 lines
from line 8
88
99On Team and Enterprise plans, you can add and use custom connectors only if your organization allows them. When it doesn't, the **Remote** and **Local command** options under **Add connector** are grayed with a note that custom connectors are disabled by your admin. Custom connectors you added earlier stay listed and grayed, Claude can't use them, and they work again if your organization turns custom connectors back on. See [Custom connectors](/docs/claude-science/admin-controls#custom-connectors) in the admin controls.
1010
11Every tool from a custom connector starts at **Ask each time**. On the connector's page, set individual tools to **Always allow** or **Block** under **Tools**, or turn on Skip approvals for the whole connector.
11Every tool from a custom connector starts as **Not set**, and Claude asks before using it. On the connector's page, set individual tools to **Always allow**, **Ask each time**, or **Block** under **Tools**, or turn on Skip approvals for the whole connector.
1212
1313<Warning>
1414 Skip approvals disables the per-call card for every tool on that connector. Only use connectors from developers you trust.
claude-science/enable-claude-science Changed · +2 / -2 lines
from line 2
22
33> Claude Science is a desktop app for scientific research.
44
5Claude Science is a desktop app for scientific research. It's off by default for Team and Enterprise organizations. Turning it on in **Organization settings** > **Claude Science** opens a short dialog that covers who gets access and which connectors to turn on. You can change any of it later on the same page, which also holds the other [organization settings](/docs/claude-science/admin-controls#organization-settings) for Claude Science: which connectors, skills, compute, network access, and memory members can use.
5Claude Science is a desktop app for scientific research. It's off by default for Team and Enterprise organizations. Turning it on in **Organization settings** > **Claude Science** opens a short dialog that covers who gets access and which connectors to turn on. You can change any of it later on the same page, which also holds the other [organization settings](/docs/claude-science/admin-controls#organization-settings) for Claude Science: which connectors, skills, compute, network access, and memory members can use, and whether members can access previously saved Claude Science work.
66
77## Availability
88
from line 65
6565
6666Organizations with HIPAA compliance enabled can turn on Claude Science during the beta, but usage isn't covered under your BAA, so keep protected health information out of it. The **Turn on Claude Science** dialog opens with a step that says so. In its connectors step the local connectors start off, and you can turn on the ones you have reviewed. The Anthropic-hosted and directory connectors in that step are read-only because the dialog's quick-enable path doesn't include the per-connector HIPAA attestation, so add those from **Organization settings** > **Connectors** instead, where the attestation is required.
6767
68These organizations also start with stricter organization settings. Featured connectors and skills, SSH hosts, Modal, model endpoints, and memory are off until you turn them on (including for members who were already using them), custom connectors can't be turned on, and the organization always manages the network allowlist. See [Defaults by plan](/docs/claude-science/admin-controls#defaults-by-plan).
68These organizations also start with stricter organization settings. Featured connectors and skills, SSH hosts, Modal, model endpoints, and memory are off until you turn them on (including for members who were already using them), custom connectors and access to previously saved Claude Science work can't be turned on, and the organization always manages the network allowlist. See [Defaults by plan](/docs/claude-science/admin-controls#defaults-by-plan).
6969
7070## Turn off Claude Science
7171
claude-science/get-started Changed · +2 / -0 lines
from line 83
8383
8484* 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.
8585* 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.
86* 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.
8687* 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.
8788* 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)).
8889* 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).
8990* 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).
91* 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 **Import 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).
9092* 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.
9193
claude-science/glossary Changed · +1 / -1 lines
from line 28
2828
2929**Network allowlist**: the list of every outside host that sandboxed code may reach, kept under Settings or, on Team and Enterprise plans, managed by your organization.
3030
31**Permission card**: the card that replaces the message box when Claude needs your permission for running code, running a job, accessing a network host, a folder, a connector tool, or re-configuring Claude Science; you allow or deny it.
31**Permission card**: the card that replaces the message box when Claude needs your permission for running code, running a job, accessing a network host, a folder, a connector tool, a saved credential, or re-configuring Claude Science; you allow or deny it.
3232
3333**Provenance (the artifact record)**: the panel behind every artifact version showing the code, cells, conversation, environment, and findings that produced it.
3434
claude-science/how-claude-science-works-with-your-data Changed · +1 / -1 lines
from line 44
4444
4545## Controls available to your organization
4646
47* **Organization settings** for connectors, skills, the sandbox network allowlist, SSH hosts, Modal, model endpoints, and memory (see [Admin controls](/docs/claude-science/admin-controls)). There is no organization setting for web search, dictation, or telemetry.
47* **Organization settings** for connectors, skills, the sandbox network allowlist, SSH hosts, Modal, model endpoints, memory, and access to previously saved Claude Science work (see [Admin controls](/docs/claude-science/admin-controls)). There is no organization setting for web search, dictation, or telemetry.
4848* **US-only inference** (usage-based Enterprise plans) runs model inference for Claude Science requests in the United States, as for your other Claude apps (see [Enable US-only inference](https://support.claude.com/en/articles/15422948-enable-us-only-inference-for-your-organization)).
4949* **Device configuration** turns off telemetry, error reports, and feedback and relocates the local data folder (see [Manage Claude Science on devices](/docs/claude-science/manage-on-devices)).
5050* **Running Claude Science next to your data**, on a Linux server or virtual machine you control, keeps datasets on your infrastructure, apart from what Claude reads into the conversation, while Claude's inference runs on Anthropic's service (see [Run on a remote Linux server](/docs/claude-science/run-on-remote-linux-server)).
claude-science/network-requirements Changed · +2 / -2 lines
from line 71
7171| NCBI and NIH | `*.ncbi.nlm.nih.gov`, `*.nih.gov`, `cactus.nci.nih.gov` |
7272| Genomics and biology | `rest.ensembl.org`, `grch37.rest.ensembl.org`, `*.ensembl.org`, `reactome.org`, `*.reactome.org`, `rest.kegg.jp`, `*.kegg.jp`, `cellguide.cellxgene.cziscience.com`, `gnomad.broadinstitute.org`, `gtexportal.org`, `jaspar.elixir.no`, `www.encodeproject.org`, `mygene.info`, `rfam.org`, `www.cbioportal.org`, `sparql.rhea-db.org`, `bindingdb.org`, `www.bindingdb.org`, `r12.finngen.fi`, `pheweb.jp`, `api.genome.ucsc.edu`, `unibind.uio.no` |
7373| Proteomics | `rest.uniprot.org`, `*.uniprot.org`, `string-db.org`, `*.string-db.org`, `*.ebi.ac.uk`, `search.foldseek.com`, `rcsb.org`, `*.rcsb.org`, `*.proteinatlas.org` |
74| Literature and citations | `api.semanticscholar.org`, `api.biorxiv.org`, `www.biorxiv.org`, `api.crossref.org`, `doi.org`, `api.openalex.org`, `arxiv.org`, `*.arxiv.org` |
75| Clinical and pharma | `api.fda.gov`, `clinicaltrials.gov`, `*.clinicaltrials.gov`, `api.clinpgx.org`, `api.platform.opentargets.org`, `cancer.sanger.ac.uk`, `actionability.clinicalgenome.org`, `search.clinicalgenome.org`, `erepo.genome.network`, `civicdb.org`, `api.grants.gov`, `www.antibodyregistry.org`, `cartblanche22.docking.org`, `files.docking.org` |
74| Literature and citations | `api.semanticscholar.org`, `api.biorxiv.org`, `www.biorxiv.org`, `api.crossref.org`, `doi.org`, `api.openalex.org`, `arxiv.org`, `*.arxiv.org`, `api.grants.gov` |
75| Clinical and pharma | `api.fda.gov`, `clinicaltrials.gov`, `*.clinicaltrials.gov`, `api.clinpgx.org`, `api.platform.opentargets.org`, `cancer.sanger.ac.uk`, `actionability.clinicalgenome.org`, `search.clinicalgenome.org`, `erepo.genome.network`, `civicdb.org`, `www.antibodyregistry.org`, `cartblanche22.docking.org`, `files.docking.org` |
7676
7777### Optional compute integrations
7878
claude-science/the-reviewer Changed · +1 / -1 lines
from line 25
2525
2626## Controls
2727
28Auto-review is a per-session toggle in the session settings menu. It starts on for Max, Team, and Enterprise plans and off for the Pro plan. Reviews run against your plan's usage.
28Auto-review is a per-session toggle in the session settings menu. It starts on for Max, Team, and Enterprise plans and off for the Pro plan. If you turn Auto-review off while Claude is working, no new automatic reviews start, including for delegated work that is already running. Reviews that have already started or are waiting to start still finish. Turning Auto-review back on resumes automatic reviews, starting with the work done while it was off. Reviews run against your plan's usage.
2929