Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
320 changes: 170 additions & 150 deletions content/.metadata.json

Large diffs are not rendered by default.

111 changes: 111 additions & 0 deletions content/CHANGELOG.md

Large diffs are not rendered by default.

40 changes: 20 additions & 20 deletions content/claude-code-manifest.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,25 +6,25 @@
"url": "https://github.com/anthropics/claude-code/issues"
},
"dist": {
"shasum": "09af0517822a0ba947a126b2e0ecb4d7953bdae5",
"tarball": "https://registry.npmjs.org/@anthropic-ai/claude-code/-/claude-code-2.1.273.tgz",
"shasum": "9fe3efc2385bd3c528d5b0c15c5cdc5d59994654",
"tarball": "https://registry.npmjs.org/@anthropic-ai/claude-code/-/claude-code-2.1.274.tgz",
"fileCount": 7,
"integrity": "sha512-ym42/WNRf6H43FQdIPigvzzTW0DeQ1CPqrTdYnAlkWVGj8x8NaysCE0TU148mb3lpny5yo1/94+7dQK5USmBEQ==",
"integrity": "sha512-UI8TGoOO0fYT38VSoAjtu9C0EQkOwgwA4+ETFCgQhTO9NZvpgCERANL0UzioEW89b2zbcoL1B3z+7W37QdBxOA==",
"signatures": [
{
"sig": "MEUCIA4o1Cs72BgCsBRQvpIm99HbKmhHFl4btpVNkYh/stJmAiEArnbb2UwnN/2Qn2rpn8wOHbRd3evEsY4M2jEYc4/9hDk=",
"sig": "MEQCIFATAp0Ar6mIkqqiORV77Xudx3H6Pld/ekz4NOWmRq86AiAPeq18xT8t0wExq9mhHLLuAhRLv+X5xEp2v5MTG/aqfA==",
"keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"
},
{
"sig": "MEYCIQC34CmdXeY1YPtTFYQN93odm+HcK30+LMh/NVD6DbEKGwIhANFC9lFeBD8cikUxxulz0RhUDiX6cVEChdPfyTRaKeeW",
"sig": "MEUCIQC6g6bJC4OEaVsVincyexVfEvQggxc3dWASMVRDmYDkJQIgEpuMa546fs6/duNclLgp1yiQp/0vFNdFkuAABQbFpyk=",
"keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"
}
],
"unpackedSize": 184549
"unpackedSize": 184602
},
"name": "@anthropic-ai/claude-code",
"type": "module",
"_from": "file:staged-npm/anthropic-ai-claude-code-2.1.273.tgz",
"_from": "file:staged-npm/anthropic-ai-claude-code-2.1.274.tgz",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
Expand All @@ -42,8 +42,8 @@
"email": "wolffiex@anthropic.com"
},
"homepage": "https://github.com/anthropics/claude-code",
"_resolved": "/home/runner/work/claude-cli-internal/claude-cli-internal/staged-npm/anthropic-ai-claude-code-2.1.273.tgz",
"_integrity": "sha512-ym42/WNRf6H43FQdIPigvzzTW0DeQ1CPqrTdYnAlkWVGj8x8NaysCE0TU148mb3lpny5yo1/94+7dQK5USmBEQ==",
"_resolved": "/home/runner/work/claude-cli-internal/claude-cli-internal/staged-npm/anthropic-ai-claude-code-2.1.274.tgz",
"_integrity": "sha512-UI8TGoOO0fYT38VSoAjtu9C0EQkOwgwA4+ETFCgQhTO9NZvpgCERANL0UzioEW89b2zbcoL1B3z+7W37QdBxOA==",
"_npmVersion": "11.19.0",
"description": "Use Claude, Anthropic's AI assistant, right from your terminal. Claude can understand your codebase, edit files, run terminal commands, and handle entire workflows for you.",
"directories": {},
Expand Down Expand Up @@ -106,19 +106,19 @@
"_hasShrinkwrap": false,
"readmeFilename": "README.md",
"optionalDependencies": {
"@anthropic-ai/claude-code-linux-x64": "2.1.273",
"@anthropic-ai/claude-code-win32-x64": "2.1.273",
"@anthropic-ai/claude-code-darwin-x64": "2.1.273",
"@anthropic-ai/claude-code-linux-arm64": "2.1.273",
"@anthropic-ai/claude-code-win32-arm64": "2.1.273",
"@anthropic-ai/claude-code-darwin-arm64": "2.1.273",
"@anthropic-ai/claude-code-linux-x64-musl": "2.1.273",
"@anthropic-ai/claude-code-linux-arm64-musl": "2.1.273"
"@anthropic-ai/claude-code-linux-x64": "2.1.274",
"@anthropic-ai/claude-code-win32-x64": "2.1.274",
"@anthropic-ai/claude-code-darwin-x64": "2.1.274",
"@anthropic-ai/claude-code-linux-arm64": "2.1.274",
"@anthropic-ai/claude-code-win32-arm64": "2.1.274",
"@anthropic-ai/claude-code-darwin-arm64": "2.1.274",
"@anthropic-ai/claude-code-linux-x64-musl": "2.1.274",
"@anthropic-ai/claude-code-linux-arm64-musl": "2.1.274"
},
"_npmOperationalInternal": {
"tmp": "tmp/claude-code_2.1.273_1789495593984_0.00547513167959246",
"tmp": "tmp/claude-code_2.1.274_1789598169796_0.914194267676016",
"host": "s3://npm-registry-packages-npm-production"
},
"_id": "@anthropic-ai/claude-code@2.1.273",
"version": "2.1.273"
"_id": "@anthropic-ai/claude-code@2.1.274",
"version": "2.1.274"
}
31 changes: 26 additions & 5 deletions content/claude/claude-tag/concepts/personal-connectors.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,21 +42,42 @@ To change a saved answer, open the Claude app in Slack and select its **Home** t

