Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Documentation
One capture · claude-docs

One read of Claude Documentationclaude-docs-20261110T173709Z

8 pages moved out of 286 read.

Pages moved 8 significant first
Pages read 286 in this capture
Captured 17:37 UTC
Corpus hash fb75cf4c1123 corpus-hash

What this read moved

1-8 of 8

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

## Git and GitHub ### SSH is off inside Claude Science’s sandbox

from line 1
11# Troubleshoot Claude Science
22 
3> Fix errors you see while using Claude Science: being signed out, capacity retries, Agent Failed, environment setup, connectors, dictation, and updates.
3> Fix errors you see while using Claude Science: being signed out, capacity retries, Agent Failed, environment setup, connectors, git, dictation, and updates.
44 
55This page covers error messages that Claude Science shows while you work. Other problems have their own troubleshooting sections:
66 
from line 59
5959### failed to load 5 times in a row — automatic retries are paused
6060 
6161This 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.
62 
63## Git and GitHub
64 
65The messages in this section appear when Claude runs git in the sandbox on a Mac or Linux.
66 
67### SSH is off inside Claude Science’s sandbox
68 
69By design, SSH is off in the [sandbox](https://claude.com/docs/claude-science/core-concepts.md#sandbox). For `github.com`, Claude can push over HTTPS with a GitHub token you save. With the token, a `[email protected]:` remote works as it is. If your organization [manages the network allowlist](https://claude.com/docs/claude-science/admin-controls.md#network-allowlist), ask an admin to check that the [GitHub domains](https://claude.com/docs/claude-science/network-requirements.md#package-management-domains) are on.
70 
71Check these limits before you push:
72 
73* **A host other than `github.com`**: Claude Science has no built-in sign-in for it
74* **A Git LFS repository**: Claude's commits can store LFS files as ordinary files, and a push from the sandbox may not upload them
75* **On Linux**: folders such as `.devcontainer` look empty in the sandbox, so git shows their files as deleted. Don't commit those deletions.
76 
77For a `github.com` repository that doesn't use Git LFS, follow these steps:
78 
791. Go to **Settings > Credentials**, select **Connect** next to **GitHub**, paste a personal access token that can write to the repository, and select **Save**. To limit the token to one repository, use a [fine-grained token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) for it alone, with **Contents** set to **Read and write**. If the button says **Disconnect**, a token is already saved.
80 
812. Ask Claude:
82 
83 ```text Prompt wrap theme={null}
84 Push my commits with a shell command in the default python environment, using my saved GitHub credential.
85 ```
86 
873. Select **Allow for this conversation** on the **Run a shell command?** [permission card](https://claude.com/docs/claude-science/core-concepts.md#permission-cards) if it appears, then on the **Credentials** card.
88 
89 By default, the approval lasts for the conversation, and commands Claude runs there can use the token without asking again. To revoke the approval, go to **Settings > Permissions**, hold the pointer over each **GitHub** row under **Credentials**, and select **Revoke** (the ×).
90 
91Check GitHub for your commits, because git can print an error even when the push worked.
92 
93These steps also apply to `could not read Username for 'https://github.com'`, and to the `/bin/false` error git printed before Claude Science 0.1.61.
6294 
6395## Dictation
6496 

claude-tag/admins/attach-to-scope Changed · +1 / -4 lines

from line 155
155155 
156156Channel members reach the same field for the channel scope through the **Configure** page, linked in the footer of any Claude reply in the channel, without going through admin settings. Both entry points write the same instructions, so a change from either place is visible in the other.
157157 
158To let a central team write a channel's instructions from its own Slack channel, see [Manage a channel's instructions from another channel](https://claude.com/docs/claude-tag/admins/managed-by.md).
159 
160158#### Instruction format
161159 
162160The field is plain text, inserted as written; there is no include or template syntax, and `{{include:...}}` is passed through literally. To give Claude a repository's `CLAUDE.md`, [grant the repository](https://claude.com/docs/claude-tag/admins/configure-github.md#grant-repository-access) and name it in the request; its `CLAUDE.md` loads after the clone completes.
from line 161
163161 
164162#### What Claude reads in a channel
165163 
166What Claude reads in a channel is the concatenated custom instructions of its scope chain, the instructions of each bundle that applies there, the channel's [managed instructions](https://claude.com/docs/claude-tag/admins/managed-by.md#how-managed-instructions-load) if another channel manages it, and the `CLAUDE.md` of any repository it clones. Projects in claude.ai don't apply here; Claude doesn't read a Project's instructions or knowledge in Slack, and a channel can't be pointed at a Project.
164What Claude reads in a channel is the concatenated custom instructions of its scope chain, the instructions of each bundle that applies there, and the `CLAUDE.md` of any repository it clones. Projects in claude.ai don't apply here; Claude doesn't read a Project's instructions or knowledge in Slack, and a channel can't be pointed at a Project.
167165 
168166#### When a new instruction applies
169167 
from line 175
177175| :- | :- | :- |
178176| Custom instructions | Owner for any scope; [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) for workspace and channel scopes; channel members and [channel managers](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) for the channel scope, unless members are [restricted](#restrict-who-can-set-channel-instructions) | The instructions field on a scope's page in admin settings, or the **Configure** link in any reply footer for the channel scope |
179177| Bundle instructions | An Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) | The **Instructions** section of the bundle's page. They apply wherever the bundle applies |
180| Managed instructions | Full workspace members in one of the channel's [managing channels](https://claude.com/docs/claude-tag/admins/managed-by.md), which an Owner or a Claude Tag admin selects under **Managed by** on the channel's Configure page | By asking Claude in the managing channel and confirming the card it posts |
181178| Channel memory | Anyone in the channel | By telling Claude to remember |
182179| Task prompt | The requester | The message itself |
183180 

claude-tag/admins/managed-by Page removed · 211 lines, page removed

# Manage a channel's instructions from another channel ## When to use Managed by ## Channel requirements for Managed by ## Choose the managing channels ## Write or update managed instructions ### Correct Claude privately from a managing channel ## How managed instructions load ## Public and private channels ## Limits of Managed by as a control ## Troubleshoot Managed by ## Related resources

The page is gone upstream. What it last said is kept here.

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

from line 157
157157 
158158Until you change the list, members use Claude Science's Featured list, including domains added in later versions of Claude Science. Once you change it, the list is saved exactly as you left it, so a domain added in a later version stays off until you turn it on. **Reset** returns to the Featured list and removes your custom domains, for all members.
159159 
160You can also turn off the **Package management** domains (PyPI, conda, CRAN and Bioconductor, npm, and GitHub), with limits. The PyPI and conda domains can be turned off only while the [organization package mirror](#organization-package-mirror) covers them. Turning the CRAN and Bioconductor, npm, or GitHub domains off means members can't install packages from them, and the page asks you to confirm. The domains the sandbox always blocks (see [Network requirements](https://claude.com/docs/claude-science/network-requirements.md#domains-the-sandbox-always-blocks)) stay blocked whichever list is in force.
160You can also turn off the **Package management** domains (PyPI, conda, CRAN and Bioconductor, npm, and GitHub), with limits. The PyPI and conda domains can be turned off only while the [organization package mirror](#organization-package-mirror) covers them. Turning the CRAN and Bioconductor, npm, or GitHub domains off means members can't install packages from them, and the page asks you to confirm. With the GitHub domains off, git commands that Claude runs in the sandbox against GitHub, such as `git clone`, `git fetch`, or `git push`, also fail. The domains the sandbox always blocks (see [Network requirements](https://claude.com/docs/claude-science/network-requirements.md#domains-the-sandbox-always-blocks)) stay blocked whichever list is in force.
161161 
162162The allowlist governs the network connections of code Claude runs in the sandbox on the member's computer, the local-command connectors that run inside it, and, while you manage it, the [model endpoints](#scientific-model-endpoints) members connect by host name. Jobs on SSH hosts use the host's own network, so the allowlist doesn't apply to them, and the [**Allow members to connect SSH hosts**](#ssh-hosts) switch is the control for those.
163163 

claude-science/network-requirements Changed · +2 / -2 lines

from line 54
5454| `conda.anaconda.org`, `repo.anaconda.com`, `anaconda.org`, `*.anaconda.org`, `*.conda.io` | conda packages |
5555| `cran.r-project.org`, `cloud.r-project.org`, `bioconductor.org`, `www.bioconductor.org` | R packages from CRAN and Bioconductor |
5656| `registry.npmjs.org` | npm packages for connectors that need them |
57| `github.com`, `*.github.com`, `*.githubusercontent.com` | Tools and packages published as GitHub releases |
57| `github.com`, `*.github.com`, `*.githubusercontent.com` | Tools and packages published as GitHub releases, and git commands Claude runs against GitHub repositories |
5858 
59Claude Science itself does not require GitHub; the package manager ships inside the app. The GitHub domains are used only when a package Claude installs is published as a GitHub release or a member imports a skill from a GitHub repository, and blocking them fails only those operations.
59Claude Science itself does not require GitHub; the package manager ships inside the app. The GitHub domains are used when a package Claude installs is published as a GitHub release, when a member imports a skill from a GitHub repository, and when code Claude runs reaches GitHub, for example with `git clone`, `git fetch`, or `git push`. If your firewall blocks them, those operations fail.
6060 
6161When you configure a conda channel mirror, Claude Science removes only the conda hosts (`conda.anaconda.org`, `repo.anaconda.com`, `anaconda.org`, `*.anaconda.org`) from the allowlist, and a Python index mirror removes only `pypi.org`, `*.pypi.org`, and `files.pythonhosted.org`. The `*.conda.io`, CRAN and Bioconductor, npm, and GitHub rows stay. A removed host is reachable again if a member re-adds it under **Settings** > **Network** or an administrator lists it in `[sandbox.network] allowed_domains`, which takes precedence over the removal. Environment builds contact the mirror host directly from the workstation, not through the outbound proxy, so it must be reachable directly (over your VPN or internal network if the mirror is internal, HTTPS on TCP 443 or 8443). A proxy allowlist entry alone does not make the mirror reachable for builds, and build-time mirror traffic will not appear in your proxy logs. See [Point package installs at an internal mirror](https://claude.com/docs/claude-science/corporate-networks.md#point-package-installs-at-an-internal-mirror).
6262 

claude-tag/admins/customize Changed · +0 / -1 lines

from line 24
2424| Setting | What it does | More |
2525| :- | :- | :- |
2626| Custom instructions | Standing guidance read in every session on a scope, like team conventions. Outranks channel memory. | [Add custom instructions](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#add-custom-instructions) |
27| Managed by | Which other Slack channels' members can write a channel's standing instructions by asking Claude, including from a private channel. On the Enterprise plan, an Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) sets it on the **Admin** tab of the channel's Configure page. | [Manage a channel's instructions from another channel](https://claude.com/docs/claude-tag/admins/managed-by.md) |
2827| How Claude participates | When Claude replies to a channel's messages. **How Claude participates** exists only on channels. Channel members can change it too, from Slack or the channel's Configure page, unless the scope's [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) setting is **Block**. | [Turn automatic replies on or off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) |
2928| Plugins | Bundles of skills that teach Claude how to use a specific tool | [Attach plugins](https://claude.com/docs/claude-tag/admins/add-connections.md#attach-plugins) |
3029| Connectors | Which systems Claude can reach from each channel | [Add a connector](https://claude.com/docs/claude-tag/admins/add-connections.md) |

claude-tag/admins/restrict-access Changed · +0 / -3 lines

from line 403
403403* Edit workspace and channel settings at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), such as custom instructions and the default model
404404* Turn Claude on or off for a workspace or a channel with its **Enable Claude Tag** switch, or for every channel with the **Respond in all channels** switch on the **Slack** page
405405* Add and remove [channel managers](#delegate-channel-setup-to-channel-managers), if the role also sets **Identity & Access** to **Can manage**
406* Set up [**Managed by**](https://claude.com/docs/claude-tag/admins/managed-by.md) for a channel, on the **Admin** tab of the channel's Configure page
407406* Open [on-call setup](https://claude.com/docs/claude-tag/admins/setup-oncall.md) at [`claude.ai/oncall`](https://claude.ai/oncall)
408407* Set a scope's [**How should Claude work in channels with guests**](#restrict-guest-channels) setting to **Restrict** or **Channel only**; choosing **Full access** or setting a scope back to **Inherit** stays with Owners
409408 
from line 439
440439A channel manager is a member of your Claude organization who can set up Claude in specific channels without the Owner role. Channel managers are available on the Enterprise plan. An Owner can add or remove them, and so can a [Claude Tag admin](#delegate-claude-tag-administration) whose role also sets **Identity & Access** to **Can manage**.
441440 
442441You name channel managers one channel at a time. For that channel, a channel manager sets the default model, adds repositories, manages credentials and plugins in the channel's bundle, and edits channel instructions. Every other setting at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) stays with Owners; on the Enterprise plan, an Owner can delegate most of them through the [**Claude Tag Admin** permission](#delegate-claude-tag-administration).
443 
444A channel manager is a person. To let the members of another Slack channel write a channel's instructions, see [Manage a channel's instructions from another channel](https://claude.com/docs/claude-tag/admins/managed-by.md).
445442 
446443### What a channel manager can do on the Configure page
447444 

claude-tag/users/good-habits Changed · +0 / -1 lines

from line 169
169169| How this channel should behave: format, tone, when to respond | [**Channel memory**](https://claude.com/docs/claude-tag/users/memory.md) (say it and ask Claude to remember) | Anyone in the channel | This channel; the whole workspace only if Claude saves it as a workspace note from a public channel |
170170| Conventions and setup for one repository: file layout, PR labels, dependencies to install | **`CLAUDE.md`** at the repo root ([loaded when the repo is](https://claude.com/docs/claude-tag/admins/configure-github.md#what-loads-from-a-repository)) | Anyone with repo write | Any session that works in that repo, from any channel |
171171| Standing rules for this channel that outrank memory | The [**Configure** page](#configure-claude-for-a-channel), in the **Channel instructions** field | Channel members, unless an admin has [restricted it](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) | This channel |
172| A correction for this channel that you don't want to raise in the channel | [**Managed instructions**](https://claude.com/docs/claude-tag/admins/managed-by.md#correct-claude-privately-from-a-managing-channel), written from a private managing channel | Full workspace members in the managing channel who have a Claude account in your organization, after an Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) sets it up | This channel |
173172| How to use a tool correctly, or follow a specific process, org-wide | [**A skill**](https://claude.com/docs/claude-tag/admins/skills-repo.md) in your org's plugin marketplace | An organization Owner adds it; anyone can ask Claude to open a PR proposing the change | Every workspace and channel it's added to |
174173| Standing rules across many channels | [**Workspace instructions** or **Slack instructions**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#add-custom-instructions) in Claude Tag admin settings | An organization Owner, or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) for a workspace | Every channel in that workspace, or in all of Slack |
175174 
Feedback