What this read moved
1–4 of 4claude-science/safeguards New page · 31 lines, new page
# Safeguards ## When safeguards flag a message ## Switch models automatically ## Life Sciences Verification Program (beta) ## Choose a use case
A whole new page. There's nothing to diff it against, so here is what it says.
# Safeguards > What happens when a model's safeguards flag a message, how to switch models automatically, and how to choose a use case under the Life Sciences Verification Program (beta). Claude models include safeguards that can flag a message and stop the response. Some are intentionally broad and can flag legitimate coding, cybersecurity, and biology work. See [Our Approach to User Safety](https://support.claude.com/en/articles/8106465-our-approach-to-user-safety) for more about these safeguards. ## When safeguards flag a message When a model's safeguards flag a message, Claude Science pauses the session and shows a **Chat paused** card above the composer. If another model can continue, select **Retry with `<model>`** to retry on the model the card names. That model has its own safeguards. The session stays on it until you choose a different model in the composer. ## Switch models automatically To have Claude Science retry without stopping at the **Chat paused** card, turn on the **Automatically switch models when a message is flagged** switch under **Settings** > **General** > **Model**. You can also select it on the card before you retry. Claude Science then retries a flagged message on another model right away and shows a notice that names the model it switched to. If no other model can continue, or after several automatic switches in one session, you see the **Chat paused** card instead. Automatic switching is off by default and applies to every session on this computer. ## Life Sciences Verification Program (beta) Under Anthropic's Life Sciences Verification Program (beta), verified organizations on Team and Enterprise plans can use Claude models with fewer life sciences restrictions. Protections against the most serious misuse stay in place, and safeguards can still flag a message. [What is the Life Sciences Verification Program?](https://support.claude.com/en/articles/16975617) has the details, including which models it applies to and how an organization applies. ## Choose a use case If you have access through the Life Sciences Verification Program (beta), your organization specified one or more approved research use cases. Claude Science sends a session's use case with the requests it makes for that session, so Claude's safeguards can apply the access approved for that work. Anthropic also monitors program usage against the scope your organization shared when it applied. See [What is the Life Sciences Verification Program?](https://support.claude.com/en/articles/16975617) for data retention and safety review. With one use case, Claude Science applies it to every session. With more than one use case, you choose one for each session: * Claude Science asks you to choose the one that matches your work when you first send a message in a session, unless you've set a default. Everyday tasks like writing or coding are allowed with any use case. * To switch during a session, open the model picker in the composer and select **Use case**. * To set a default on this computer, select **Set as default** when Claude Science offers it, or choose one from the **Default use case** menu under **Settings** > **General** > **Model**. The use case controls need version 0.1.49 or later of the Claude Science app. If you're up to date and don't see a use case, ask your organization's admin.
claude-science/changelog Changed · +1 / -0 lines
from line 3
33> Release notes for Claude Science, including new features, improvements, and bug fixes by version.
44
55<Update label="0.1.49" description="September 16, 2026">
6 * If your organization is in Anthropic's Life Sciences Verification Program (beta), you can now [choose a use case](/docs/claude-science/safeguards#choose-a-use-case) for your sessions
67 * Saved credentials now reach Claude's code only when it asks for them and you approve. They're no longer present in every cell
78 * Access Claude Science work saved on your computer from other sign-ins, from Home or Settings. Admins control it on Team and Enterprise plans
89 * Claude can send you a short message, such as a link to a file, while it keeps working on a task
claude-science/glossary Changed · +2 / -0 lines
from line 46
4646
4747**SSH host**: a remote machine (server, cluster node, or a job submission host) added by its SSH name, that Claude can run jobs on, or dispatch jobs from.
4848
49**[Use case](/docs/claude-science/safeguards#choose-a-use-case)**: a research purpose that Anthropic has approved for your organization under the Life Sciences Verification Program (beta); if you have more than one, you choose which one a session uses.
50
4951**Version**: one immutable save of an artifact; saving again adds a new version on top instead of overwriting.
5052
5153**Workspace**: the per-session folder on disk where Claude's code reads and writes files before they are saved as artifacts.
third-party/claude-desktop/browser Changed · +1 / -1 lines
from line 2
22
33> Configuring Claude in Chrome and the built-in browser in Cowork and Code for Claude Desktop 3P
44
5In Claude Desktop on third-party (3P), Claude can work with web pages in Cowork and Code sessions through Claude in Chrome or through the built-in browser. [Claude in Chrome](#claude-in-chrome) lets Claude work in the user's own Google Chrome or Microsoft Edge and is available to organizations managed from the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console). The [built-in browser](#built-in-browser) is a pane inside Claude Desktop that any deployment can turn on with the [`builtinBrowserEnabled`](/docs/third-party/claude-desktop/configuration#builtinbrowserenabled) key, and three related keys control which sites Claude can open in it.
5In Claude Desktop on third-party (3P), Claude can work with web pages in Cowork and Code sessions through Claude in Chrome or through the built-in browser. [Claude in Chrome](#claude-in-chrome) lets Claude work in the user's own Google Chrome or Microsoft Edge and is available to organizations managed from the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console). The [built-in browser](#built-in-browser) is a pane inside Claude Desktop that any deployment can turn on with the [`builtinBrowserEnabled`](/docs/third-party/claude-desktop/configuration#builtinbrowserenabled) key, and three related keys control which sites Claude can open in it. This page explains how to configure both for Claude Desktop on 3P and how they work there. To learn how to use them, see [Use the built-in browser in Claude Cowork](https://support.claude.com/en/articles/16607400-use-the-built-in-browser-in-claude-cowork) and [Use Claude Code with Chrome](https://code.claude.com/docs/en/chrome).
66
77## Claude in Chrome
88