### Review results before posting

Claude can hold a result and show it to you before anything posts to the channel. When you chose **Allow with review**, Claude holds every result. When you chose **Allow**, Claude holds a result when the content looks sensitive and posts the rest directly. Once you approve a held result, Claude posts it in the thread where you asked.
Claude can hold a result and show it to you before anything posts to the channel. When you chose **Allow with review**, Claude holds every result. When you chose **Allow**, Claude holds a result when the content looks sensitive and posts the rest directly.

Before a result posts directly, Claude checks it for private or sensitive content and holds anything the check flags so you can review it first. The check looks for content such as:

* Credentials and secret keys
* Personal identifiers
* Compensation, HR, and performance records
* Personnel changes, including layoffs, offboarding, hiring, and candidates
* Customer, deal, and other commercial information
* Privileged legal material
* Company strategy, unannounced plans, and in-flight projects
* Protected-class information
* Medical and health information
* Security incidents

The check is a screen, not a guarantee, and it doesn't consider whether other people in the channel have the same access you do. For sensitive topics, choose **Allow with review** so you see every result before it posts, and use judgment about what you bring into a shared channel.

Once you approve a held result, Claude posts it in the thread where you asked.

On the Enterprise plan, an Owner can set the review rule for a scope with the **Delegated task results** setting, at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) → **Claude Tag's access** → **Slack** → the scope → **Advanced** → **Delegated task results**. **Require review** removes **Allow** from the prompt and **Auto mode** from the **Home** tab, so Claude holds every result for your review. **Share without review** removes **Allow with review** from both.

### Stop connector use

To stop a task that's using your connectors, select **Stop** under the message in the task's thread where Claude says it's going to use your connectors. Only you can see the **Stop** button.

## What other people in the channel see
## How Claude protects your connectors

Results stay visible in the channel. What Claude posts back to a channel thread is readable by everyone there, like any other work Claude does in a channel. Claude's detailed work on a task you approved lives in a session only you can open. The work runs with your permissions and is recorded under your name.
Other people can't use your connectors. Requests other people make to Claude in your task's thread run with the connections an admin attached to the channel, not with your connectors.

While Claude works on your connector task, it is designed to take direction from you. Other people's messages in the thread reach Claude as information about the task, not as instructions. A message that tells Claude to change course or share what it found can't use your connectors, and Claude is designed not to let it redirect your task.

Other people can't use your connectors. Requests other people make to Claude in your task's thread run with the channel's own access, not with yours.
Claude treats anything else it reads while it works the same way. A web page it visits, a comment on a GitHub pull request, or a Slack conversation you ask it to summarize can all contain text written to look like instructions for Claude, a technique called prompt injection. Claude is designed to treat what it reads as material to weigh rather than commands to follow.

While Claude works on your connector task, it is designed to take direction from you and to treat what other people post in the thread as information for the task rather than as instructions.
## What other people in the channel see

Results stay visible in the channel. What Claude posts back to a channel thread is readable by everyone there, like any other work Claude does in a channel. Claude's detailed work on a task you approved lives in a session only you can open. The work runs with your permissions and is recorded under your name.

## Related resources

Expand Down
2 changes: 1 addition & 1 deletion content/claude/government/config/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Settings that may contain secrets, such as telemetry headers, are never echoed b

## When changes take effect

Settings that govern the admin portal, such as whether organizations may manage seat tiers, apply immediately. Settings that govern the Claude applications themselves, such as the Claude Desktop banner, product availability, and telemetry endpoint, are delivered to each member's application the next time it refreshes its configuration, which happens when the application is launched or the member signs in. You do not need to push anything, but members who are currently running the application may need to restart it to pick up a change. Lowering the session idle timeout applies to new sign-ins only, and so does raising or removing the maximum session length. Lowering the maximum session length, or setting one for the first time, also reaches members who are already signed in, taking up to one idle timeout period to do so, as described under [Maximum session length](/docs/government/config/settings#maximum-session-length).
Settings that govern the admin portal, such as whether organizations may manage seat tiers, apply immediately. Settings that govern the Claude applications themselves, such as the Claude Desktop banner, product availability, and telemetry endpoint, are delivered to each member's application the next time it refreshes its configuration, which happens when the application is launched or the member signs in. You do not need to push anything, but members who are currently running the application may need to restart it to pick up a change. Claude Desktop prompts for that restart, and requires it once the [Restart deadline for configuration changes](/docs/government/config/settings#restart-deadline-for-configuration-changes) has passed. Lowering the session idle timeout applies to new sign-ins only, and so does raising or removing the maximum session length. Lowering the maximum session length, or setting one for the first time, also reaches members who are already signed in, taking up to one idle timeout period to do so, as described under [Maximum session length](/docs/government/config/settings#maximum-session-length).

## Working with the list

Expand Down
Loading
Loading