这是本节的多页打印视图。点击此处打印.

[产品]Claude Tag

Claude 新推出的 Tag 产品

1: 概述
2: 信息和介绍

2.1: Introducing Claude Tag
2.2: Tag Claude in Slack
2.3: What is Claude Tag?
2.4: Work with Claude Tag

3: 运行机制

3.1: How Claude Tag works
3.2: Glossary
3.3: How agent identity works
3.4: Agent identity: a new access model
3.5: Security and data handling
3.6: Data lifecycle and deletion
3.7: Claude Tag settings map
3.8: Claude Tag for Claude Code users

1 - 概述

Claude Tag 概述

基本信息

产品名：Claude Tag
发布：2026 年 6 月 23 日（公开 Beta）
厂商：Anthropic
形态：Slack 频道里的共享 AI 队友；在频道中 @Claude 委派任务
底层模型：默认 Opus 4.8（频道内可切换）
可用计划：Claude Team / Enterprise（Anthropic 第一方服务）。Free / Pro / Max 以及 Bedrock、Vertex 等第三方部署不可用
取代：旧版 Claude in Slack（含 Claude Code in Slack）。Slack 侧已于 2026 年 8 月 3 日切到 Claude Tag
官方产品页：https://claude.com/product/tag
管理后台：https://claude.ai/admin-settings/claude-tag
文档总索引（机器可读，含全部 Claude Tag 条目）：https://claude.com/docs/llms.txt

一句话：Claude Tag 把 Claude Code 那套云端沙箱引擎放进团队 Slack，用组织级 Agent Identity（服务账号）干活，而不是借用某个员工的个人权限。

使用门槛（读资料前先记住）

只有 Claude 组织的 Primary Owner / Owner 能完成身份与频道配置；普通 Admin 看得到但配不完
组织必须先开启 Routines，否则 @Claude 会回不可用
启用了 Zero Data Retention（ZDR）的组织不能用（需要存频道记忆与 session 记录）
频道内 Tag 走组织用量余额；私信 DM 走个人 claude.ai 席位
Slack 配对：在频道发送 @Claude connect，15 分钟内把配对码贴到管理页

怎么用这份列表

按编号从 1 往下读即可。每一条对应一篇原文，后面可以单独拆成学习笔记。

必读：深入理解产品所必须过一遍
按需：连接指南、单点用例，按自己的工具栈和场景选读，不必全篇啃完
中文二手文放在最后，只作对照，以官网为准

第一阶段：产品是什么

先建立定位：它不是又一个 Slack 聊天机器人，而是多人、异步、带独立身份的团队 Agent。

Introducing Claude Tag（必读）
Anthropic 发布博文。多人协作、跨天记忆、Ambient 主动跟进、异步执行；内部产品团队约 65% 代码来自内部版 Tag。
Claude in Slack: Tag @Claude in any thread（必读）
官方产品页。适合先看它对外承诺的能力边界。
什么是 Claude Tag？（必读，中文）
帮助中心总述：频道 Tag / DM / 助手面板三套入口，计费、权限层级、记忆与隐私。
What is Claude Tag?（对照）
上一篇的英文原文，细节有出入时以这篇和官方 docs 为准。
Work with Claude Tag（必读）
官方文档总览。管理员一次性配置、终端用户如何派活、计费与 spend limit、常见用途入口。

第二阶段：运行机制（深入核心）

这一阶段是后面所有配置和用法的地基。建议按顺序、每篇读完再进下一篇。

How Claude Tag works（必读）
会话模型：@Claude → 短暂沙箱 → checklist → 回帖 → 空闲释放。频道 session 与线程 session 的区别，以及和 Cowork / Claude Code 的对比表。
Glossary
先扫一遍术语：agent identity、Access bundle、scope、Agent Proxy、routine、channel memory、session。读后续文档时回查。
How agent identity works（必读）
频道里 Claude 用自己的服务账号，不是“替发消息的人行事”。频道 vs DM 的身份分叉、GitHub App 署名。
Agent identity: a new access model for autonomous, team-wide AI（必读）
概念博文（Noah Zweben，Claude Code 团队）。为什么 “act as the user” 在异步、多驾驶员场景会崩；公开频道共享工作区身份、私有频道隔离；未来 JIT 凭证。
Security and data handling（必读）
沙箱不持有凭证；凭证在网络边界注入；出站主机白名单；频道成员共享该频道 bundle 的能力。
Data lifecycle and deletion（必读）
Anthropic 侧存什么、存多久；断开工作区、卸载应用、删频道、离开组织分别发生什么。Slack 里删消息删不掉 session transcript。
Claude Tag settings map
管理页、用量页、频道内 Configure、个人 connector（仅 DM）分别管什么。
Claude Tag for Claude Code users
已会 Claude Code 的人必看：哪些配置能迁过来，哪些必须改由管理员配；Slack 线程如何映射到 session。

第三阶段：管理员配置

读完身份模型再看落地。组织里如果暂时没有 Owner 权限，仍建议通读 14–22，知道生产上要配哪些开关。

Set up Claude Tag（必读）
四步：配对 Slack → 接工具 → 设花费上限 → 私有频道试跑。含前置条件与常见失败。
What the Claude Slack app can access
写给批准 Slack 安装的人：OAuth scope、能读能发什么、安装本身不授予外部系统权限。
Give Claude access to your tools（必读）
Access bundle：专用服务账号、先接什么、allowed websites 如何限制可达范围。
Configure GitHub access
Claude 自己的 GitHub 身份、仓库授权、克隆进沙箱、依赖安装、GitHub Actions。写代码场景优先读。
Configure GitLab access
与 GitHub 对照，自建 GitLab 时读。
Configure per-channel access（必读）
bundle 绑到组织 / 工作区 / 单个频道；继承与重叠规则。
Restrict where Claude Tag operates（必读）
谁能调用、guest 频道、按频道开关、RBAC（Enterprise）、安静或移除。
Manage workspaces and versions
多个 Slack 工作区、Enterprise Grid、每频道 Off / Legacy / New。
Set a spend limit（必读）
组织用量余额、频道上限、75%/95% 告警；超限会拒绝任务，不会悄悄截断。
Customize Claude Tag
按 scope 定制，不是按人。哪些在 claude.ai 配，哪些可在频道里改。
Set up a skills repository Claude can update
组织 skills 放 git 并自动同步；可授权 Claude 给自己的 skills 开 PR。
Review what Claude Tag has done
审计页 + 各连接系统自己的日志；如何把一次动作追回 Slack 线程。
Network requirements
出站 IP、仅 HTTP/HTTPS；和企业防火墙 allowlist 的关系。
Migrate from the earlier Claude in Slack
身份从“每人自己的账号”变成“组织一个身份”；数据不迁移；频道可钉在 Legacy。
Troubleshoot Claude Tag setup
配置阶段报错手册。用到再查也可以。

连接指南（按需，不必按号全读）

先读总览，再只打开自己栈里有的服务。自定义 MCP 适合没有预设的内部系统。

第四阶段：作为频道成员怎么用

管理员配完之后，日常就靠这一组。建议 47–54 全读，用例库按自己工作选。

Get started（必读）
如何确认频道已开通、第一条消息、Claude 能读什么、DM 为何不同。
Commands Claude Tag understands（必读）
@Claude !restart、!routines 等 bang 命令；卡住或上下文跑偏时用。
Control when Claude Tag responds
没人 @ 它时会不会回；线程/频道静音。觉得它话太多或突然哑巴时读。
Good habits for working with Claude Tag（必读）
写清完成定义、选对频道、长任务尽早把产物推到 GitHub/文档，因为沙箱会释放。
Set up routines（必读）
定时任务、盯频道、订 PR；列出/暂停站岗工作。Ambient 行为的操作面。
What Claude Tag remembers（必读）
记忆属于频道不是个人；公开频道写入工作区记忆，私有频道隔离。如何查看和纠正。
Choose the model Claude Tag uses
线程内切换、频道默认、DM 选模型。
Prompt library
可粘贴的第一句、转发交接、频道规则、记忆检查、中途转向。
Troubleshoot Claude Tag in channels and DMs
无回复、排队失败、丢失工作、缺连接、链接被拦。用到再查。

用例库（按需）

先读总库，再按场景点开单篇。每篇都带可粘贴 prompt 和所需连接。

第五阶段：内部案例与业界评论

官方 docs 读完后，用案例建立“团队里到底怎么用”的直觉。

How Anthropic employees use Claude Tag（必读）
Anthropic 内部：客诉/事故汇总、法务审素材、数据自助查询等。
Self-service data analytics in Slack
内部如何把数仓问答放到共享频道。若链接变更，从上一篇文末的 related posts 进入。
Anthropic releases Claude Tag, a virtual employee that works within Slack
Fortune 报道。Cat Wu 对“相对 Claude Code / Cowork 的多人产品”表述；和 Slackbot、Agentforce 的竞品语境。
Anthropic and Salesforce Announce New Claude to Slack Integration
Salesforce 侧对 ambient colleague 的解读。

附录：中文二手整理（对照用，不作为依据）

官方与帮助中心读完后，如需中文导读可看这些，细节冲突以 1–69 为准。

建议的精读顺序（压缩版）

时间紧时，先按这条最短路径走完再回头补按需篇：

1 → 3 → 5 → 6 → 8 → 9 → 10 → 14 → 16 → 19 → 20 → 22 → 47 → 50 → 51 → 52 → 56 → 70

最短路径过完，对身份模型、沙箱生命周期、管理员四步、日常派活和内部案例就有完整骨架；其余编号按工具栈和场景插入即可。

2 - 信息和介绍

Claude Tag 信息和介绍

本栏按资料列表顺序，存放原文的中英对照。完整编号清单见概述。

已完成：

Introducing Claude Tag（发布博文）
Tag Claude in Slack（产品页） 3–4. What is Claude Tag?（帮助中心；中英官方合并为一篇）
Work with Claude Tag（文档总览）

编号 6–13（运行机制）见机制。

2.1 - Introducing Claude Tag

Anthropic 发布博文 Introducing Claude Tag 的中英对照

来源： Introducing Claude Tag
日期： 2026 年 6 月 23 日
分类： Product

Introducing Claude Tag / 介绍 Claude Tag

Claude Tag is a new way for teams to work with Claude.

Claude Tag 是团队与 Claude 协作的一种新方式。

We’re starting on Slack, which Claude can join as a team member. Grant Claude access to selected channels, and connect it to whichever tools, data—and even codebases—you choose. Then, anyone in the channel can tag @Claude in, and delegate tasks to it while they focus on other work. Claude builds context by remembering relevant information from the channels it’s in, and can plan out tasks to complete in the future.

我们先从 Slack 开始——Claude 可以像一名团队成员一样加入其中。向选定的频道授予 Claude 访问权限，并把它连接到你选择的任意工具、数据，乃至代码库。之后，频道里的任何人都可以 @Claude，把任务委派给它，自己去忙别的事。Claude 会记住它所在频道中的相关信息来建立上下文，并能规划将来要完成的任务。

We see Claude Tag as the beginning of an evolution of Claude Code: it makes the model even more proactive, and it works better with a full team. Tagging @Claude is now one of the main ways we get things done at Anthropic. Today, 65% of our product team’s code is created by our internal version of Claude Tag. The same pattern is now spreading well beyond engineering—we’re tagging Claude to chase down product metrics and data, work through support tickets, or even help find the root cause of tricky bugs.

我们把 Claude Tag 视为 Claude Code 演化的开端：它让模型更加主动，也更适合与整个团队一起工作。在 Anthropic 内部，@Claude 已经成为我们推进工作的主要方式之一。目前，产品团队 65% 的代码由内部版 Claude Tag 产出。同一模式正在超出工程范围扩散——我们会 @Claude 去追查产品指标与数据、处理支持工单，甚至帮忙定位棘手缺陷的根因。

We’re launching Claude Tag on Slack, since it’s a natural home for collaborative work between teams and AI, and where much of Anthropic’s day-to-day work already happens. It’s available today in beta for Claude Enterprise and Team customers. Our goal is to expand where it’s available more widely, so that teams can tag @Claude in the many other places they work.

我们选择在 Slack 上线 Claude Tag，因为它天然适合团队与 AI 的协作，而 Anthropic 日常工作的很大一部分也已经发生在这里。即日起，Claude Enterprise 与 Team 客户可以以 beta 使用。我们的目标是把它扩展到更多地方，让团队能在日常工作的许多其他场景里 @Claude。

Working with @Claude / 与 @Claude 一起工作

If you’ve worked with Claude Code or Cowork before, Claude Tag will feel familiar. Tag @Claude with a request in simple terms and it’ll break its task down into stages and then work through them in turn, using the tools it has access to. Once it’s done, it’ll respond in a Slack thread with what it’s created.

如果你用过 Claude Code 或 Cowork，Claude Tag 会有熟悉感。用简单的话向 @Claude 提出请求，它会把任务拆成若干阶段，再依次利用它能访问的工具推进。完成后，它会在 Slack 线程里回复它所产出的内容。

But tagging Claude comes with a few new advantages:

不过，@Claude 还带来几项新的优势：

@Claude is multiplayer. Within a given Slack channel, there’s one Claude that interacts with everyone. This means that anyone can see what it’s working on, and can pick up the conversation from where the last person left off. This makes tagging Claude very different from working within a single chat or for a single task—it’s much more like interacting collaboratively with a teammate.

@Claude 是多人的。 在一个给定的 Slack 频道里，只有一个与所有人互动的 Claude。这意味着任何人都能看到它正在做什么，也可以从上一任停下的地方接续对话。这让 @Claude 与「单独开一个聊天」或「只做一件任务」非常不同——它更像是在和一位队友协作。

@Claude learns over time. As Claude follows along with its channel, it builds more context about the work. This means that users don’t need to explain things to it from scratch over and over again. And Claude can even automatically learn from other Slack channels and data sources, if it’s granted permission. (It doesn’t report from private channels.) This gives it the tacit knowledge necessary for it to provide the best possible work.

@Claude 会随时间学习。 随着 Claude 跟进它所在的频道，它会积累关于这项工作的更多上下文。因此用户不必一遍又一遍地从零解释。若获得授权，Claude 甚至还能自动从其他 Slack 频道和数据源学习。（它不会从私有频道向外汇报。）这为它提供了把工作做到最好所需的默会知识。

@Claude takes initiative. If “ambient” behavior is enabled, Claude will proactively keep you updated about whatever it thinks you might need to know. It’ll flag relevant information from across the channels it’s in and the tools it’s connected to, and follow up on threads or tasks that have gone quiet without being resolved.

@Claude 会主动作为。 若启用了 “ambient”（主动在场）行为，Claude 会主动把它认为你可能需要知道的事情更新给你。它会从所在频道和已连接的工具中标出相关信息，并跟进那些陷入安静、却尚未解决的线程或任务。

@Claude works asynchronously. Set Claude a task, and you can focus on your other priorities while it works. It can also schedule tasks for itself, pursuing a project autonomously over hours or days. We’ve found this particularly helpful at Anthropic: we now spend much more of our time delegating tasks to many Claudes in parallel.

@Claude 异步工作。 给 Claude 一项任务后，你可以在它干活时去忙别的优先级。它也可以给自己安排任务，在数小时乃至数天里自主推进一个项目。我们在 Anthropic 内部发现这一点尤其有用：现在我们把更多时间花在把任务并行委派给许多个 Claude 上。

You can also send Claude direct messages: it’ll respond privately, using the personal tools and connectors you’ve set up.

你也可以给 Claude 发私信：它会私下回复，并使用你个人已配置的工具与连接器。

Getting started / 开始使用

We’ve designed Claude Tag with teams and organizations in mind: @Claude’s access to sensitive data and task-specific tools can be very tightly controlled.

我们从一开始就按团队与组织来设计 Claude Tag：@Claude 对敏感数据和任务专用工具的访问可以被非常精细地控制。

To get up and running, system administrators specify which tools and information the model should have access to, in which channels. Think of it as creating separate Claude identities for different uses: everything, including its memories, will stay scoped to the channels defined by the administrators. For example, a model set up for sales work won’t pass on memories to one set up for engineering; nor will it give engineers access to any sales data or tools. More information about provisioning access is available here.

要跑起来，系统管理员需要指定模型应能访问哪些工具与信息、以及在哪些频道中访问。可以把它理解成：为不同用途创建相互分离的 Claude 身份。包括记忆在内的一切，都会被限定在管理员划定的频道范围内。例如，为销售工作配置的模型不会把记忆传给为工程配置的那一个，也不会让工程师拿到任何销售数据或工具。关于如何配置访问权限，见 How agent identity works。

Once permissions are set, everyone can begin tagging right away. Administrators can set limits for token spend (both for the organization and for individual channels), and can view a log of everything that @Claude has done, along with who requested each task.

权限设定完成后，所有人都可以立刻开始 @Claude。管理员可以为 Token 花费设置上限（组织级与单个频道级），并查看 @Claude 做过的全部事项日志，以及每项任务是由谁发起的。

If you’re a Claude Enterprise or Team customer, you have access to Claude Tag in beta starting today. To get started, visit here and follow these four steps:

如果你是 Claude Enterprise 或 Team 客户，即日起即可使用 Claude Tag 的 beta。请打开管理设置，按下面四步操作：

Pair Claude Tag with your Slack workspace
将 Claude Tag 与你的 Slack 工作区配对
Give Claude access to your tools
向 Claude 授予你的工具访问权限
Set a limit on your organization’s monthly spend
为组织设定每月花费上限
Test Claude in a private channel to confirm it works.
在私有频道中测试 Claude，确认其工作正常。

Claude Tag replaces the existing Claude in Slack app. To migrate, administrators can opt in within 30 days. We’re issuing an introductory launch credit to eligible Enterprise and Team organizations so that the whole company can try it out.

Claude Tag 将取代现有的 Claude in Slack 应用。迁移时，管理员可在 30 天内选择加入。我们会向符合条件的 Enterprise 与 Team 组织发放上线试用额度，方便全公司试用。

Claude Tag works with Opus 4.8. You can read our docs and product page.

Claude Tag 基于 Opus 4.8。你可以阅读我们的文档和产品页。

2.2 - Tag Claude in Slack

官方产品页 Claude in Slack: Tag @Claude in any thread 的中英对照

来源： Claude in Slack: Tag @Claude in any thread
状态： Public Beta
文档： Read documentation

Tag Claude in Slack / 在 Slack 里 Tag Claude

@Claude reacts in real time, where the work is happening. Available today for Claude Enterprise and Team in Slack. Tag it in, and it tags you back.

@Claude 在工作发生的地方实时响应。即日起面向 Slack 中的 Claude Enterprise 与 Team 开放。你把它 Tag 进来，它会把你 Tag 回去。

@Claude reads threads, understands full context, and reacts in real time so your team moves forward together. Bring Claude into your channel.

@Claude 会阅读线程、理解完整上下文，并实时响应，让团队一起往前走。把 Claude 请进你的频道。

Available in beta for Claude Enterprise and Team customers in Slack.

目前以 beta 提供给 Slack 中的 Claude Enterprise 与 Team 客户。

Customer quotes / 客户评价

“Claude Tag is our first responder for internal bugs. It reads incoming reports, looks at screenshots of failures, and uses access to Datadog, Linear, and GitHub to weed out user errors, trace root cause, and often draft a fix PR. Our engineers’ first reaction was ‘this is amazing.’” — Aabhas Sharma, CTO

“Claude Tag 是我们内部缺陷的第一响应者。它阅读收到的报告、查看失败截图，并利用对 Datadog、Linear 和 GitHub 的访问，筛掉用户操作失误、追查根因，还经常起草修复 PR。工程师们的第一反应是‘这太厉害了。’” —— Aabhas Sharma，CTO

“Claude Tag turned a summer of conference logistics — the follow-ups and chasing that always fell through the cracks — into an events program that runs itself while I stay on strategy.” — Matthew Scott, Product Marketing

“Claude Tag 把一个夏天的会议后勤——那些总是漏掉的跟进和催办——变成了一套能自己运转的活动体系，而我继续盯策略。” —— Matthew Scott，产品市场

“Claude Tag doesn’t just do the work — it challenges our thinking, provokes better questions, and elevates our judgement rather than replacing it. And we still feel very much in control throughout.” — Simon Mansfield, Director, Enterprise AI

“Claude Tag 不只是把活干了——它挑战我们的想法、逼出更好的问题，并提升我们的判断，而不是取代判断。全程我们仍觉得掌控在自己手里。” —— Simon Mansfield，企业 AI 总监

“There were no skeptics on our team. Everyone leaned in from day one — it felt like Claude Tag in Slack was something they’d been waiting for.” — Darian Bailey, AI Engineer & Tag Admin

“团队里没有怀疑者。从第一天起所有人都扑了上去——感觉 Slack 里的 Claude Tag 是他们一直在等的东西。” —— Darian Bailey，AI 工程师兼 Tag 管理员

“Claude Tag meets our teams where they already work. Slack is the entry point for everything at Gusto, and the fact that Claude Tag is native there is huge for us. We see a lot of potential here.” — Chad Kunsman, AI Developer

“Claude Tag 在团队已经工作的地方与他们会合。在 Gusto，Slack 是一切的入口，Claude Tag 原生在那里对我们意义很大。我们看到很大潜力。” —— Chad Kunsman，AI 开发者

Coming soon to Microsoft Teams / 即将登陆 Microsoft Teams

Tag @Claude in Teams, where it will read the conversation, understand context, and respond in real time.

在 Teams 里 Tag @Claude，它会阅读对话、理解上下文，并实时响应。

How it works / 它如何工作

Tag Claude into any thread in Slack, no matter how long or messy. It reacts to context, decisions, or open questions to help busy teams get more done.

把 Claude Tag 进 Slack 里任意线程，无论多长、多乱。它会对上下文、决策或未决问题作出反应，帮助忙碌的团队多做成事。

Tag it in. @Claude in any thread or channel and it picks up the context everyone already shares. Ask it to run the numbers, file a ticket, or organize a chaotic chat into action items. It reads the room and does the work.

把它 Tag 进来。 在任意线程或频道里 @Claude，它会接上大家已经共享的上下文。让它跑数字、建工单，或把一团乱的聊天整理成待办。它读懂现场，然后干活。

Set a schedule or let it run long tasks. Give @Claude standing instructions and it works without a mention now or in the future. Ask it to watch a channel, run a weekly digest, flag anything urgent, or page the right person.

设定日程，或让它跑长任务。 给 @Claude 常驻指令，它现在或将来都不必再被提及也能工作。让它盯一个频道、做每周摘要、标出紧急事项，或呼叫对该的人。

It jumps in, and can tag you back. @Claude doesn’t wait to be asked. It surfaces the thread that went quiet, posts when the deploy is live, and flags the decision that needs your call.

它会主动介入，也可以把你 Tag 回去。 @Claude 不会干等被叫。它会把冷掉的线程翻上来，在部署上线时发帖，并标出需要你拍板的决策。

How teams use @Claude / 团队如何使用 @Claude

Claude in Slack can share work in the format your team needs, right in the thread.

Slack 里的 Claude 能以团队需要的形式，直接在线程里交出工作成果。

Catch up fast. Prompt: @Claude What got decided here and what's still open?
Get everything you need from a long thread in seconds. @Claude can surface decisions, open questions, and stakeholders, and you see exactly what’s waiting on you.

快速赶上进度。 提示词：@Claude What got decided here and what's still open?
几秒内从长线程里拿到你需要的一切。@Claude 能标出决策、未决问题和相关干系人，你也能看清哪些正等着你。

Pull the numbers. Prompt: @Claude Top 20 enterprise accounts by spend, last 7 and 28 days.
Ask @Claude to query your data and it posts results like metrics, benchmarks, and charts in the channel, so the whole team sees the answer and can keep asking questions right there.

把数字拉出来。 提示词：@Claude Top 20 enterprise accounts by spend, last 7 and 28 days.
让 @Claude 查询数据，它会把指标、基准和图表发到频道里，全团队都能看见答案，并就地继续追问。

Build from the thread. Prompt: @Claude Fix the bug in this thread and open a draft PR.
Turn a bug report into a draft PR from the context in the thread without ever leaving Slack. Get more done without switching tabs.

从线程里直接做出来。 提示词：@Claude Fix the bug in this thread and open a draft PR.
利用线程里已有的上下文，把缺陷报告变成草稿 PR，而不必离开 Slack。少切标签页，多做成事。

Prep before calls. Prompt: @Claude I'm meeting Acme at 2 — what do I need to know?
Walk into every meeting with a full briefing. CRM notes, recent threads, and call history pulled together before you think to ask.

会前准备。 提示词：@Claude I'm meeting Acme at 2 — what do I need to know?
带着完整简报走进每一次会议。CRM 笔记、最近线程和通话记录，在你想到要问之前就已经汇总好。

Watch what matters. Prompt: @Claude Watch this channel, triage what comes in, and work through the backlog. Tag me only when something needs my call.
@Claude can manage work in the channels your team never had bandwidth for: monitoring backlogs, triaging alerts, and surfacing what needs a human to review, so work that keeps getting pushed out can finally be completed.

盯住真正重要的事。 提示词：@Claude Watch this channel, triage what comes in, and work through the backlog. Tag me only when something needs my call.
@Claude 能管理团队一直腾不出手的频道：监控积压、分诊告警、把需要人审的事项翻上来，那些总被往后推的工作终于能做完。

Core capabilities / 核心能力

Understands your org. The longer Claude works with your team, the more it understands how your organization thinks, how decisions get made, and who owns what.

理解你的组织。 Claude 和团队共事越久，就越理解组织如何思考、决策如何作出、以及谁负责什么。

Memory across threads and days. Context can draw on previous conversations and memory. What happened in Monday’s standup is still there on Thursday, without anyone repeating it.

跨线程、跨天的记忆。 上下文可以调用先前的对话和记忆。周一站会里发生的事，周四还在，不必有人再讲一遍。

A shared resource in your channel. Claude surfaces what matters to the whole channel, not just the person who asked. Everyone sees the work, and anyone can build on it.

频道里的共享资源。 Claude 把对整个频道重要的事翻上来，而不只给提问的那个人。所有人都看见工作，任何人都可以在上面继续做。

Proactive action instead of asking. Set a standing instruction once. Claude watches the channel, runs routines, flags what’s urgent, and tags you back when something needs a decision.

主动行动，而不是等人问。 常驻指令设一次即可。Claude 盯着频道、跑 routines、标出紧急事项，并在需要决策时把你 Tag 回去。

In the work and tools with you. Shape how Claude works in each channel with skills and instructions. Give it access to tools and data to take action on your behalf and post results.

和你一起待在工作与工具里。 用 skills 和指令塑造 Claude 在每个频道里的工作方式。给它工具和数据的访问权，让它代为行动并把结果发出来。

Runs tasks that take days. Hand Claude a complex task and it works while you move on to other projects. It follows up, asks for input, or comes back when it’s done.

能跑耗时数天的任务。 把复杂任务交给 Claude，你转去做别的项目时它继续干。它会跟进、征求意见，或在做完后回来。

@Claude connects to your tools / @Claude 连接到你的工具

Configure any tool with an API using Agent Identity. Claude can query, act, and report back in the thread where the work is happening.

用 Agent Identity 配置任何带 API 的工具。Claude 可以查询、行动，并在工作发生的那条线程里回报。

Admins stay in control / 管理员保持掌控

Claude acts under its own identity in your systems. Admins configure access once; everyone else just types @Claude.

Claude 在你的系统里以自己的身份行动。管理员配置一次访问权限；其他人只需输入 @Claude。

Customizable identities for granular governance. Claude has its own account in your systems, not a borrowed login. Every credential’s use is logged, so “what did Claude do, and who asked for it?” always has an answer.

可定制身份，用于细粒度治理。 Claude 在你的系统里有自己的账号，而不是借用某个人的登录。每一次凭证使用都会被记录，因此「Claude 做了什么、是谁让它做的」总有答案。

Add it per channel. Decide which tools Claude can reach and read. Confine sensitive connectors to a single private channel or enable broader access for specific tools and resources. Adjust any time from the admin console.

按频道添加。 决定 Claude 能触及和阅读哪些工具。把敏感连接限制在单个私有频道，或为特定工具与资源开放更广的访问。可随时在管理控制台调整。

What is Claude Tag? — Learn more about @Claude and what happens to the former Claude for Slack experience.
Agent identity: a new security model for autonomous, team-wide AI — Explore our new security model built for agents, not retrofitted from chatbots.
Tutorial: Working with @Claude in your workspace — Claude now works alongside your team, under its own account, in the places you already work together. You tag it in the way you’d tag anyone, or have it speak up on its own when there’s something it can help with.

2.3 - What is Claude Tag?

帮助中心 What is Claude Tag? 的中英对照

来源（英）： What is Claude Tag?
来源（中）：什么是 Claude Tag？

What is Claude Tag? / 什么是 Claude Tag？

Claude in Slack switched over to the new Claude Tag experience on August 3, 2026. To integrate Claude and Slack, use Claude Tag instead. Learn how to set up Claude Tag or migrate from the earlier Claude in Slack.

Slack 中的 Claude 已于 2026 年 8 月 3 日切换到新的 Claude Tag 体验。要集成 Claude 和 Slack，请使用 Claude Tag。了解如何设置 Claude Tag 或从早期的 Slack 中的 Claude 迁移。

Claude Tag is a new way to work with Claude: tag @Claude into a conversation and it takes on real work, using your organization’s tools and the shared context around it. Claude works under its own identity, builds context by remembering relevant information from the channels it’s in, and can follow up on its own.

Claude Tag 是与 Claude 协作的一种新方式：在对话中标记 @Claude，它会承担真实工作，使用你组织的工具以及周围的共享上下文。Claude 以自己的身份工作，通过记住所在频道的相关信息来建立上下文，并可以自行跟进。

Claude Tag is available on Team and Enterprise plans in beta. Claude Tag works in Slack today.

Claude Tag 在 Team 和 Enterprise 计划中以测试版提供。Claude Tag 目前在 Slack 中可用。

It’s how we’ve brought Claude’s capabilities directly to Slack, bringing AI assistance into your team’s workspace. This integration allows you to work with Claude without leaving Slack through three convenient surfaces:

这是我们将 Claude 的能力直接带进 Slack 的方式，把 AI 协助放进团队工作区。通过三个便捷界面，你可以在不离开 Slack 的情况下与 Claude 协作：

Channel tagging: Tag @Claude in any channel to hand it a task, and follow along as it works in the thread.
Direct message with Claude: Start a private conversation with @Claude.
AI assistant panel: Click the Claude icon in Slack’s AI assistant header to open a panel on the right side of your Slack window, allowing you to access Claude from anywhere in the Slack app.
频道标记： 在任意频道中标记 @Claude 以交付任务，并在线程中跟进它的工作。
与 Claude 的私信： 与 @Claude 开始私人对话。
AI 助手面板： 点击 Slack AI 助手标题中的 Claude 图标，在窗口右侧打开面板，从 Slack 应用中的任何位置访问 Claude。

When you tag @Claude in a channel, Claude works through the task while the whole exchange stays visible to everyone in the channel. Everyone in a channel works with the same Claude, so anyone can steer it or pick up where it left off. Claude can also check in on its own, like posting when a job finishes or tagging you when a thread stalls. To learn more, see the Claude Tag overview.

当你在频道中标记 @Claude 时，Claude 会处理任务，整段交互对频道里所有人都可见。频道中的每个人都与同一个 Claude 协作，因此任何人都可以引导它，或从停下的地方接续。Claude 也可以自行检查，例如在工作完成时发帖，或在线程停滞时标记你。了解更多，见 Claude Tag 概述。

In direct messages and the assistant panel, Claude has the capabilities you’ve enabled in your own Claude account, like web search and your connected tools. Channel tagging works differently: Claude acts under your organization’s identity, using the tools and access an admin set up for that channel, and the work is billed to your organization rather than to you.

在私信和助手面板中，Claude 具有你在自己的 Claude 账户里启用的能力，例如网络搜索和已连接的工具。频道标记则不同：Claude 以组织身份行动，使用管理员为该频道配置的工具和访问权限，费用由组织而非你个人承担。

Set up Claude Tag / 设置 Claude Tag

After the Claude app is installed, a Primary Owner or Owner sets up Claude Tag: provision Claude’s identity, connect your organization’s tools and repositories, and choose which channels Claude Tag can work in. People on your team don’t need to set up anything individually once a channel is ready. For the full walkthrough, see the Claude Tag setup guide.

安装 Claude 应用后，由主所有者或所有者设置 Claude Tag：配置 Claude 的身份、连接组织的工具和代码仓库，并选择 Claude Tag 可以在哪些频道中工作。频道就绪后，团队成员无需各自再做设置。完整演练见 Claude Tag 设置指南。

Important: Only a Primary Owner or Owner can set up Claude Tag’s access and channels. The Admin role can’t.

重要： 只有主所有者或所有者可以设置 Claude Tag 的访问权限和频道。Admin 角色无法完成这项设置。

Control who can use Claude Tag / 控制谁可以使用 Claude Tag

In Organization settings > Claude Tag, Member Access has three modes: open to anyone in the Slack workspace, open to any member of your Claude organization, or only members whose role allows it. The third option is role-based access and is available on the Claude Enterprise plan. To restrict by role, set Member Access to “Only members whose role allows it” and grant the “Claude Tag in Slack” capability to a custom role. This setting applies to both channel mentions and direct messages. To set member access, see Restrict where Claude Tag operates.

在组织设置 > Claude Tag 中，成员访问有三种模式：对 Slack 工作区中的任何人开放、对 Claude 组织的任何成员开放，或仅对其角色允许的成员开放。第三种是基于角色的访问，在 Claude Enterprise 计划中可用。要按角色限制，将成员访问设为 “Only members whose role allows it”，并向自定义角色授予 “Claude Tag in Slack” 能力。该设置同时作用于频道提及和私信。设置成员访问见 Restrict where Claude Tag operates。

Manage spend limits for Claude Tag / 管理 Claude Tag 的支出限额

Claude Tag is consumption-based, so spend is based on usage rather than the number of people. As a Primary Owner or Owner, you control it from the usage settings in your admin console.

Claude Tag 按用量计费，支出取决于使用量而非人数。作为主所有者或所有者，你可从管理控制台的用量设置中控制它。

Organization-wide limit: a hard cap on total Claude Tag spend across every channel. Spend can’t exceed it.
Per-channel limits: set a limit on any individual channel, on top of the organization-wide cap. New channels inherit a default limit.
Threshold alerts: admins are notified at 75% and 95% of any limit.
Usage analytics: a per-channel spend breakdown lives on the same page.
组织范围限额： 对所有频道 Claude Tag 总支出的硬性上限，支出不能超过它。
按频道限额： 在组织上限之上，为任意单个频道设置限额。新频道继承默认限额。
阈值告警： 任一限额达到 75% 和 95% 时通知管理员。
用量分析： 按频道的支出明细在同一页面。

Note: Work that would go over a limit is declined, never silently cut short. A blocked user can request more from their admin without leaving Slack, and the alert says whether the limit or the available balance caused the block.

注意： 会超出限额的工作会被拒绝，绝不会被静默截断。被拦住的用户可以不离开 Slack 向管理员申请更多额度；告警会说明是限额还是可用余额导致了阻止。

Tagging Claude in a channel is billed to your organization. Direct messages are billed to your own Claude account instead.

在频道中标记 Claude 的费用由组织承担。私信则由你自己的 Claude 账户承担。

To set limits, see Set spend limits for Claude Tag.

设置限额见 Set spend limits for Claude Tag。

Set access and permissions for Claude Tag / 为 Claude Tag 设置访问与权限

You decide what Claude Tag can reach by setting credentials and repository access at three levels. Each level inherits the permissions and memory of the one above it.

你通过在三个层级设置凭证和仓库访问，来决定 Claude Tag 能触及什么。每一级继承上一级的权限和记忆。

Organization-wide: credentials and repositories that apply everywhere Claude Tag is installed.
Workspace: access that applies to every public channel inside a Slack workspace. Inherits organization-wide permissions and memory.
Private channel: extra credentials or repositories on top of what the workspace already grants. Use a private channel to keep sensitive connections to a smaller group. For example, a channel set up for legal work keeps its tools and memory separate from an engineering channel.
组织范围： 适用于安装了 Claude Tag 的所有地方的凭证和仓库。
工作区： 适用于 Slack 工作区内每个公开频道的访问。继承组织范围的权限和记忆。
私有频道： 在工作区已授予内容之上追加的凭证或仓库。用私有频道把敏感连接限制在更小的群体。例如，为法务工作设置的频道，其工具和记忆与工程频道分开。

To configure access, see Claude Tag identity and access.

配置访问见 Claude Tag identity and access。

Channels with guests / 包含访客的频道

Channels that include Slack guests have a separate Allow Claude to respond to guests setting that controls whether Claude responds there, and what access Claude has when it does. Choose Restrict (the default, which blocks Claude from those channels entirely), Channel only (Claude replies, but while a guest is present it runs with channel-only access), or Allow (Claude replies with the full access configured for it, as in any other channel). For the full guide, see Restrict guest channels.

包含 Slack 访客的频道有单独的 “Allow Claude to respond to guests” 设置，用来控制 Claude 是否在那里回复，以及回复时拥有何种访问。可选 Restrict（默认，完全阻止 Claude 进入这些频道）、Channel only（Claude 会回复，但访客在场时只使用频道级访问），或 Allow（Claude 以为其配置的完整访问回复，与其他频道相同）。完整指南见 Restrict guest channels。

Review memory and activity for Claude Tag / 查看 Claude Tag 的记忆与活动

Claude Tag keeps context per channel and per workspace. Admins can view, edit, and delete that memory.

Claude Tag 按频道和工作区保留上下文。管理员可以查看、编辑和删除这些记忆。

An Audit view in Organization settings > Claude Tag > Audit lists every scheduled and one-time task across your organization in addition to all network calls made using Agent Identity. Each action is also traceable in the tool where it happened: posts come from the Claude app in Slack, and commits and pull requests show the Claude GitHub App as the author with a link back to the Slack thread that started them. In any channel, you can ask “@Claude what triggers do you have set up here?” to see and turn off standing work.

组织设置 > Claude Tag > Audit 中的审计视图列出组织内每一项计划任务和一次性任务，以及使用 Agent Identity 发出的所有网络调用。每个动作也能在发生它的工具里追溯：帖子来自 Slack 中的 Claude 应用，提交和拉取请求以 Claude GitHub App 为作者，并带有指回发起它们的 Slack 线程的链接。在任意频道中，可以问 “@Claude what triggers do you have set up here?” 来查看并关闭常驻工作。

Privacy and data / 隐私与数据

Data storage / 数据存储

Your Slack conversations with Claude remain separate from your Claude history, keeping work organized across platforms.

你与 Claude 的 Slack 对话与 Claude 历史记录保持分离，让工作在各平台之间保持有序。

Data visibility / 数据可见性

Conversations initiated in Slack are not visible in your Claude chat history.

在 Slack 中发起的对话，不会出现在 Claude 聊天历史中。

Conversations initiated in the Claude web app are not accessible in Slack.

在 Claude 网页应用中发起的对话，无法在 Slack 中访问。

Each platform maintains separate conversation histories.

每个平台维护各自独立的对话历史。

Data deletion / 数据删除

Conversations are automatically deleted from Claude within 30 days if you disconnect the integration or uninstall the app.

如果断开集成或卸载应用，对话会在 30 天内从 Claude 侧自动删除。

Your conversations in Slack follow your organization’s Slack retention policies.

你在 Slack 中的对话遵循组织的 Slack 保留策略。

Claude Tag memory / Claude Tag 记忆

Claude Tag remembers context to do its work, so channel and workspace memory is retained rather than discarded after each task. Memory and activity respect channel boundaries, and admins can review or delete what Claude remembers. Channel work is attributed to your organization’s Claude identity, while work done in a direct message runs on your own account.

Claude Tag 记住上下文以便完成工作，因此频道和工作区记忆会被保留，而不是在每个任务后丢弃。记忆和活动尊重频道边界，管理员可以审查或删除 Claude 记住的内容。频道工作归属于组织的 Claude 身份，私信中完成的工作则跑在你自己的账户上。

Frequently asked questions / 常见问题

How is Claude Tag different from the Claude in Slack I already use? / Claude Tag 与我已经在用的 Slack 中的 Claude 有何不同？

Claude Tag is the next generation of that experience, in the same place. The familiar ways of working still apply, and Claude can now do more: it remembers context across days, schedules its own follow-ups, checks in proactively, and acts under its own identity. An organization’s Primary Owner or Owner opts your organization in to move over.

Claude Tag 是同一位置上该体验的下一代。熟悉的工作方式仍然适用，而 Claude 现在能做更多：记住跨越数天的上下文、安排自己的跟进、主动检查，并以自己的身份行动。由组织的主所有者或所有者选择让组织迁过去。

Who can set up Claude Tag, and who pays for it? / 谁可以设置 Claude Tag，费用由谁承担？

Only an organization’s Primary Owner or Owner can set up Claude Tag’s access and channels. Tagging Claude in a channel is billed to your organization. Direct messages are billed to the person’s own Claude account instead.

只有组织的主所有者或所有者可以设置 Claude Tag 的访问权限和频道。在频道中标记 Claude 的费用由组织承担。私信则由该人自己的 Claude 账户承担。

2.4 - Work with Claude Tag

官方文档 Work with Claude Tag 的中英对照

来源： Work with Claude Tag
状态： Public Beta

Work with Claude Tag / 使用 Claude Tag

Claude Tag puts Claude in your Slack channels with admin-governed access. See what to hand it, how setup works, and where to start as an admin or end user.

Claude Tag 把 Claude 放进 Slack 频道，访问由管理员治理。本文说明可以交给它什么、如何配置，以及管理员和终端用户该从哪里开始。

Tag @Claude in. Get results back in the thread.

把 @Claude Tag 进来。在线程里拿回结果。

Anyone in a channel can tag Claude into a problem and hand it work: reproduce a bug and open a pull request, turn a decision thread into a doc, assemble the state of a project. It posts a checklist in the thread as it goes, and the whole exchange stays visible to the channel.

频道里的任何人都可以把 Claude Tag 进一个问题并交给它工作：复现缺陷并开出拉取请求、把决策线程写成文档、汇总项目现状。它会边做边在线程里发 checklist，整段交互对频道可见。

示例线程 / Example thread（#platform-eng）：

Dana: checkout has felt slow all morning — anyone else seeing it?
Leo: same. @Claude can you investigate? Compare latency against this morning’s deploy and find what’s causing it.
ClaudeAPP: On it. I’ll compare latency before and after the deploy, track down the cause, and report back here.
Done: Pulled p99 latency from Datadog / Diffed deploy 4f2c1 against main / Reproduced the slow query locally / In progress: Opening a pull request with the fix…

Dana：整个上午 checkout 都感觉很慢——还有人遇到吗？
Leo：一样。@Claude 你能查一下吗？对比今天早上那次部署的延迟，找出原因。
ClaudeAPP：收到。我会对比部署前后的延迟，定位原因，然后在这里回报。
完成：从 Datadog 拉取 p99 延迟 / 对比部署 4f2c1 与 main / 在本地复现慢查询 / 进行中：正在打开带修复的拉取请求…

Plans that include Claude Tag / 包含 Claude Tag 的计划

Claude Tag is available on Team and Enterprise plans, on Anthropic’s first-party service. It isn’t available on individual plans (Free, Pro, or Max), or for third-party deployments. To use it, your organization pairs its Slack workspace with its Claude organization; see the setup overview for the full prerequisites.

Claude Tag 在 Anthropic 第一方服务的 Team 和 Enterprise 计划中可用。个人计划（Free、Pro 或 Max）以及第三方部署不可用。要使用它，组织需要将 Slack 工作区与 Claude 组织配对；完整前置条件见 setup overview。

If you’re choosing between Claude products for Slack-shaped work, how Claude Tag differs from Cowork and Claude Code compares them directly: team work in shared channels is Claude Tag; personal work on your own files is Cowork or Claude Code.

如果要在面向 Slack 形态的工作里选择 Claude 产品，how Claude Tag differs from Cowork and Claude Code 有直接对比：共享频道里的团队工作用 Claude Tag；个人文件上的工作用 Cowork 或 Claude Code。

Where Claude Tag runs / Claude Tag 运行在哪里

Claude Tag works in Slack. You interact with it by writing in a Slack channel, thread, or direct message, and it replies there. Mention @Claude in a channel to guarantee it picks the message up.

Claude Tag 在 Slack 中工作。你在频道、线程或私信里写，它就在那里回复。在频道中提及 @Claude，可以确保它收到这条消息。

When Claude works on a task, it runs in an ephemeral sandbox, not on your computer. The sandbox is created when a conversation starts, holds any code or files Claude is working with, and is discarded when the conversation goes idle. See how Claude Tag works for the full lifecycle.

Claude 处理任务时，运行在短暂沙箱里，而不是你的电脑上。对话开始时创建沙箱，容纳 Claude 正在处理的代码或文件，对话空闲后丢弃。完整生命周期见 how Claude Tag works。

You extend what Claude can reach, like your repositories, ticketing systems, data warehouses, and custom tools, through connections, plugins, and skills. An Owner configures these per scope (a channel, a workspace, or the whole organization), separately from any connectors an individual user has set up in their own claude.ai account.

通过 connections、plugins 和 skills，扩展 Claude 能触及的范围，例如仓库、工单系统、数据仓库和自定义工具。由 Owner 按 scope（一个频道、一个工作区或整个组织）配置，与个人用户在自己的 claude.ai 账户里设置的连接器相互独立。

For administrators / 给管理员

Set up Claude Tag — Pair your Slack workspace, connect the services Claude will work in, launch, and test that it works.
What can Claude Tag access? — How admins set access per channel, and where credentials are stored.
How do I connect each service? — Credential types, allowed hosts, and what each connection lets Claude reach.
设置 Claude Tag — 配对 Slack 工作区，连接 Claude 将使用的服务，上线并测试。
Claude Tag 能访问什么？ — 管理员如何按频道设置访问，以及凭证存放在哪里。
如何连接各个服务？ — 凭证类型、允许的主机，以及每个连接让 Claude 能触及什么。

For end users / 给终端用户

How do I hand Claude Tag a task? — Mention Claude in any channel it’s in, with nothing to install.
What is Claude Tag good at? — Use cases for coding, data, incidents, and go-to-market.
How do I get good results? — Good habits for scoping and reviewing work.
What does Claude Tag remember? — Channel memory, what’s shared across the workspace, and who can see what.
Can Claude Tag run tasks on a schedule? — Scheduled jobs, channel watching, and triggers.
如何交给 Claude Tag 一项任务？ — 在它已在的任意频道里提及 Claude，无需再安装任何东西。
Claude Tag 擅长什么？ — 编码、数据、事故与市场落地用例。
如何拿到好结果？ — 界定范围与审阅工作的好习惯。
Claude Tag 记住什么？ — 频道记忆、跨工作区共享什么、谁能看见。
Claude Tag 能按日程跑任务吗？ — 计划任务、盯频道与触发器。

Billing and spend limits / 计费与支出限额

Adding Claude to Slack doesn’t add a per-seat charge. Channel and thread work is billed by usage instead: it draws from a usage balance, an amount in your organization’s billing currency that an Owner funds. A spend limit caps how much of that balance Claude Tag can use each billing period.

把 Claude 加进 Slack 不会额外按席位收费。频道和线程工作按用量计费：从 Owner 注入的用量余额中扣减（以组织账单货币计）。spend limit 限制每个账期内 Claude Tag 最多能用掉多少余额。

Direct messages don’t draw from this balance. A DM runs on the sender’s own claude.ai account and follows that seat’s usual usage limits, so the organization spend limit doesn’t apply to it.

私信不从这笔余额扣。DM 跑在发送者自己的 claude.ai 账户上，遵循该席位通常的用量限制，因此组织 spend limit 对它不适用。

To learn what your team’s usage costs, run a pilot with a spend limit set and watch the per-channel breakdown on the usage page in your admin settings. Your organization may already have a launch usage credit to run that pilot against before it funds the balance itself.

要了解团队用量成本，先设好 spend limit 做试点，并在管理设置的用量页观察按频道明细。组织可能已有上线试用额度，可在自行注入余额之前先拿它跑试点。

Set a spend limit covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.

Set a spend limit 说明各计划如何注入余额、如何设限，以及用量触达限额时会发生什么。

Put Claude Tag to work / 让 Claude Tag 开始干活

If Claude Tag is in your channel, you can use it now. (If it isn’t there yet, an Owner in your Claude organization runs setup: see Set up Claude Tag.) Anyone in the channel can hand it work, and channel work bills to the organization, not to you.

如果 Claude Tag 已在你的频道里，现在就可以用。（若还没有，由 Claude 组织中的 Owner 完成设置：见 Set up Claude Tag。）频道里的任何人都可以交给它工作，频道工作记在组织账上，而不是你个人。

What it can reach depends on the channel you’re in, not on who you are. The fastest way to find out is to ask it: @Claude what can you access from this channel? Or, if you’re signed in to your Claude organization, click Configure in the footer of a Claude reply in the channel to see its connections, the external services an admin has connected for that channel. Replies in org-shared channels have no Configure link.

它能触及什么，取决于你所在的频道，而不是你是谁。最快的办法是问它：@Claude what can you access from this channel? 或者，若已登录 Claude 组织，点击频道里 Claude 回复页脚的 Configure，查看管理员为该频道连接的外部服务。组织共享频道里的回复没有 Configure 链接。

The one exception is a DM, where it runs on your own claude.ai account instead of the channel’s setup. Owners can disable DMs organization-wide; see Allow or disable direct messages.

唯一例外是私信：它跑在你自己的 claude.ai 账户上，而不是频道配置。Owner 可以在全组织禁用私信；见 Allow or disable direct messages。

Common uses / 常见用途

The list below covers common ways teams use Claude Tag. Each link opens a guide with the prompts to paste and the connections the task needs.

下面列出团队使用 Claude Tag 的常见方式。每个链接打开一篇指南，含可粘贴的提示词以及该任务所需的连接。

Watch monitors and alerts: scheduled dashboard checks, and alerts investigated as they arrive. Needs a monitoring connection like Datadog, Sentry, or PagerDuty.
Triage requests: an intake channel where Claude answers what it can, flags duplicates, and routes the rest. Works on Slack content alone.
Find answers in your docs: policy and runbook questions answered with the source. Needs a docs connection like Google Drive, Notion, or Confluence.
Answer data questions: a plain-language question becomes a warehouse query and a chart. Needs a data warehouse connection.
Track projects and chase approvals: standing status digests and follow-ups that run until an approval lands.
Turn threads into docs and tickets: a settled discussion becomes the decision doc, the customer reply, or the filed tickets.
Fix bugs: a bug reported in the channel comes back as a draft pull request. Needs GitHub.
Work from your own channel: scratch questions, digests of channels you don’t follow, and follow-ups on what you said you’d do.
盯监控与告警：定时检查仪表盘，告警一到就调查。需要 Datadog、Sentry 或 PagerDuty 一类监控连接。
分诊请求：接入频道里 Claude 能答的先答、标重复、其余再路由。仅凭 Slack 内容即可工作。
在文档里找答案：政策与 runbook 问题带来源作答。需要 Google Drive、Notion 或 Confluence 一类文档连接。
回答数据问题：自然语言问题变成数仓查询和图表。需要数据仓库连接。
跟踪项目并催办审批：常驻状态摘要，以及一直跟到审批落地的催办。
把线程变成文档和工单：已经谈定的讨论变成决策文档、客户回复或已提交工单。
修缺陷：频道里报的缺陷，回来时是草稿拉取请求。需要 GitHub。
在自己的频道里工作：随手问题、你没在跟的频道摘要，以及对你说过要做之事的跟进。

Get started covers your first message, what you see while Claude works, and how to shape Claude’s behavior in your channel.

Get started 覆盖第一条消息、Claude 工作时你看到什么，以及如何塑造它在频道里的行为。

Set Claude Tag up once for everyone / 为所有人设置一次 Claude Tag

You set up Claude Tag once, at claude.ai/admin-settings/claude-tag, and you must be an Owner in your Claude organization to do it. The setup page at that URL walks you through it:

Claude Tag 只需设置一次，入口是 claude.ai/admin-settings/claude-tag，且必须是 Claude 组织中的 Owner。该页会带你走完：

Pair your Slack workspace: send @Claude connect in Slack to get a pairing code, then enter it on the setup page.
Connect the services Claude will work in: for each one, such as your issue tracker or data warehouse, create an account for Claude and enter its credential.
Grant repositories: choose which repositories the Claude GitHub App can reach.
Set a monthly spend limit and launch.
配对 Slack 工作区：在 Slack 发送 @Claude connect 拿到配对码，再填到设置页。
连接 Claude 将使用的服务：对工单系统或数据仓库等每一个服务，为 Claude 创建账号并填入凭证。
授予仓库：选择 Claude GitHub App 能触及哪些仓库。
设定每月花费上限并上线。

Claude Tag starts with no access to your external systems. The services you connect during setup form an Access bundle, the set of tools Claude can reach, attached to the workspace or channels you paired. Once you launch, everyone in a channel Claude is in can use Claude Tag immediately, with no per-user setup.

Claude Tag 一开始不能访问任何外部系统。设置时连接的服务构成 Access bundle——Claude 能触及的工具集合——并绑到你配对的工作区或频道。上线后，Claude 所在频道里的所有人都能立刻使用，无需按人再配。

Set up Claude Tag walks through those steps with what to have ready, what each choice means, and how to verify Claude Tag works once you launch.

Set up Claude Tag 逐步说明要准备什么、每个选择意味着什么，以及上线后如何验证可用。

安全评审见 Security and data handling：安全模型、管理员能限制和不能限制什么、审计轨迹与网络要求。

Where to start with Claude Tag / 从哪里开始

Set up Claude Tag — Admins: pair your Slack workspace, connect the services Claude will work in, and launch.
Hand Claude Tag your first task — It’s already in your channel: send your first message.
How Claude Tag works — The session model, what it can read, and how memory follows places.
Use case library — Prompts to paste, by team and connection.
设置 Claude Tag — 管理员：配对 Slack 工作区，连接服务，然后上线。
交给 Claude Tag 第一项任务 — 它已在频道里：发出第一条消息。
Claude Tag 如何工作 — 会话模型、它能读什么、记忆如何跟随场所。
用例库 — 按团队与连接分类的可粘贴提示词。

3 - 运行机制

Claude Tag 运行机制：会话、身份、安全与设置

本栏按资料列表第二阶段（编号 6–13），存放原文的中英对照。完整编号清单见概述。栏目结构对齐介绍。

How Claude Tag works（会话、沙箱、转向、记忆范围）
Glossary（Access bundle、Agent Proxy、scope、routine、channel memory）
How agent identity works
Agent identity: a new access model（Noah Zweben，Claude Code 团队）
Security and data handling
Data lifecycle and deletion
Claude Tag settings map
Claude Tag for Claude Code users

建议按编号顺序读：先扫 Glossary，再进身份模型与安全。

3.1 - How Claude Tag works

官方文档 How Claude Tag works 的中英对照：会话、沙箱、转向、记忆范围

来源： How Claude Tag works

How Claude Tag works / Claude Tag 如何工作

Each Claude Tag thread in Slack runs a working session in a sandbox. See how progress shows in the thread, how to steer mid-task, what survives between turns, and how memory is scoped.

每个 Claude Tag 线程都在沙箱里跑一个工作 session。本文说明进度如何出现在线程里、任务中途如何转向、回合之间什么会留下来，以及记忆如何划定范围。

Claude Tag is Claude, working inside your team’s Slack channels. An organization Owner gives it its own accounts to the tools your team uses, so it arrives already able to act, and anyone in a channel can tag it into a problem without setting anything up.

Claude Tag 就是在团队 Slack 频道里工作的 Claude。组织 Owner 给它配好团队所用工具的独立账号，所以它一到就能动手；频道里任何人都可以把它 Tag 进一个问题，无需再配置。

When someone tags Claude in at a channel’s top level, the channel’s own session picks the message up. A task that needs investigation, tools, or a longer exchange gets a working session in a thread under the message, and that thread binds to its own session from then on. Claude works through the task and posts the result back into the conversation. The work runs in an ephemeral cloud sandbox, not on your local machine.

有人在频道顶层 Tag Claude 时，由该频道自己的 session 接住这条消息。需要调查、工具或较长往返的任务，会在该消息下开一个线程工作 session，此后该线程就绑定这个 session。Claude 做完任务，把结果发回对话。工作跑在短暂的云端沙箱里，而不是你的本机。

This page covers:

本文覆盖：

Walk through a session: an annotated example thread showing one task end to end
Starting a session, tracking progress, and steering mid-thread: what to type, what to watch, and who can redirect
Team channels and personal DMs: which surface to use, and how access differs between them
Key concepts: agent identity, scheduling, and memory defined
Lifecycle of a request: the five-step loop, the checklist, per-channel access, and scheduled tasks
Session context and memory: what Claude reads, what survives idle, and what carries across channels
走一遍 session：带注释的示例线程，展示一项任务从头到尾
开始 session、跟踪进度、线程中途转向：写什么、看什么、谁能改方向
团队频道与个人私信：用哪一面，访问如何不同
关键概念：agent identity、调度、记忆
一次请求的生命周期：五步循环、checklist、按频道访问、计划任务
Session 上下文与记忆：Claude 读什么、空闲后留下什么、什么跨频道带走

Walk through a Claude Tag session / 走一遍 Claude Tag session

The thread below is one task end to end in Slack: Jordan tags @Claude into #launch-week with a question, a colleague steers mid-thread, and the answer lands in the channel.

下面这段线程是 Slack 里一项任务的全过程：Jordan 在 #launch-week 里 @Claude 提问，同事在线程中途转向，答案落回频道。

示例线程 / Example thread（#launch-week，19 members）：

Jordan 9:02 AM
@Claude where are we on launch prep? Pull together what’s still open from this channel.

ClaudeAPP 9:02 AM
On it. I’ll go through this channel’s open threads and the launch plan.
Done: Read 14 open threads
Done: Cross-checked the launch plan in Drive
Done: Listed who each item is waiting on
Done: Drafted the status summary

Sam 9:06 AM
fold in the vendor quotes from last week’s thread too

ClaudeAPP 9:08 AM
Done. Full status below: eight items closed, three open. The venue contract is the oldest, waiting on legal since the 2nd.

Jordan 9:02 AM
@Claude 发布准备做到哪了？把这个频道里还开着的事项汇总一下。

ClaudeAPP 9:02 AM
收到。我会过一遍本频道未关闭的线程和发布计划。
完成：读了 14 个未关闭线程
完成：对照了 Drive 里的发布计划
完成：列出每项在等谁
完成：起草了状态摘要

Sam 9:06 AM
把上周线程里的供应商报价也折进去

ClaudeAPP 9:08 AM
好了。完整状态如下：八项已关，三项仍开。场馆合同最老，从 2 号起就在等法务。

Each of the five moments in that thread shows a piece of how Claude Tag works:

这条线程里的五个时刻，各对应 Claude Tag 工作方式的一块：

Jordan handed Claude a problem, not a prompt. Typing @Claude in a message that asks for something is what starts a working session.
Claude acknowledged, then went quiet. The “is thinking…” line and the checklist are the progress surface; the silence between 9:02 and 9:06 was the work happening. How the checklist updates
Sam steered Claude without @-mentioning it again. Once a session is active in a thread, it belongs to everyone there. Reply in the thread to steer
The work ran somewhere real, with the channel’s tools. Reading fourteen threads happened in a sandbox built for this thread, and the launch plan came through this channel’s Drive connection. What a session can reach is set per channel. Channel access
The result is in the thread. The whole channel can see it, use it, and build on it. What survives between replies
Jordan 交给 Claude 的是一个问题，不是一段提示词。在一条提出需求的消息里写 @Claude，就会开始工作 session。
Claude 先应答，然后安静。线程底部的 “is thinking…” 和 checklist 才是进度面；9:02 到 9:06 的沉默就是在干活。How the checklist updates
Sam 没有再次 @ 就转向了 Claude。session 一旦在线程里激活，就属于线程里所有人。Reply in the thread to steer
工作发生在真实环境里，用的是频道的工具。读十四个线程是在为本线程建的沙箱里完成的，发布计划来自该频道的 Drive 连接。session 能触及什么按频道设定。Channel access
结果在线程里。整个频道都能看见、使用、接着往上做。What survives between replies

The rest of this page takes each piece apart.

后文把每一块拆开讲。

Start a session / 开始一个 session

To start a session, type @Claude in a Slack message and say what you need in that same message (a question to answer, a task to run, a problem to dig into). Jordan’s “@Claude where are we on launch prep?” is the whole move. Anyone in the channel can do it.

要开始 session，在一条 Slack 消息里写 @Claude，并在同一条消息里说出你要什么（要答的问题、要跑的任务、要挖的问题）。Jordan 那句 “@Claude where are we on launch prep?” 就是完整动作。频道里任何人都可以做。

Track Claude’s progress / 跟踪 Claude 的进度

Once your message sends, an “is thinking…” line at the bottom of the thread means Claude picked it up. What happens next depends on the size of the ask. Questions and one-off requests get a direct reply. A longer task, like Jordan’s, gets a checklist instead. How the checklist updates covers how it works and how to read one while it runs.

消息发出后，线程底部出现 “is thinking…” 表示 Claude 已经接住。接下来取决于请求大小。问题和一次性请求会直接回复。更长的任务（如 Jordan 的）会改用 checklist。How the checklist updates 说明它如何工作、运行时如何读。

While a session runs, check in by replying in the same thread. Asking “how’s it going?” in the thread is enough; it reads new replies as it works.

session 运行期间，在同一线程里回复即可过问。问一句 “how’s it going?” 就够；它边干活边读新回复。

Reply in the thread to steer / 在线程里回复以转向

Anyone in the channel can steer a running session by replying in its thread, not just the person who started it. That is what Sam did in the walkthrough. Without re-mentioning @Claude or starting over, he replied in Jordan’s thread, and the session folded his instruction into work already in progress. Add context, redirect the approach, or pick up the result later; a colleague’s thread is yours to continue.

频道里任何人都可以在线程里回复来转向正在跑的 session，不只是发起人。演示里 Sam 就是这样做的。他没有再 @Claude，也没有重开，只是在 Jordan 的线程里回复，session 就把他的指示折进已经在进行的工作。补充上下文、改方向、稍后接结果都可以；同事的线程你也可以继续。

Editing or deleting an earlier message doesn’t steer the session the way a reply does:

编辑或删除更早的消息，并不能像回复那样转向 session：

Editing a message: Claude receives a note each time you edit, showing what the message said before the edit and what it says now. Both versions become part of the session’s transcript, so editing a message doesn’t remove the earlier text from what Anthropic stores. An edit doesn’t start a new task or re-address Claude, even if you add @Claude to it.
Deleting a reply: Claude gets no notification and keeps the version it already read. Deleting the reply in Slack doesn’t remove it from the session’s transcript.
Deleting the thread’s first message: if the thread already has replies, Claude keeps working and the session stays open. If you delete it before anyone has replied, the session closes. Anything Claude already pushed or posted persists, per what survives between replies, and you start a new thread to pick the task back up. Closing the session archives it rather than deleting it, so its transcript, including the message you deleted, stays with the channel’s Claude data until that data is deleted.
Correcting course: Claude responds to replies; edits reach it only as notes, and a deleted reply not at all. Say the change in a new reply; the reply is also how you walk back a message it already read.
编辑消息：每次编辑 Claude 都会收到一条说明，展示编辑前和编辑后的文本。两个版本都会进入 session transcript，所以编辑并不能从 Anthropic 存储里抹掉更早的文字。编辑不会开新任务，也不会重新呼叫 Claude，即使你在编辑里加上 @Claude。
删除一条回复：Claude 收不到通知，继续保留它已经读过的版本。在 Slack 里删回复，并不会从 session transcript 里删掉它。
删除线程的第一条消息：若线程已有回复，Claude 继续干活，session 保持打开。若在任何人回复之前删除，session 关闭。Claude 已经推送或发出的内容会按回复之间留下什么保留，你需要开新线程把任务捡回来。关闭 session 是归档而不是删除，因此 transcript（包括你删掉的那条消息）会跟着该频道的 Claude 数据，直到那些数据被删除。
纠正方向：Claude 响应的是回复；编辑只作为说明到达，已删的回复则完全不到。把变更写在一条新回复里；撤回它已经读过的消息，同样靠回复。

Team channels and personal DMs / 团队频道与个人私信

Where you message Claude determines whose tools and accounts it uses. In a channel, it acts with the connections an organization admin set for that channel, and the work is attributed to its own accounts. In a DM, the same engine runs with your own claude.ai connectors, and the work is attributed to you, except pull requests, which the Claude GitHub App authors from DMs as well.

你在哪里给 Claude 发消息，决定它用谁的工具和账号。在频道里，它使用组织管理员为该频道配置的 connections，工作记在它自己的账号上。在私信里，同一套引擎跑在你自己的 claude.ai connectors 上，工作记在你名下；例外是拉取请求：从私信开出的 PR 同样由 Claude GitHub App 署名。

Working in…	Access	Attribution	Best for
A channel	The channel’s connections, set by an admin	The agent’s own accounts	Shared work the team should see
A DM	Your own claude.ai connectors	You	Personal tasks using your own data

工作地点	访问	归属	适合
频道	管理员为该频道设置的 connections	agent 自己的账号	团队应看见的共享工作
私信	你自己的 claude.ai connectors	你	使用个人数据的私事

The Access column is about external systems. A channel session reaches what the channel was granted, and a DM session reaches what your own account is connected to.

Access 列说的是外部系统。频道 session 能触及频道被授予的范围，私信 session 能触及你自己账户已连接的范围。

Everything below describes channel sessions, where most of the model lives. For the DM side, see direct message channels; for choosing between the two, see pick the right surface.

以下全部描述频道 session——模型的主体在这里。私信一侧见 direct message channels；两者如何选，见 pick the right surface。

How Claude Tag differs from Cowork and Claude Code / Claude Tag 与 Cowork、Claude Code 的差别

Anthropic offers several ways to work with Claude on real tasks; they reach the same kinds of systems but through different mechanisms.

Anthropic 提供多种方式让 Claude 做真实任务；它们能触及同类系统，但机制不同。

	Claude Tag	Cowork	Claude Code
Where	Slack channels	claude.ai chat	Your terminal or IDE
Whose access	The team’s: service-account credentials an admin sets per channel	Yours: your personal OAuth connectors	Yours: your local credentials and filesystem
Who sees the work	Everyone in the channel	Just you	Just you
Best for	Shared work the team should see and steer	Personal research and drafting	Hands-on coding in your own checkout

	Claude Tag	Cowork	Claude Code
在哪里	Slack 频道	claude.ai 聊天	你的终端或 IDE
谁的访问	团队的：管理员按频道设置的服务账号凭证	你的：个人 OAuth connectors	你的：本机凭证和文件系统
谁看见工作	频道里所有人	只有你	只有你
适合	团队应看见并转向的共享工作	个人研究与起草	在自己 checkout 里动手写代码

The short version: team work → Claude Tag; personal work → Cowork or Claude Code. Claude Tag’s connections authenticate the agent itself with service accounts, not any person. Personal connectors apply in a Claude Tag DM, which runs on your own claude.ai account, the same way Cowork does.

短版：团队工作 → Claude Tag；个人工作 → Cowork 或 Claude Code。Claude Tag 的 connections 用服务账号认证的是 agent 自身，不是某个人。个人 connectors 只在 Claude Tag 私信里生效，私信跑在你自己的 claude.ai 账户上，和 Cowork 一样。

Key concepts / 关键概念

Three ideas recur across this page and the rest of these docs.

三个概念在本页和其余文档里反复出现。

Agent identity: in channels, Claude acts under its own service accounts that an admin provisions, not as the person who asked. What it can reach is set per channel, so everyone in a channel works with the same access. See How agent identity works.
Scheduling and long-running work: a task can run on a schedule, follow a pull request and act when it changes, or keep going across many turns in one thread. The same channel access applies whether a person or a schedule started it. See Set up routines.
Memory: what Claude learns in public channels is saved as workspace memory that any channel can use; private channels keep their own. See What Claude remembers.
Agent identity： 在频道里，Claude 以管理员配好的自己的服务账号行事，而不是提问的那个人。能触及什么按频道设定，所以频道里所有人用同一套访问。见 How agent identity works。
调度与长时工作： 任务可以按日程跑、跟一个拉取请求并在它变化时行动，或在同一线程里跨许多回合继续。无论是人还是日程启动，都用同一套频道访问。见 Set up routines。
记忆： Claude 在公开频道里学到的内容存为工作区记忆，任意频道都能用；私有频道保留自己的。见 What Claude remembers。

Lifecycle of a request / 一次请求的生命周期

Every session, in any channel, follows the same five-step loop.

任意频道里的每个 session，都走同一套五步循环。

The session starts. Someone tags @Claude with a task that needs a working session, or a scheduled routine runs. At a channel’s top level, the channel’s own session picks the message up and starts the thread’s session.
A sandbox builds. Each thread gets its own isolated working environment.
The working loop runs. Claude works through the task with the channel’s access, editing its checklist in place.
The result lands in the thread. An answer, a doc, a chart, or a pull request.
A quiet period follows. The sandbox is released while the thread persists; a new reply rebuilds it and starts the loop again.
Session 开始。有人用 @Claude Tag 一项需要工作 session 的任务，或一条计划好的 routine 跑起来。在频道顶层，频道自己的 session 接住消息并启动该线程的 session。
沙箱建起。每个线程有自己的隔离工作环境。
工作循环运行。Claude 用频道的访问把任务做完，并就地改 checklist。
结果落在线程里。一个答案、一份文档、一张图，或一个拉取请求。
随后是安静期。线程还在，沙箱被释放；新回复会重建沙箱并再开循环。

Steps 1 and 2 are starting a session: a message tags Claude in, and a sandbox builds for that thread. Step 3, the working loop, is the checklist below. Steps 4 and 5, the result and the quiet period that follows, are covered in What survives between replies.

第 1、2 步就是开始 session：一条消息把 Claude Tag 进来，并为该线程建沙箱。第 3 步工作循环就是下面的 checklist。第 4、5 步——结果和随后的安静期——见回复之间留下什么。

Every session runs in an ephemeral sandbox, a real working environment where Claude can read documents, run code, build charts, and open pull requests. Claude clones your GitHub repositories into the sandbox, edits them there, and pushes changes back to GitHub as a branch or pull request. The sandbox runs the same engine that powers Claude Code on the web, Anthropic’s agent for writing and running code, which is why the results are working artifacts rather than chat.

每个 session 都跑在短暂沙箱里——真实的工作环境，Claude 可以读文档、跑代码、做图、开拉取请求。Claude 把 GitHub 仓库克隆进沙箱，在里面改，再作为分支或拉取请求推回 GitHub。沙箱跑的是驱动 Claude Code on the web 的同一套引擎（Anthropic 用于写代码、跑代码的 agent），所以结果是可工作的产物，而不只是聊天。

Two threads in the same channel are two separate sessions with separate sandboxes; sessions don’t share state directly.

同一频道里的两个线程是两个独立 session、两套沙箱；session 之间不直接共享状态。

A channel where Claude works at the top level, outside threads, also carries one session for the channel itself, separate from every thread’s. That session reads the channel’s top-level messages and handles top-level @-mentions, so context carries across separate top-level asks in the same channel; What survives between replies covers how long it lives. For a task that needs investigation, tools, or a longer exchange, it starts a dedicated session in a thread under the message. At the channel’s top level, !restart replaces the channel’s session.

Claude 在频道顶层（线程之外）工作时，频道本身也带着一个 session，与每个线程的 session 分开。那个 session 读频道顶层消息、处理顶层 @提及，因此同一频道里分开的顶层请求可以带着上下文；它活多久见回复之间留下什么。需要调查、工具或较长往返的任务，会在该消息下的线程里开专用 session。在频道顶层，!restart 会替换频道的 session。

Even with nothing connected, every session starts from the same baseline.

即使什么都没连接，每个 session 也从同一基线开始。

It reads its own thread and the channel’s history, including pinned items
It searches the workspace’s content
It writes and runs code inside the sandbox, which is how a chart comes out of a posted CSV, or a doc out of a long thread, with nothing wired up
读自己的线程和频道历史，包括钉选
搜索工作区内容
在沙箱里写代码、跑代码——所以贴一份 CSV 能出图，长线程能出文档，不必先接线

What Claude posts back / Claude 回帖什么

Claude posts each session’s result in the thread you asked in, choosing the form that fits the work.

Claude 把每个 session 的结果发在你提问的线程里，并选择适合这项工作的形态。

Form	What it is	When you see it
A reply	An answer, list, or summary as a Slack message	Questions and short results
A file or chart	Attached to the thread the way anyone shares a file	Data, images, generated documents
A page kept current	Any of the above, edited in place over time	Digests, indexes, standing reports
A hosted page	A web page published on claude.ai, linked in the thread	Dashboards, prototypes, reports

形态	是什么	何时见到
回复	作为 Slack 消息的答案、列表或摘要	问题和短结果
文件或图表	像任何人分享文件一样附在线程上	数据、图像、生成的文档
保持更新的页面	以上任意一种，随时间就地编辑	摘要、索引、常驻报告
托管页面	发布在 claude.ai 上的网页，链接在线程里	仪表盘、原型、报告

A hosted page stays available after the session ends, and Claude updates it when you ask in the thread. Anyone with access to the channel can open it; artifact visibility covers the access model. These are the same artifacts Claude Code publishes, with channel-based access in place of owner-controlled sharing.

托管页面在 session 结束后仍然可用，你在线程里要求时 Claude 会更新它。能进该频道的人都能打开；访问模型见 artifact visibility。这些与 Claude Code 发布的 artifacts 相同，只是用基于频道的访问，代替由所有者控制的分享。

For code work, the result is usually a draft pull request opened under the Claude GitHub App, with the link posted in the thread.

代码工作的结果通常是 Claude GitHub App 名下开出的草稿拉取请求，链接发在线程里。

How the checklist updates / checklist 如何更新

For a longer task, Claude’s first reply is a checklist, a live task list that it edits in place as it goes. Slack does not send notifications when a message is edited, so the thread can look frozen while the list is still moving.

更长的任务里，Claude 的第一条回复是 checklist——一份它边做边就地改的实时任务列表。Slack 不会在消息被编辑时发通知，所以列表还在动时，线程看起来可能像冻住了。

A quiet thread usually means Claude is mid-task, not stuck. Open the thread. Checklist items checked off since you last looked mean the work is moving. In the walkthrough, nothing new arrived in anyone’s notifications between 9:02 and 9:06, while the checklist ticked through fourteen threads of reading. If the work hits a wall, Claude usually says so in a reply rather than going silent. When a thread stays silent well past what the task should need, treat it as a stuck session; see Claude reacted or started thinking, then never replied.

安静的线程通常表示 Claude 正在干活，而不是卡住。打开线程。自你上次看过后又勾掉的 checklist 项，说明工作在推进。演示里，9:02 到 9:06 谁的通知里都没有新消息，同时 checklist 正在勾完十四个线程的阅读。若工作撞墙，Claude 通常会用回复说明，而不是一直沉默。线程安静的时间远超任务该花的时间，就当作卡住的 session；见 Claude reacted or started thinking, then never replied。

Channel access / 频道访问

Connections extend a session’s reach into your own systems. An organization admin attaches access to a scope (the organization, a workspace, or a single channel), so the same request can do more in one channel than in another, and everyone in a given channel works with the same capability.

Connections 把 session 的触及范围扩到你们自己的系统。组织管理员把访问绑到一个 scope（组织、工作区或单个频道），因此同一请求在某个频道能做的比在另一个频道多，而给定频道里所有人能力相同。

A thread locks in its skills, plugins, and custom instructions when it starts, and a running thread keeps that set. Connections and domain rules are enforced on each request, so one an admin adds mid-thread works in a running thread. Claude doesn’t announce a new connection in an existing thread; ask it to use the service by name. A new thread picks up every kind of change, so after a configuration change, start a new top-level thread.

线程启动时锁定其 skills、plugins 和自定义指令，正在跑的线程保持这一套。Connections 和域名规则按每次请求强制执行，因此管理员在线程中途加上的连接，对正在跑的线程也生效。Claude 不会在已有线程里宣布新连接；用服务名请它去用。新线程会接上所有种类的变更，所以改完配置后，开一个新的顶层线程。

How to identify access / 如何确认访问范围

Because access is set per channel rather than per person, the way to find out what a session can reach is to ask it, not to guess from your own permissions.

因为访问按频道而不是按人设定，要知道 session 能触及什么，去问它，而不是从你自己的权限去猜。

Ask what Claude can reach. In any channel, @Claude what can you access from this channel? lists its current reach.
If Claude cannot reach something, the channel was not granted access. Another channel may have the access, and an organization Owner can add it. How agent identity works covers the model.
Personal connectors apply only in DMs. A connection an admin attaches to a channel is separate from a connector on your personal claude.ai account; anything on your own account works in your DMs, not here.
问 Claude 能触及什么。在任意频道发 @Claude what can you access from this channel?，会列出当前范围。
若 Claude 够不到某样东西，是这个频道没被授予访问。另一个频道可能有，组织 Owner 可以加上。模型见 How agent identity works。
个人 connectors 只在私信里生效。管理员绑到频道的 connection，与你个人 claude.ai 账户上的 connector 分开；你自己账户上的东西在私信里可用，这里不行。

One-off and scheduled tasks / 一次性任务与计划任务

A session starts the same way whether a person triggers it or a schedule does. A tagged task runs in its thread’s session, and the sandbox is released once the work finishes. A routine runs the same loop on a schedule, a channel watch, or a repository event, with the channel’s connections, so a recurring digest or watcher gets the same access a typed request would. See set up routines.

无论是人触发还是日程触发，session 的启动方式相同。被 Tag 的任务跑在其线程的 session 里，做完后释放沙箱。routine 按日程、盯频道或仓库事件跑同一套循环，用的是频道的 connections，因此周期性摘要或看守者拿到的访问，与手打请求相同。见 set up routines。

Session context and memory / Session 上下文与记忆

Every session runs the same lifecycle; what varies by place and thread is what it can see, what survives idle, and what it remembers.

每个 session 生命周期相同；随场所和线程变化的是它能看见什么、空闲后留下什么、记住什么。

Conversation context / 对话上下文

A session reads its own thread and its channel. Mentioning @Claude partway into an existing thread gives it a window of the thread’s messages, not the whole thread, with other bots’ replies filtered out. In long threads, restate anything critical.

session 读自己的线程和所在频道。在已有线程中途提及 @Claude，它拿到的是该线程消息的一个窗口，不是整条线程，其他机器人的回复会被滤掉。长线程里，关键内容请再陈述一遍。

Claude works in channels it has been added to, but workspace search can still find messages by keyword from public channels it’s not a member of (the same search any Slack user has). Workspace search is unavailable in channels that include guests. Finding something is broader than being able to act somewhere; to have it participate in a channel directly, invite it with /invite @Claude.

Claude 在已被加入的频道里工作，但工作区搜索仍能按关键词找到它不是成员的公开频道里的消息（与任意 Slack 用户拥有的搜索相同）。包含访客的频道里，工作区搜索不可用。找到某样东西，比能在某处行动更宽；要让它直接参与一个频道，用 /invite @Claude 邀请。

What survives between replies / 回复之间留下什么

A thread is durable, but the sandbox behind it is not. Durable means the thread stays in Slack, and everything Claude read and said in it is kept in the session’s transcript on Anthropic’s side, so the session can pick up where it left off whenever someone replies. Deleting messages or the thread in Slack doesn’t remove them from that transcript. The sandbox is the computer where Claude runs commands and keeps working files for a task. A few minutes after a session finishes its turn, its sandbox is released, and the same session resumes in a fresh one when the next message arrives. A thread’s session keeps resuming this way for as long as people use the thread. Claude replaces it with a new session in two cases.

线程是持久的，背后的沙箱不是。持久意味着线程留在 Slack 里，Claude 在其中读过和说过的一切，都保存在 Anthropic 侧的 session transcript 里，因此有人回复时 session 能从停下的地方接上。在 Slack 里删消息或删线程，并不会从那份 transcript 里抹掉。沙箱是 Claude 跑命令、为任务保留工作文件的那台计算机。session 完成本回合几分钟后，沙箱被释放；下一条消息到达时，同一 session 在全新沙箱里恢复。只要人们还在用这条线程，线程的 session 就会这样一直恢复。Claude 在两种情况下会换成新 session。

When	What Claude does
Someone sends `@Claude !restart`	Archives the session right away and starts a fresh one that rereads the thread
The session gets stuck and fails	Starts the replacement when the next message arrives in the thread

何时	Claude 做什么
有人发送 `@Claude !restart`	立刻归档当前 session，开一个重读该线程的新 session
session 卡住并失败	线程里下一条消息到达时启动替换

	Survives idle periods
The conversation and its context	Yes
Channel memory	Yes
Work pushed, posted, or opened as a PR	Yes, in the external system
Files that exist only in the sandbox	No. Claude recreates them if asked.

	空闲后是否留下
对话及其上下文	是
频道记忆	是
已推送、已发帖或已开成 PR 的工作	是，在外部系统里
只存在于沙箱里的文件	否。若被要求，Claude 会重建它们。

For long tasks, ask it to push branches and post drafts as it goes, so deliverables are saved somewhere durable while the work is still running. See Good habits.

长任务请让它边做边推分支、发草稿，这样交付物在工作还在跑时就已经落到持久的地方。见 Good habits。

A running thread isn’t told about configuration changes an admin makes after it started, such as a new connection, plugin, skill, repository grant, or custom instruction. A new thread starts from the scope’s current configuration, so after changing a scope, start a fresh thread to see the change.

正在跑的线程不会被告知管理员在它启动之后做的配置变更，例如新的 connection、plugin、skill、仓库授权或自定义指令。新线程从 scope 的当前配置开始，所以改完 scope 后，开一条新线程才能看到变更。

The channel’s own session, the one that handles top-level messages outside any thread, lives longer than a thread’s. Claude replaces it with a fresh one when a top-level message arrives after about an hour with no top-level activity, when the session is about a day old, or when the channel’s configuration has changed since the session started. Channel memory and the channel’s history are unaffected, so the only visible effect is that Claude no longer carries what the previous session had been working on.

频道自己的 session（处理线程之外的顶层消息）比线程的活得更久。出现以下情况时 Claude 会换成新的：约一小时没有顶层活动后到达一条顶层消息、session 大约一天了，或自 session 启动以来频道配置已变。频道记忆和频道历史不受影响，所以唯一可见的效果是 Claude 不再带着上一个 session 当时在做的事。

Claude also stops reading a channel’s top-level messages once about 100 of them have arrived since it last posted or replied there. An @Claude mention in the channel starts it reading again; see When Claude stops reading a channel. These thresholds are defaults and can change, so treat the numbers as approximate.

自从它上次在该频道发帖或回复以来，大约又到了 100 条顶层消息，Claude 也会停止阅读该频道的顶层消息。在频道里 @Claude 会让它重新开始读；见 When Claude stops reading a channel。这些阈值是默认值，可能变化，数字当作近似。

Channel and workspace memory / 频道记忆与工作区记忆

Memory follows places the same way access does, and it accumulates for the team rather than for any individual.

记忆像访问一样跟随场所，并且为团队累积，而不是为某个人。

Memory from public channels is shared across the workspace, so a decision recorded while working in #launch-week is available when someone asks in #gtm-west. When Claude cites something from a channel you have never used it in, it is reading workspace memory shared from that channel, not a profile of you.

公开频道的记忆在整个工作区共享，所以在 #launch-week 工作时记下的决定，有人在 #gtm-west 提问时也能用。当 Claude 引用一个你从未在其中用过它的频道里的内容时，它读的是从那个频道共享来的工作区记忆，不是你的个人档案。

Private channels read workspace memory while working, and what they save is written to that channel’s own store rather than the workspace store.

私有频道工作时会读工作区记忆，但它们保存的内容写到该频道自己的存储，而不是工作区存储。

To see what it holds, ask @Claude what do you remember about this channel?. Anyone in the channel can correct or remove entries. What Claude Tag remembers covers reading, correcting, and adding to memory.

要看它记了什么，问 @Claude what do you remember about this channel?。频道里任何人都可以纠正或删除条目。What Claude Tag remembers 覆盖读、纠正和向记忆里添加。

The whole model so far fits in one picture, with access set at the scope, memory shared from public channels, work in progress per thread, and DMs outside all of it.

至此整套模型可以收进一张图：访问设在 scope，记忆从公开频道共享，进行中的工作按线程，私信在这一切之外。

DMs are outside this picture; they run on your own account, as covered in Team channels and personal DMs above. Owners can disable DMs organization-wide; see Allow or disable direct messages.

私信在这张图之外；它们跑在你自己的账户上，见上文团队频道与个人私信。Owner 可以在全组织禁用私信；见 Allow or disable direct messages。

Getting started: hand Claude your first task
How agent identity works: why an admin sets access per channel, and how credentials stay out of the sandbox
Good habits: write tasks that survive the sandbox lifecycle
Getting started：把第一项任务交给 Claude
How agent identity works：管理员为何按频道设访问，以及凭证如何留在沙箱之外
Good habits：写出能熬过沙箱生命周期的任务

3.2 - Glossary

官方文档 Glossary 的中英对照：Access bundle、Agent Proxy、scope、routine、channel memory

来源： Glossary

Glossary / 术语表

Claude Tag terms defined in one place. See agent identity, Access bundle, channel manager, connection, scope, Agent Proxy, routine, channel memory, environment, and session.

Claude Tag 术语集中定义。见 agent identity、Access bundle、channel manager、connection、scope、Agent Proxy、routine、channel memory、environment 和 session。

Access bundle

A named set of connections, domain entries, repository access, and rules that an Owner creates for Claude to use. Bundles attach to scopes, and one bundle can serve many scopes. See Give Claude access.

Owner 为 Claude 创建的一套具名组合：connections、域名条目、仓库访问和规则。Bundle 绑到 scope 上，一个 bundle 可以服务许多 scope。见 Give Claude access。

Agent identity

The service accounts Claude acts with: the Claude app in Slack, the Claude GitHub App on code, and the credentials an admin provisions for every other tool. See How agent identity works.

Claude 据以行事的服务账号：Slack 里的 Claude 应用、代码侧的 Claude GitHub App，以及管理员为其他每个工具配好的凭证。见 How agent identity works。

Agent Proxy

The network layer that injects credentials into Claude’s outbound requests. The model and the sandbox are not given the key; Agent Proxy adds the credential at the network boundary when a request matches the rules an admin set. See How agent identity works.

把凭证注入 Claude 出站请求的网络层。模型和沙箱拿不到密钥；当请求匹配管理员设定的规则时，Agent Proxy 在网络边界加上凭证。见 How agent identity works。

Channel manager

A member of your Claude organization whom an Owner has named to set up specific channels. For each channel assigned to them, a channel manager sets the default model, adds repositories their own GitHub account can write to, and manages credentials in the channel’s own bundle, without holding the Owner role. See Delegate channel setup to channel managers.

Claude 组织中的一名成员，由 Owner 指定来配置特定频道。对分配给他们的每个频道，channel manager 设定默认模型、添加其本人 GitHub 账号可写入的仓库，并管理该频道自己的 bundle 里的凭证，而不需要持有 Owner 角色。见 Delegate channel setup to channel managers。

Channel memory

Facts Claude retains while working in a channel, including facts you told it to remember and notes it writes itself. Entries from public channels are shared across the workspace; entries from private channels are saved to that channel’s own store. See What Claude Tag remembers.

Claude 在频道里工作时保留的事实，包括你让它记住的，以及它自己写下的笔记。公开频道的条目在工作区共享；私有频道的条目存到该频道自己的存储。见 What Claude Tag remembers。

The earlier Claude in Slack / 早期的 Slack 中的 Claude

Claude Tag is the second generation of the Claude app in Slack:

Claude Tag 是 Slack 中 Claude 应用的第二代：

	Legacy (the earlier Claude in Slack)	New (Claude Tag)
Identity	Each user links their own claude.ai account	One agent identity with org-level service credentials
Sessions	Spawned per request	One persistent session per thread, shared
Memory	None	Shared workspace memory plus private-channel memory
Proactive work	None	Routines and channel watching

	Legacy（早期 Slack 中的 Claude）	New（Claude Tag）
身份	每个用户链接自己的 claude.ai 账户	一个 agent identity，配组织级服务凭证
Session	按请求生成	每个线程一个持久 session，共享
记忆	无	共享工作区记忆 + 私有频道记忆
主动工作	无	Routines 与盯频道

Your admin chooses which generation answers @Claude in a given channel, so two channels in the same workspace can work differently. See Migrate from the earlier Claude in Slack.

管理员选择给定频道里由哪一代应答 @Claude，因此同一工作区里两个频道可以工作方式不同。见 Migrate from the earlier Claude in Slack。

Connection

A credential for one external service that Claude uses on the channel’s behalf, like a Datadog API key or a GitHub App installation. Connections belong to the agent identity, not to any user, and are grouped into Access bundles by an admin.

Claude 代表频道使用的、针对某一个外部服务的凭证，例如 Datadog API key 或 GitHub App 安装。Connections 属于 agent identity，不属于任何用户，由管理员归入 Access bundles。

A connection is not a connector. A connector belongs to your personal claude.ai account. Claude cannot use your connectors in channels; it uses the channel’s connections. The one exception is a DM, where it uses your own account instead; see how DMs work in this model.

connection 不是 connector。connector 属于你个人的 claude.ai 账户。Claude 不能在频道里用你的 connectors；它用的是频道的 connections。唯一例外是私信，那里它改用你自己的账户；见 how DMs work in this model。

Connector

A tool you add to your own claude.ai account, like Gmail, Google Drive, or a custom MCP server, listed under Customize > Connectors. Connectors are personal; in Slack they apply only in DMs. For the agent-side equivalent that works in channels, see Connection.

你加到自己 claude.ai 账户上的工具，例如 Gmail、Google Drive 或自定义 MCP 服务器，列在 Customize > Connectors。Connectors 是个人的；在 Slack 里只在私信生效。频道里对应的 agent 侧概念见 Connection。

Environment

The sandboxed compute configuration a session runs in, including its network access setting. Environments used here must be scoped to the organization, not to an individual account, because channel sessions run with no user account attached.

session 运行所在的沙箱计算配置，包括其网络访问设置。这里用的 environments 必须划到组织，而不是个人账户，因为频道 session 运行时不附着任何用户账户。

Plugin

A bundle of skills an Owner attaches to an Access bundle or scope, teaching Claude how to use a specific tool or follow a specific process. Anthropic provides plugins for common tools; you can add your own. See Attach plugins.

Owner 绑到 Access bundle 或 scope 上的一组 skills，教 Claude 如何使用特定工具或遵循特定流程。Anthropic 为常见工具提供 plugins；你也可以加自己的。见 Attach plugins。

Routine

A scheduled or run-once task Claude runs on its own, such as a daily digest or a channel watch. Anyone in a channel can ask Claude to set one up, list what’s scheduled, or disable one. Routines run with the channel’s connections, not the creator’s.

Claude 自行运行的计划任务或一次性任务，例如每日摘要或盯频道。频道里任何人都可以请 Claude 设一条、列出已计划的，或禁用一条。Routines 用的是频道的 connections，不是创建者的。

Claude Code also has a feature named routines. Those run under an individual user’s account; Claude Tag routines run under the agent identity.

Claude Code 也有名为 routines 的功能。那些跑在个人用户账户下；Claude Tag 的 routines 跑在 agent identity 下。

Rule

The match conditions Agent Proxy checks against each outbound request. A connection pairs one credential with the rule that decides when to inject it, and a request that matches the rule gets the credential attached at the boundary. A request that nothing allows (no rule, no domain entry, no environment network access setting) is blocked. See Agent Proxy.

Agent Proxy 对每条出站请求检查的匹配条件。一条 connection 把一份凭证与决定何时注入的 rule 配对；匹配该 rule 的请求在边界被附上凭证。没有任何一层允许的请求（没有 rule、没有域名条目、没有 environment 网络访问设置）会被拦截。见 Agent Proxy。

Scope

One of three levels Claude’s settings can target: Default Slack access (the organization-wide root), one Slack workspace, or one channel (public or private). Scopes inherit downward, so a channel gets its workspace’s settings plus any of its own. An Owner attaches Access bundles and instructions at a scope. See Attach the bundle to a scope.

Claude 设置可以瞄准的三个层级之一：Default Slack access（全组织根）、一个 Slack 工作区，或一个频道（公开或私有）。Scope 向下继承，因此一个频道拿到其工作区的设置，再加上它自己的。Owner 在某个 scope 上绑定 Access bundles 和指令。见 Attach the bundle to a scope。

Session

The unit of work behind one conversation. Each Slack thread binds to one persistent session, and anyone in the channel can continue it by replying in the thread. A channel where Claude works at the top level, outside threads, also carries one session for the channel itself, separate from every thread’s. See How Claude Tag works and Restart a stuck or wrong-context session.

一次对话背后的工作单元。每个 Slack 线程绑定一个持久 session，频道里任何人都可以在线程里回复来继续它。Claude 在频道顶层（线程之外）工作时，频道本身也带着一个 session，与每个线程的分开。见 How Claude Tag works 和 Restart a stuck or wrong-context session。

How Claude Tag works: the scope, channel, and thread model in action
How agent identity works: how connection, scope, and Agent Proxy fit together when Claude runs a task
Set up Claude Tag: where bundles, scopes, and connections get created in the console
How Claude Tag works：scope、频道、线程模型如何落地
How agent identity works：Claude 跑任务时 connection、scope 和 Agent Proxy 如何拼在一起
Set up Claude Tag：bundle、scope 和 connections 在控制台的哪里创建

3.3 - How agent identity works

官方文档 How agent identity works 的中英对照

来源： How agent identity works

How agent identity works / Agent identity 如何工作

Claude Tag acts under its own service accounts in Slack channels, not as you. See how channel access is bounded, how credentials reach it, and why DMs differ.

Claude Tag 在 Slack 频道里以自己的服务账号行事，而不是作为你。本文说明频道访问如何划界、凭证如何到达它，以及私信为何不同。

Claude Tag’s identity depends on where you message it.

Claude Tag 的身份取决于你在哪里给它发消息。

In Slack channels, Claude acts with its own service accounts, rather than as a specific user. An organization Owner provisions this identity during setup, so it arrives with its own account in each system it works in: the Claude app in Slack, the Claude GitHub App on GitHub, and a service account in every other connected tool. Actions it takes are attributed to those accounts; for example, posts come from the Claude app and pull requests show the Claude GitHub App as the author.

在 Slack 频道里，Claude 用自己的服务账号行事，而不是某个具体用户。组织 Owner 在设置时配好这套身份，因此它在每个工作系统里都有自己的账号：Slack 里的 Claude 应用、GitHub 上的 Claude GitHub App，以及其他每个已连接工具里的服务账号。它采取的动作记在那些账号上；例如帖子来自 Claude 应用，拉取请求显示 Claude GitHub App 为作者。

In direct messages (DMs) between a user and @Claude, the provisioned identity does not apply. DMs are one-to-one only; group DMs aren’t supported. A DM has no channel to scope it to, so a DM session runs on the individual’s own claude.ai account instead, with their personal connectors. GitHub is the exception in attribution: a pull request opened from a DM is authored by the Claude GitHub App, the same as in channels, though the session can only work with repositories connected on that user’s own account. Owners can disable DMs organization-wide; see Allow or disable direct messages.

用户与 @Claude 之间的私信（DM）不适用这套配好的身份。私信仅一对一；不支持群组私信。私信没有可绑定的频道 scope，因此私信 session 改跑在该个人自己的 claude.ai 账户上，使用其个人 connectors。归属上 GitHub 是例外：从私信开出的拉取请求由 Claude GitHub App 署名，与频道相同，但 session 只能使用该用户自己账户上已连接的仓库。Owner 可以在全组织禁用私信；见 Allow or disable direct messages。

How Claude behaves in channels (its standing instructions, plugins, and channel memory) is configured separately from its identity; see custom instructions, plugins, and memory for more information.

Claude 在频道里如何表现（常驻指令、plugins、频道记忆）与其身份分开配置；详见 custom instructions、plugins 和 memory。

Channel sessions / 频道 session

When Claude works on a channel task, the request moves through three places:

Claude 处理频道任务时，请求经过三处：

The ask happens in your Slack workspace, when a user tags Claude to do something or a scheduled task starts.
The work Claude does runs in a sandbox, an isolated working environment built for the thread.
The agent’s credentials for any additional connections, such as GitHub or a data warehouse, reach those systems to pull the required information. An organization Owner sets up those credentials as part of provisioning the identity.
请求发生在你的 Slack 工作区：用户 Tag Claude 去做某事，或一条计划任务启动。
Claude 做的工作跑在沙箱里——为该线程建的隔离工作环境。
agent 为额外 connections（如 GitHub 或数据仓库）准备的凭证到达那些系统，拉取所需信息。组织 Owner 在配身份时设置这些凭证。

The diagram below traces one request through this process.

下图追踪一次请求如何走完这个过程。（原文此处有示意图。）

Tag Claude in a channel / 在频道里 Tag Claude

A user asks Claude to chart last week’s signups or fix a deploy test. The task gets a session in a thread under the message.

用户请 Claude 画出上周注册量，或修一次部署测试。任务在该消息下的线程里获得一个 session。

The session sandbox starts / session 沙箱启动

Claude does the work in an isolated environment built for this thread, reading files, writing documents, and running code. The credentials you provision are not placed in the sandbox; they stay in the credential store and are injected at the proxy.

Claude 在为本线程建的隔离环境里干活：读文件、写文档、跑代码。你配好的凭证不放进沙箱；它们留在凭证库，在代理处注入。

The request crosses Agent Proxy / 请求穿过 Agent Proxy

When the work needs something outside the sandbox, like calling the GitHub API or querying a warehouse, the request crosses Agent Proxy, the network boundary between the sandbox and everything else. Agent Proxy checks it against the rules an admin configured, and decides whether it proceeds and what credential, if any, travels with it.

当工作需要沙箱之外的东西（例如调用 GitHub API 或查询仓库）时，请求穿过 Agent Proxy——沙箱与其他一切之间的网络边界。Agent Proxy 对照管理员配置的规则检查它，决定是否放行，以及（若有）带上哪份凭证。

Agent Proxy attaches a credential / Agent Proxy 附上凭证

A matching credential comes from the credential store, where an admin’s connections are kept. Once saved, a credential is never displayed again; Agent Proxy retrieves it only at the moment of injection and attaches it to the request at the boundary, so the model and the sandbox itself are not given the key.

匹配的凭证来自凭证库，管理员的 connections 存放在那里。一旦保存，凭证不再显示；Agent Proxy 只在注入那一刻取出，并在边界把它附到请求上，因此模型和沙箱本身拿不到密钥。

The result posts back, as Claude / 结果以 Claude 的身份回帖

The credentialed request reaches your system, like GitHub or the warehouse, and the result returns to the thread.

带凭证的请求到达你的系统（如 GitHub 或仓库），结果回到线程。

Agent Proxy

For each outbound request from the sandbox, Agent Proxy checks the destination against three allow layers. A request goes through if any one of them allows it; a host that none of them allows is blocked.

对沙箱发出的每条出站请求，Agent Proxy 用三层允许规则检查目的地。任一层面允许，请求就通过；三层都不允许的主机被拦截。

When the destination	Result
Matches a connection’s rule, its allowed websites	The proxy attaches that connection’s credential and forwards the request. The credential stays at the proxy; the model and sandbox are not given it.
Is on the bundle’s Domains list but matches no connection	The proxy forwards the request without a credential.
Is allowed by the network access setting of the environment the scope’s sessions run on	The proxy forwards the request without a credential.
Matches none of these	The proxy blocks the request.

当目的地	结果
匹配某条 connection 的 rule（其 allowed websites）	代理附上该 connection 的凭证并转发。凭证留在代理处；模型和沙箱拿不到。
在 bundle 的 Domains 列表上，但不匹配任何 connection	代理不带凭证转发。
被该 scope 的 session 所跑 environment 的网络访问设置允许	代理不带凭证转发。
以上都不匹配	代理拦截该请求。

A new environment’s network access level defaults to Trusted access, so a fresh setup can reach a documented set of package registries and developer hosts before an admin has configured anything. The cloud environments documentation lists the covered hosts. To narrow that default, pin an environment with a stricter level, such as No access.

新 environment 的网络访问级别默认为 Trusted access，因此在管理员尚未配置任何东西之前，全新设置就能到达一组已文档化的包注册表和开发者主机。cloud environments 文档列出覆盖的主机。要收紧该默认，钉一个更严的级别，例如 No access。

The same rules apply to code Claude runs in the sandbox, like curl or a fetch call: a request is blocked unless its host is allowed by one of the layers above.

Claude 在沙箱里跑的代码（如 curl 或 fetch）适用同一套规则：除非其主机被上面某一层允许，否则请求被拦截。

Agent Proxy carries HTTP and HTTPS only. A protocol that isn’t HTTP, such as SSH or a database’s native wire protocol, can’t cross the proxy even to an allowed host.

Agent Proxy 只承载 HTTP 和 HTTPS。非 HTTP 的协议，例如 SSH 或数据库的原生线路协议，即使主机在允许名单上也不能穿过代理。

For the endpoints and addresses your network team may need to allowlist, see Network requirements.

网络团队可能需要加入 allowlist 的端点和地址，见 Network requirements。

How a host gets allowed / 主机如何被允许

A host that none of the three layers above allows is blocked, and Claude names the blocked host in the thread so an admin can add it; see Give Claude access to your tools.

上面三层都不允许的主机被拦截，Claude 会在线程里点出被拦的主机，方便管理员添加；见 Give Claude access to your tools。

Web search vs. network requests / 网页搜索 vs. 网络请求

Claude can search the web from a channel without any Domains entry. Web search is Anthropic’s built-in web search tool, which runs on Anthropic’s servers, not code running in the channel’s sandbox.

Claude 可以从频道搜索网页，不需要任何 Domains 条目。网页搜索是 Anthropic 内置的搜索工具，跑在 Anthropic 的服务器上，而不是频道沙箱里的代码。

The sandbox sends nothing new for a search. Search requests travel to Anthropic the same way the session’s model traffic already does, and the searching happens server-side. The Agent Proxy rules don’t apply to web search; fetching a page or calling a service from the sandbox is an outbound network request and follows them.

搜索时沙箱不会新发出任何东西。搜索请求以 session 的模型流量同一路径到达 Anthropic，搜索发生在服务端。Agent Proxy 规则不适用于网页搜索；从沙箱抓取页面或调用服务才是出站网络请求，要走这些规则。

Searching and opening a page are different actions. A search returns content from the pages it matches, which Claude reads and cites, so it can answer from a page that search surfaced. Opening a URL, whether one you pasted or one a search returned, is a fetch from the sandbox, and the host needs an allow layer. That is why Claude can quote a page it found through search and still report that it can’t open the same link.

搜索和打开页面是不同动作。搜索返回所匹配页面的内容，Claude 阅读并引用，因此它能根据搜索捞到的页面作答。打开一个 URL——无论是你粘贴的还是搜索返回的——是从沙箱发起的 fetch，主机需要一层允许。这就是为什么 Claude 可以引用它通过搜索找到的页面，却仍报告打不开同一条链接。

The web search capability setting in your organization’s claude.ai admin settings governs claude.ai chat; it doesn’t govern Claude Tag sessions, in channels or DMs. If Claude reports that it can’t reach a host from a channel, the fix is a domain entry or the scope’s environment, not that setting.

组织 claude.ai 管理设置里的网页搜索能力开关管的是 claude.ai 聊天；不管 Claude Tag 的 session（频道或私信）。若 Claude 报告从频道够不到某个主机，要修的是域名条目或该 scope 的 environment，不是那个开关。

Agent access / Agent 访问

What Claude can reach in a channel comes from the Access bundles an admin attached to that channel’s scope. Anyone in the channel gets the same capability, and the same request can do more in #platform-eng than in a general channel.

Claude 在频道里能触及什么，来自管理员绑到该频道 scope 上的 Access bundles。频道里任何人能力相同；同一请求在 #platform-eng 能做的比在普通频道多。

This design has four consequences.

这一设计有四项后果。

Configure once. Everyone in the scope can use it immediately.
Predictability. What Claude can do never changes based on who asked.
Personal connectors apply in DMs. A shared channel uses only the service-account connections an admin attached, not connectors on anyone’s claude.ai account.
Clean audit. Actions in connected tools show up under a service account your security team already knows how to reason about.
配置一次。该 scope 里所有人立刻能用。
可预期。Claude 能做什么从不因提问者是谁而变。
个人 connectors 在私信里生效。共享频道只用管理员绑上的服务账号 connections，不用任何人 claude.ai 账户上的 connectors。
干净审计。已连接工具里的动作出现在安全团队已经知道如何推理的服务账号下。

That service-account identity is also how Claude appears wherever it acts. In Slack, it posts as the Claude app. On GitHub, commits and pull requests show the Claude GitHub App, and pull requests link back to the Slack thread they came from. In every other connected service, actions appear under the service account an admin provisioned, in that service’s audit log.

这套服务账号身份也是 Claude 在各处行动时的露面方式。在 Slack，它以 Claude 应用发帖。在 GitHub，提交和拉取请求显示 Claude GitHub App，拉取请求链回它们来自的 Slack 线程。在其他每个已连接服务里，动作出现在管理员配好的服务账号下，记在该服务自己的审计日志中。

Direct message channels / 私信频道

A DM with Claude works differently from a channel. There is no scope to attach an identity to, so a DM session runs with your own claude.ai account instead, the same way a Claude Code session on the web does, using your own connectors and credentials, with results attributed to you (pull requests excepted; the Claude GitHub App authors those from DMs too). The diagram contrasts with the channel path above; the sandbox is the same engine, but everything around it is yours.

与 Claude 的私信和频道不同。没有可绑定身份的 scope，因此私信 session 改跑在你自己的 claude.ai 账户上，和网页上的 Claude Code session 一样，使用你自己的 connectors 和凭证，结果记在你名下（拉取请求除外；从私信开出的同样由 Claude GitHub App 署名）。示意图与上面的频道路径对照：沙箱是同一套引擎，周围的一切是你的。（原文此处有示意图。）

The table lines up the two paths on the four dimensions that differ.

下表按四个不同维度把两条路径对齐。

	In a channel	In a DM
Acts as	Its own service accounts	You
Access	The channel’s Access bundles	Your personal connectors
Attribution	The agent’s accounts, in each tool’s audit log	Your name, except pull requests, which the Claude GitHub App authors
Billing	The organization	Your seat

	在频道里	在私信里
作为谁行事	它自己的服务账号	你
访问	频道的 Access bundles	你的个人 connectors
归属	agent 的账号，记在各工具的审计日志	你的名字；拉取请求除外，由 Claude GitHub App 署名
计费	组织	你的席位

Three of those differences are worth spelling out.

其中三项值得展开。

Connectors. The connectors on your account are available, including MCP servers you’ve added.
Billing. Usage bills to your seat rather than the organization’s service key.
Channel-side configuration. It doesn’t follow you in; the agent’s connections and repository grants don’t apply in DMs.
Connectors。你账户上的 connectors 可用，包括你加过的 MCP 服务器。
计费。用量记在你的席位上，而不是组织的服务密钥。
频道侧配置。不会跟着你进来；agent 的 connections 和仓库授权在私信里不适用。

DM work runs under your credentials, so most of it is attributed to you and can reach only what your own accounts can. Pull requests are the exception: Claude authors them as the Claude GitHub App from DMs too, so a repository’s history shows the same author either way, while the repositories it can reach are still only the ones connected on your own account.

私信工作跑在你的凭证下，所以大部分记在你名下，也只能触及你自己账号能触及的。拉取请求是例外：从私信开出的同样由 Claude GitHub App 署名，因此仓库历史里作者两边一样，而它能触及的仓库仍然只是你自己账户上已连接的那些。

Use channels for shared work and DMs for personal tasks, or for data you’d rather access under your own authenticated identity than a shared channel credential.

共享工作用频道；个人任务，或你更希望以自己的已认证身份而不是共享频道凭证去访问的数据，用私信。

Claude Tag versus Claude Code in Slack / Claude Tag vs. Slack 里的 Claude Code

A DM with Claude Tag runs under your own account, which is also how Claude Code in Slack works, routing a coding @-mention to a Claude Code session on the web under the requester’s own account. The two can look identical. The table shows how to tell them apart.

Claude Tag 的私信跑在你自己的账户下，这也是 Slack 里 Claude Code 的工作方式：把编码相关的 @提及路由到请求者自己账户下、网页上的 Claude Code session。两者看起来可以一模一样。下表说明如何区分。

	Claude Tag in a channel	Claude Code in Slack
Runs under	The agent identity an admin provisioned	Your own Claude account, linked in the Claude app
GitHub	The Claude GitHub App; pull requests belong to the app	Your GitHub connection on claude.ai/code; pull requests open under your account
Access	The Access bundles an admin attached to the channel	Your personal connectors
Billing	The organization	Your seat

	频道里的 Claude Tag	Slack 里的 Claude Code
跑在谁下面	管理员配好的 agent identity	你在 Claude 应用里链接的自己的 Claude 账户
GitHub	Claude GitHub App；拉取请求属于该应用	claude.ai/code 上你的 GitHub 连接；拉取请求开在你账户下
访问	管理员绑到该频道的 Access bundles	你的个人 connectors
计费	组织	你的席位

If @Claude in your workspace opens pull requests as you, you’re seeing Claude Code in Slack, not a Claude Tag session.

如果工作区里 @Claude 以你的身份开拉取请求，你看到的是 Slack 里的 Claude Code，而不是 Claude Tag session。

Security and data handling: where credentials are stored, what leaves your tenant, and what runs unattended
Give Claude access: provision the access this page describes
Restrict where Claude Tag operates: narrow where this agent identity is allowed to act
Security and data handling：凭证存在哪里、什么离开你的租户、什么在无人值守时运行
Give Claude access：配置本页描述的访问
Restrict where Claude Tag operates：收窄这套 agent identity 被允许行动的范围

3.4 - Agent identity: a new access model

概念博文 Agent identity: a new access model for autonomous, team-wide AI 的中英对照（Noah Zweben）

来源： Agent identity: a new access model for autonomous, team-wide AI
日期： 2026 年 6 月 24 日
作者： Noah Zweben（Claude Code 团队，Member of Technical Staff）
分类： Product
阅读时间：约 5 分钟

Agent identity in Claude Tag: a new access model for autonomous, team-wide AI / Claude Tag 中的 Agent identity：面向自主、全团队 AI 的新访问模型

How Claude Tag’s agent identity access model works, and best practices for configuring it in your team’s workspace.

Claude Tag 的 agent identity 访问模型如何工作，以及在团队工作区里配置它的实践建议。

For an AI agent to do its best work on a human-agent team, it needs access to the same tools, documents, and context humans have.

要让 AI agent 在人机混编团队里把工作做到最好，它需要能访问人类已有的同一套工具、文档和上下文。

In a “single player” AI experience (where one person chats with one assistant), that’s straightforward: you connect your own accounts and the agent acts on your behalf. But in a “multiplayer” AI experience like Claude Tag, Claude sits in a shared channel alongside many people at once, and it draws on the tools and context that belong to the workspace, rather than any one individual.

在「单人」AI 体验里（一个人与一个助手聊天），这很直接：你连上自己的账号，agent 代表你行事。但在 Claude Tag 这样的「多人」AI 体验里，Claude 同时坐在共享频道里、旁边有许多人，它调用的是属于工作区的工具和上下文，而不是属于某一个人。

To make multiplayer experiences work, Claude needs its own accounts for those tools, set up by an admin and tied to the workspace. We call this access model agent identity.

为了让多人体验成立，Claude 需要这些工具上属于它自己的账号，由管理员配置并绑到工作区。我们把这套访问模型叫作 agent identity。

In this post, we explain how agent identity works, how it moves permissions from per-user to per-channel, and how to scope it well in your own workspace.

本文说明 agent identity 如何工作、它如何把权限从按人改成按频道，以及如何在你自己的工作区里把范围划好。

Why “act as the user” breaks down / 为什么「以用户身份行事」会垮掉

When you use AI as a personal assistant, you can connect platforms like Google Drive, GitHub, and your calendar, and let the model use your access permissions to read and write in them.

当你把 AI 当个人助手用时，可以连接 Google Drive、GitHub 和日历等平台，让模型用你的访问权限去读写。

This model doesn’t work for Claude Tag for two reasons:

这套模型对 Claude Tag 不适用，原因有二：

Increasing agent autonomy. The length of a task that an AI agent can reliably complete on its own has been doubling roughly every four months. Agents now schedule their own tasks for later and respond to events long after the person who asked has logged off. While users set up routines that trigger them to act given certain situations, the agent works largely autonomously.
Multiplayer teams. Claude Tag places Claude in shared spaces where teams are already working—e.g., a channel where three engineers and a PM are debugging together. But when more than one person is steering, whose permissions apply? There’s no single choice of person that’d be right all of the time. This gives admins the ability to define what an agent can do in Slack independent from the humans involved, and a distinct tracking of what is done in Slack.
Agent 自主性在上升。 AI agent 能可靠独立完成的任务长度，大约每四个月翻一倍。Agent 现在会给自己安排稍后的任务，并在提问者早已下线之后仍响应事件。虽然用户会设 routines，在特定情况下触发它们行动，但 agent 大体上是自主工作的。
多人团队。 Claude Tag 把 Claude 放进团队已经在工作的共享空间——例如三个工程师和一个 PM 一起排障的频道。但当不止一个人在转向时，用谁的权限？没有哪一个人选会永远正确。这让管理员能独立于牵涉其中的人，定义 agent 在 Slack 里能做什么，并对 Slack 里发生的事有单独的追踪。

Claude acts as itself / Claude 作为它自己行事

In a channel where Claude Tag is active, Claude isn’t acting on behalf of a single user. It has its own account in each system it touches: it posts in Slack as the Claude app, opens pull requests as the Claude GitHub App, and queries your warehouse under a service account provisioned by an admin.

在启用了 Claude Tag 的频道里，Claude 不是代表某一个用户行事。它在触及的每个系统里都有自己的账号：在 Slack 以 Claude 应用发帖，以 Claude GitHub App 开拉取请求，在管理员配好的服务账号下查询你的数仓。

And because there are no personal user credentials in play, a shared channel can never become a side door into someone’s private documents.

也因为没有个人用户凭证介入，共享频道永远不会变成通往某人私人文档的侧门。

Inheriting permissions / 权限继承

In the agent identity model, admins define an identity—the baseline set of connections and skills Claude holds everywhere—at the workspace level, and every channel inherits it by default. Then, where it makes sense, they can override it at the channel level, such as by granting the engineering channel access to GitHub and the data warehouse, or confining a CRM connection to a single private channel.

在 agent identity 模型里，管理员在工作区级定义一套身份——Claude 在各处持有的 connections 和 skills 基线——每个频道默认继承。然后在合适的地方，可以在频道级覆盖，例如给工程频道 GitHub 和数仓访问，或把 CRM 连接限制在单个私有频道。

In addition to credentials, admins also define:

除了凭证，管理员还定义：

Repository access: which repos Claude can read and write to.
Connectors: the tools and API keys that Claude uses to do its job. Across an organization, different API keys can connect to the same service at different permission levels (e.g., Claude might be given read-only warehouse access in a general channel, and write access in the data team’s private one).
Skills and plugins: folders of instructions, scripts, and resources Claude loads dynamically to improve performance on specialized tasks.
Standing instructions: custom instructions and context for each channel.
仓库访问： Claude 能读写哪些仓库。
Connectors： Claude 用来干活的工具和 API 密钥。在一个组织里，不同 API 密钥可以以不同权限级别连到同一服务（例如 Claude 在普通频道只有数仓只读，在数据团队私有频道有写权限）。
Skills 和 plugins： Claude 动态加载的指令、脚本和资源文件夹，用来提升专项任务表现。
常驻指令： 每个频道的自定义指令和上下文。

Because this model works around distinct Claude identities, revoking the identity ends Claude’s access everywhere that the identity was used. This takes much less effort to manage than auditing individual agent actions across dozens of user accounts.

因为这套模型围绕彼此分离的 Claude 身份运作，撤销该身份就会结束它被使用过的所有地方的访问。这比在几十个用户账户上审计单次 agent 动作省力得多。

How the agent identity model works / Agent identity 模型如何工作

Agent identity replaces the question “what can this user do?” with “what can this agent do in this compartment?” That’s a departure from per-user Access Control Lists: it means that a channel member without direct access to the repo can ask Claude to read that repo, if the channel’s profile grants Claude that permission.

Agent identity 把问题从「这个用户能做什么？」换成「这个 agent 在这个隔间里能做什么？」这偏离了按人的访问控制列表：意味着一个对仓库没有直接访问的频道成员，也可以请 Claude 去读那个仓库——如果该频道的 profile 授予了 Claude 这项权限。

This is unusual, but we think it is a necessary step toward an access model that works for autonomous, multiplayer agents. Below, we sketch out how to think about setting those boundaries.

这不寻常，但我们认为这是迈向适合自主、多人 agent 的访问模型的必要一步。下面勾勒如何思考这些边界。

How identity boundaries work / 身份边界如何工作

Claude Tag creates a distinct identity for each private channel; public channels in a workspace share a workspace-level identity. Claude’s identity in a legal channel can’t reach code that wasn’t granted there, and its identity in an engineering channel can’t read legal documents that weren’t granted there. Memory and access respect those boundaries: what Claude learns in a private channel never appears in the wider workspace.

Claude Tag 为每个私有频道创建独立身份；工作区里的公开频道共享工作区级身份。法务频道里的 Claude 身份够不到未在那里授予的代码，工程频道里的身份也读不到未在那里授予的法务文档。记忆和访问都尊重这些边界：Claude 在私有频道里学到的，永远不会出现在更宽的工作区里。

The identity belongs to the channel, so anyone in it can tag Claude by default, and admins can scope each channel’s profile to the least-privileged member. On Enterprise plans, role-based access control lets admins go further and decide which members can invoke Claude at all, so a channel governs both what the agent can reach and who can ask.

身份属于频道，因此默认频道里任何人都可以 Tag Claude，管理员可以把每个频道的 profile 收到权限最低的成员那一级。Enterprise 计划上，基于角色的访问控制让管理员可以再进一步，决定哪些成员根本能调用 Claude，于是一个频道既治理 agent 能触及什么，也治理谁能提问。

Broad default access to tools and context / 对工具和上下文的宽默认访问

How teams scope Claude’s tool access in Claude Tag: broad, low-risk integrations run in shared channels under an agent identity, while personal or team-specific tools stay in DMs and run as the user.

团队如何在 Claude Tag 里划定 Claude 的工具访问：宽、低风险的集成跑在共享频道里、落在 agent identity 下；个人或团队专用工具留在私信里、以用户身份运行。（原文此处有示意图。）

Running Claude Tag inside Anthropic, we found that its value compounds with tool and context access. Each connected system makes every other one more useful, because Claude can combine context across them—pulling a thread from Slack, a doc from Drive, a ticket from a tracker, and a query from a warehouse into one answer that no single tool could provide.

在 Anthropic 内部跑 Claude Tag 时，我们发现它的价值随工具和上下文访问而叠加。每多连一个系统，其他系统就更有用，因为 Claude 能跨系统组合上下文——从 Slack 抽线程、从 Drive 抽文档、从工单系统抽票、从数仓抽查询，合成任何一个单工具给不出的答案。

The teams that get the most out of Claude are the ones that grant it generous access from the start, and pare access back depending on their organization’s admin preferences. Agent identity gives admins broad enough scope for Claude to do useful cross-system work, with boundaries firm enough that the access never travels somewhere it wasn’t granted. Our advice is to start with a baseline profile in a few channels, read the audit trail, and then extend access where the work justifies it, one deliberate grant at a time.

从 Claude 拿得最多的团队，是一开始就给它宽访问、再按组织管理员偏好往回收的那些。Agent identity 给管理员足够宽的范围，让 Claude 能做有用的跨系统工作，同时边界足够硬，访问不会跑到未被授予的地方。我们的建议是：先在少数频道用基线 profile，读审计轨迹，再在工作能证明其必要的地方扩展访问，一次一次审慎授予。

For organizations that require even more granularity, admins can disable Claude Tag in specific channels. Admins can also apply role-based access controls (RBAC) to limit access to Claude Tag to specific users.

需要更细粒度的组织，管理员可以在特定频道禁用 Claude Tag。管理员也可以用基于角色的访问控制（RBAC）把 Claude Tag 限制给特定用户。

Direct messages / 私信

With Claude Tag, direct messages work differently than in shared channels. DMs run on users’ individual claude.ai accounts—their connectors, credentials, and name on the result. This makes DMs the right place to work with Claude on tasks and with tools that should never live in a channel, like email drafts or software only you have a license for.

在 Claude Tag 里，私信与共享频道不同。私信跑在用户各自的 claude.ai 账户上——他们的 connectors、凭证，以及结果上的名字。因此，那些绝不该活在频道里的任务和工具（例如邮件草稿，或只有你有许可证的软件），私信才是和 Claude 一起做的地方。

Security and audit / 安全与审计

When an admin adds a connection to a channel’s profile, the credential is stored independently and mapped to that channel’s identity, then injected at the network boundary at request time. Outbound traffic to any host an admin hasn’t allowed is blocked outright. On the audit side, every routine, memory write, and network call made with agent credentials is recorded, and because Claude acts under its own service accounts, those actions also land in each connected system’s own logs.

管理员把一条 connection 加到频道 profile 时，凭证被独立存储并映射到该频道身份，然后在请求时于网络边界注入。到管理员未允许的任何主机的出站流量直接拦截。审计侧，用 agent 凭证做出的每条 routine、每次记忆写入、每次网络调用都被记录；又因为 Claude 以自己的服务账号行事，这些动作也会落到每个已连接系统自己的日志里。

What’s next / 下一步

Agent identity is the foundation of Claude Tag’s access model. In the future, we plan to strengthen our Claude Tag’s security offerings to include just-in-time credential grants—so that a user can approve a single sensitive action in the moment without permanently widening the agent’s scope—and an identity-aware overlay for organizations with more complex clearance structures. This will add user-level checks on top of an agent’s scope, so Claude only acts when both the channel’s profile and the requesting user’s own permissions allow it.

Agent identity 是 Claude Tag 访问模型的地基。未来我们计划加强 Claude Tag 的安全能力，包括即时（just-in-time）凭证授予——让用户能当场批准一次敏感动作，而不永久扩大 agent 的范围——以及面向更复杂密级结构的组织的身份感知叠加层。这将在 agent 的 scope 之上加上用户级检查，只有频道 profile 和请求用户本人的权限都允许时，Claude 才行动。

The shift from single player to multiplayer AI in products like Claude Tag makes long-running, team-based work possible. Agent identity ensures that Claude’s access to tools is broad enough to be useful, but scoped enough to be secure at enterprise scale.

像 Claude Tag 这样的产品从单人到多人 AI 的转变，让长时、基于团队的工作成为可能。Agent identity 确保 Claude 对工具的访问宽到有用，又收得足够紧，能在企业规模上安全。

Learn more about Claude Tag.

了解更多：Claude Tag。

3.5 - Security and data handling

官方文档 Security and data handling 的中英对照

来源： Security and data handling

Security and data handling / 安全与数据处理

Claude Tag runs in an isolated sandbox that holds no credentials. Covers sandbox isolation, credential storage, network egress, service accounts, isolating credentials between channels and what one channel can reach, who can open a published artifact, and which members can invoke Claude.

Claude Tag 跑在不持有凭证的隔离沙箱里。本文覆盖沙箱隔离、凭证存储、网络出站、服务账号、频道之间如何隔离凭证以及一个频道能触及什么、谁能打开已发布的 artifact、哪些成员能调用 Claude。

In channels, Claude acts under its own service accounts that an Owner provisions. By default it can read and post in Slack channels it’s been added to and search public channels by keyword; it has no access to your external systems until an Owner adds connections. Each connection is scoped to specific channels and workspaces, and the actions Claude takes in connected tools are attributable to its own service accounts.

在频道里，Claude 以 Owner 配好的自己的服务账号行事。默认它能在已被加入的 Slack 频道里读和发，并能按关键词搜索公开频道；在 Owner 加上 connections 之前，它不能访问你们的外部系统。每条 connection 限定到特定频道和工作区，Claude 在已连接工具里采取的动作可追溯到它自己的服务账号。

Every channel request, whether a person typed it or a schedule triggered it, follows the same path: it runs in an isolated sandbox that holds no credentials. In an Anthropic-hosted environment, requests leave that sandbox only through Agent Proxy and reach your systems under the agent’s own accounts. Sessions in a self-hosted environment run on runners inside your network, and Claude can’t use Access bundles in those sessions yet.

每一条频道请求——无论是人打的还是日程触发的——都走同一条路径：跑在不持有凭证的隔离沙箱里。在 Anthropic 托管的 environment 里，请求只通过 Agent Proxy 离开沙箱，并以 agent 自己的账号到达你们的系统。自托管 environment 里的 session 跑在你们网络内的 runner 上，那些 session 目前还不能使用 Access bundles。

DMs run on the user’s own claude.ai account instead and are covered separately on How agent identity works.

私信改跑在用户自己的 claude.ai 账户上，单独见 How agent identity works。

How a request travels / 请求如何走

Each Slack thread runs in its own sandbox. In an Anthropic-hosted environment, every outbound call from that sandbox passes through the same checkpoints.

每个 Slack 线程跑在自己的沙箱里。在 Anthropic 托管的 environment 里，该沙箱的每条出站调用都经过同一组检查点。

Checkpoint	The guarantee
The sandbox	Holds no credentials
Agent Proxy	Injects credentials from the credential store at request time, and blocks traffic to unlisted hosts by default
Your systems	See the agent’s own accounts, so its actions there are attributable

检查点	保证
沙箱	不持有凭证
Agent Proxy	在请求时从凭证库注入凭证，默认拦截未列入的主机流量
你们的系统	看到的是 agent 自己的账号，因此那里的动作可归属

Compute and the sandbox / 计算与沙箱

Sessions run in ephemeral sandboxes, the same infrastructure that runs Claude Code on the web. Each Slack thread gets its own sandbox.

Session 跑在短暂沙箱里，与网页上 Claude Code 用的是同一套基础设施。每个 Slack 线程有自己的沙箱。

When a thread goes quiet, its sandbox is released; replying in the thread builds a fresh one. What persists across that release and rebuild:

线程安静后，沙箱被释放；在线程里回复会建一个新的。释放与重建之间留下什么：

Persists: The thread, its visible work, and anything pushed to a branch, opened as a pull request, or posted into Slack.
Does not persist: Files that existed only inside the sandbox. To keep generated files, ask Claude to push them to a branch or post them in the thread.
留下：线程、可见的工作，以及推到分支、开成拉取请求或发进 Slack 的任何东西。
不留下：只存在于沙箱内部的文件。要保留生成的文件，请 Claude 把它们推到分支或发到线程里。

Claude Tag retains channel memory and session transcripts. Because of that retention, Claude Tag isn’t available to organizations with Zero Data Retention (ZDR) enabled.

Claude Tag 保留频道记忆和 session transcripts。因为这项保留，启用了 Zero Data Retention（ZDR）的组织不能使用 Claude Tag。

Credential storage / 凭证存储

Credentials you provision are kept in a separate credential store, not in the proxy itself. When an outbound request matches a rule, Agent Proxy, the network layer between the sandbox and any external host, retrieves the credential from that store and injects it at the boundary, so the model and the sandbox are not given the key.

你配好的凭证放在单独的凭证库里，不在代理本身。当出站请求匹配一条 rule 时，Agent Proxy（沙箱与任何外部主机之间的网络层）从该库取出凭证并在边界注入，因此模型和沙箱拿不到密钥。

This means:

这意味着：

A saved credential is not displayed again. The setup screens are write-only.
The credential travels only to the hosts you named when you added the connection.
You can narrow the credential further, to one host, one path prefix, or read-only methods, in Add connections.
已保存的凭证不再显示。设置界面是只写的。
凭证只到达你添加 connection 时点名的主机。
你可以在 Add connections 里进一步收窄凭证：一台主机、一个路径前缀，或只读方法。

Network egress / 网络出站

In an Anthropic-hosted environment, outbound traffic from a channel session’s sandbox is default-deny. Requests go only to hosts an allow layer covers, and the layers are a connection’s Allowed websites, the bundle’s Domains tab, and the network access setting of the environment the scope’s sessions run on. A new environment’s default level, Trusted access, already covers a documented set of package registries and developer hosts. See Agent Proxy for what happens to a request under each layer.

在 Anthropic 托管的 environment 里，频道 session 沙箱的出站流量默认拒绝。请求只到达某一允许层覆盖的主机；这些层是 connection 的 Allowed websites、bundle 的 Domains 页，以及该 scope 的 session 所跑 environment 的网络访问设置。新 environment 的默认级别 Trusted access 已经覆盖一组已文档化的包注册表和开发者主机。每一层下请求会怎样，见 Agent Proxy。

Because requests to any other host are blocked, data can only leave the sandbox to hosts an allow layer covers. An admin sets the Allowed websites list on each connection and the Domains tab on each bundle. An admin sets the environment’s network access level, which defaults to Trusted access, from the Cloud environments page in admin settings. See Set allowed websites and Allow a host without a credential.

因为到任何其他主机的请求都被拦截，数据只能离开沙箱到达允许层覆盖的主机。管理员在每条 connection 上设 Allowed websites 列表，在每个 bundle 上设 Domains 页。管理员在管理设置的 Cloud environments 页设定 environment 的网络访问级别，默认为 Trusted access。见 Set allowed websites 和 Allow a host without a credential。

Organizations can opt in to allow-all egress, where a * entry on a bundle’s Domains tab admits requests to any host on the ports that entry lists, still without credentials. Private and internal network addresses and cloud metadata endpoints remain blocked. Allow-all egress is off by default and enabled per organization by Anthropic; see Allow all hosts.

组织可以选用 allow-all egress：bundle 的 Domains 页上一条 * 条目，允许到该条目所列端口上任意主机的请求，仍然不带凭证。私有和内部网络地址以及云元数据端点仍然被拦截。Allow-all egress 默认关闭，由 Anthropic 按组织开启；见 Allow all hosts。

Service accounts / 服务账号

In channels, Claude acts under service credentials of its own, not under the account of the person who tagged it. The Slack surface is the Claude app, code work goes through the Claude GitHub App, and every other connected tool uses a service account an Owner provisions in an Access bundle. See How agent identity works for the full model.

在频道里，Claude 以自己的服务凭证行事，而不是 Tag 它的那个人的账号。Slack 面上是 Claude 应用，代码工作走 Claude GitHub App，其他每个已连接工具使用 Owner 在 Access bundle 里配好的服务账号。完整模型见 How agent identity works。

A connection belongs to that agent identity and is shared by everyone the bundle’s scope covers. Anyone in a channel under that scope can ask Claude to act with the credential, so whatever the connected account can read or write is available to every member of those channels. Connect a dedicated identity you control for each service, such as a claude@yourcompany.example.com seat or a native service account, rather than a personal login. A dedicated account keeps the agent’s actions separately auditable in each tool’s logs and lets you revoke its access without affecting a person; see Create a dedicated account per service.

一条 connection 属于那套 agent identity，并由该 bundle 的 scope 覆盖的所有人共享。该 scope 下频道里的任何人都可以请 Claude 用这份凭证行动，因此已连接账号能读或写的一切，对这些频道的每个成员都可用。为每个服务连接一个你控制的专用身份，例如 claude@yourcompany.example.com 席位或原生服务账号，而不是个人登录。专用账号让 agent 的动作在各工具日志里可单独审计，也让你能撤销其访问而不影响某个人；见 Create a dedicated account per service。

DMs with @Claude run on the user’s own claude.ai account instead, with that user’s personal connectors, and work there is attributed to them, except pull requests, which the Claude GitHub App authors from DMs as well. Personal connectors apply only in DMs, never in channels. Owners can disable DMs organization-wide; see Allow or disable direct messages.

与 @Claude 的私信改跑在用户自己的 claude.ai 账户上，使用该用户的个人 connectors，那里的工作记在他们名下；拉取请求除外，从私信开出的同样由 Claude GitHub App 署名。个人 connectors 只在私信生效，从不在频道。Owner 可以在全组织禁用私信；见 Allow or disable direct messages。

Isolate credentials between channels / 在频道之间隔离凭证

A channel session can use only the Access bundles attached in one of three places:

频道 session 只能使用绑在以下三处之一的 Access bundles：

The channel itself. A bundle you attach here applies in that channel only.
The channel’s workspace. A bundle you attach here applies in every channel of that workspace.
Default Slack access. The organization-wide root; a bundle you attach here applies in every channel of every paired workspace.
频道本身。绑在这里的 bundle 只在该频道生效。
该频道的工作区。绑在这里的 bundle 在该工作区的每个频道生效。
Default Slack access。全组织根；绑在这里的 bundle 在每个已配对工作区的每个频道生效。

A bundle attached anywhere else in your organization is invisible to the session, and no request from the session’s sandbox can carry a credential from a bundle outside those three scopes.

绑在组织里其他任何地方的 bundle 对该 session 不可见，session 沙箱发出的请求也不能携带这三层 scope 之外的 bundle 的凭证。

For example, if you attach a bundle holding finance credentials to one private channel, sessions in every other channel run as if that credential doesn’t exist. If you attach the same bundle to a workspace or to Default Slack access instead, every channel beneath it gets that access, so isolation comes from where you attach the bundle, not from the bundle itself.

例如，若你把持有财务凭证的 bundle 绑到一个私有频道，其他每个频道的 session 运行起来就像那份凭证不存在。若你把同一 bundle 绑到工作区或 Default Slack access，它下面的每个频道都拿到这份访问，因此隔离来自你把 bundle 绑在哪里，而不是 bundle 本身。

Confine a credential to one channel in three steps:

把一份凭证限制在一个频道，三步：

Attach its bundle to that channel and nowhere broader.
Keep the channel private. A bundle on a public channel grants its access to anyone who joins.
Check the channel’s Access summary on the Slack tab in admin settings. It shows the access the channel actually gets, including what it inherits from the workspace and Default Slack access.
把它的 bundle 绑到该频道，不要绑到更宽的地方。
保持频道私有。公开频道上的 bundle 会把访问授予任何加入的人。
在管理设置的 Slack 页查看该频道的 Access summary。它显示频道实际拿到的访问，包括从工作区和 Default Slack access 继承的。

Claude doesn’t operate in externally shared channels, so a channel shared with another company never has a session to isolate.

Claude 不在对外共享的频道里运作，因此与另一家公司共享的频道永远不会有需要隔离的 session。

Isolating a credential doesn’t isolate what Claude knows. What it learns in a public channel becomes workspace memory that sessions in the workspace’s other channels can read, and it can search public channels by keyword without being added to them, the same way any workspace member can.

隔离凭证并不能隔离 Claude 知道的东西。它在公开频道里学到的会成为工作区记忆，工作区其他频道的 session 能读；它也可以按关键词搜索公开频道而不必被加入，和任意工作区成员一样。

Artifact visibility / Artifact 可见性

A session can publish an artifact, a web page hosted on claude.ai with the link posted in the thread, and the page stays available after the sandbox is released. Anyone with access to the source Slack channel can open it, which in a public channel covers everyone in the workspace. Someone who opens the link without that access sees a request-access prompt rather than the page. There is no share setting for anyone to change. Updates go through Claude: ask in the Slack thread, or send Claude a comment on the page, which anyone who can post in the channel can do.

session 可以发布 artifact——托管在 claude.ai 上的网页，链接发在线程里——沙箱释放后页面仍然可用。能进源 Slack 频道的人都能打开；公开频道里这覆盖工作区所有人。没有该访问的人打开链接会看到请求访问提示，而不是页面。没有任何人可以改的分享设置。更新走 Claude：在 Slack 线程里要求，或在页面上给 Claude 发评论（能在频道里发帖的人都可以）。

Artifacts you publish from your own Claude Code sessions work differently: they belong to you, and you control who can open them, with sharing options that depend on your plan and organization settings. See the Claude Code artifacts documentation.

你从自己的 Claude Code session 发布的 artifacts 不同：它们属于你，由你控制谁能打开，分享选项取决于你的计划和组织设置。见 Claude Code artifacts 文档。

Member access / 成员访问

By default, anyone in a connected Slack workspace can invoke Claude in channels, with or without a Claude account. An Owner can turn on a restriction toggle to narrow that: on Team plans it limits Claude to people with a Claude account in your organization, and on Enterprise plans it limits Claude to members whose role grants the Claude Tag in Slack capability. See Restrict who can use Claude. The toggle governs DMs as well as channels.

默认情况下，已连接 Slack 工作区里的任何人都可以在频道里调用 Claude，有没有 Claude 账户都行。Owner 可以打开限制开关来收窄：Team 计划上把 Claude 限制给组织里有 Claude 账户的人；Enterprise 计划上限制给角色授予了 Claude Tag in Slack 能力的成员。见 Restrict who can use Claude。该开关同时管私信和频道。

How agent identity works: the identity model in full, including DM attribution
Data lifecycle and deletion: what Anthropic stores, how long it’s kept, and what each action deletes
Restrict where Claude Tag operates: the controls that exist and the ones that don’t
Audit Claude Tag activity: the trails for tracing what it did
How agent identity works：完整身份模型，含私信归属
Data lifecycle and deletion：Anthropic 存什么、存多久、每个动作删什么
Restrict where Claude Tag operates：有哪些控制、没有哪些
Audit Claude Tag activity：追溯它做过什么的轨迹

3.6 - Data lifecycle and deletion

官方文档 Data lifecycle and deletion 的中英对照

来源： Data lifecycle and deletion

Data lifecycle and deletion / 数据生命周期与删除

What Claude Tag stores on Anthropic’s side, how long session transcripts and memory are kept, and what disconnecting a workspace, uninstalling the app, deleting a Slack channel, removing a scope, or leaving the organization does to that data.

Claude Tag 在 Anthropic 侧存什么、session transcripts 和记忆保留多久，以及断开工作区、卸载应用、删除 Slack 频道、移除 scope 或离开组织分别对那些数据做什么。

Claude Tag keeps a record of its work on Anthropic’s side, separate from the messages in your Slack workspace. This page is for the Owner or security reviewer who needs to know what that record contains, how long Anthropic keeps it, and which actions in Slack or in your Claude admin settings delete it. For each action, the tables below say what is deleted and whether Claude keeps responding, because the two don’t always go together.

Claude Tag 在 Anthropic 侧保留其工作的一份记录，与你 Slack 工作区里的消息分开。本页写给需要知道这份记录含什么、Anthropic 保留多久、以及 Slack 或 Claude 管理设置里哪些动作会删除它的 Owner 或安全评审人。对每个动作，下表说明删了什么、Claude 是否继续应答——这两者并不总是一起发生。

What Anthropic stores / Anthropic 存什么

There are two copies of the work Claude does in Slack. The messages, canvases, files, bookmarks, and pins in Slack stay in Slack under your workspace’s own retention settings. Anthropic doesn’t remove them when Claude-side data is deleted, and can’t once the app is uninstalled, so delete those in Slack. On Anthropic’s side, Claude Tag stores the following for each paired workspace.

Claude 在 Slack 里做的工作有两份拷贝。Slack 里的消息、canvas、文件、书签和钉选留在 Slack，遵循你工作区自己的保留设置。Claude 侧数据被删除时 Anthropic 不会移除它们，应用卸载后也做不到，所以那些要在 Slack 里删。在 Anthropic 侧，Claude Tag 为每个已配对工作区存储以下内容。

What	What it contains
Session transcripts	The record of one thread’s, channel’s, or direct message’s work. A transcript holds the messages Claude was shown in the conversation and who sent them, files attached there, earlier versions of messages that were later edited, what Claude retrieved while working (Slack search results, messages it read in channels it’s in, and data from connected tools), and everything Claude said and did
Memory	The notes Claude saves for each channel, the workspace-shared notes from public channels, and separate notes for each direct-message conversation. See What Claude Tag remembers
Routines	The scheduled and run-once tasks set up in channels or in direct messages, with their instructions and run history
Scopes and their settings	Each workspace and channel scope, with its custom instructions, version setting, and Access bundle bindings
Access bundles	The connections and credentials an Owner provisions. Bundles belong to your organization, not to a workspace
Account links	The link between each member’s Slack account and their Claude account, and the tokens that link uses
Published artifacts	Pages a session published to claude.ai. See Artifact visibility
The app’s installation credential	The token the Claude app uses to read and post in your Slack workspace

什么	含什么
Session transcripts	一条线程、一个频道或一则私信的工作记录。Transcript 保存对话里给 Claude 看过的消息及发送者、那里附上的文件、后来被编辑的消息的更早版本、Claude 工作时检索到的内容（Slack 搜索结果、它在所在频道读过的消息、来自已连接工具的数据），以及 Claude 说过和做过的一切
Memory	Claude 为每个频道保存的笔记、来自公开频道的工作区共享笔记，以及每则私信对话各自的笔记。见 What Claude Tag remembers
Routines	在频道或私信里设置的计划任务和一次性任务，含指令和运行历史
Scopes 及其设置	每个工作区和频道 scope，含自定义指令、版本设置和 Access bundle 绑定
Access bundles	Owner 配好的 connections 和凭证。Bundles 属于组织，不属于某个工作区
Account links	每个成员的 Slack 账户与 Claude 账户之间的链接，以及该链接使用的 token
Published artifacts	session 发布到 claude.ai 的页面。见 Artifact visibility
应用的安装凭证	Claude 应用用来在你的 Slack 工作区读和发的 token

Deleting or editing a message or file in Slack doesn’t remove it from a transcript that already includes it. Messages from other people in the conversation, including guests, become part of the transcript the same way and are held as your organization’s data.

在 Slack 里删除或编辑消息或文件，并不会从已经包含它的 transcript 里抹掉。对话里其他人的消息（包括访客）同样进入 transcript，并作为你组织的数据持有。

How long data is kept / 数据保留多久

During the beta there is no automatic retention period for Claude Tag data. Session transcripts, memory, routines, scopes, and account links are kept until one of the actions on this page deletes them. Your organization’s custom data retention setting doesn’t apply to Claude Tag transcripts or memory. It does apply to artifacts a session published, which follow the same retention rules as your organization’s other shared artifacts.

Beta 期间 Claude Tag 数据没有自动保留期限。Session transcripts、记忆、routines、scopes 和 account links 一直保留，直到本页某个动作删除它们。组织的自定义数据保留设置不适用于 Claude Tag 的 transcripts 或记忆。它适用于 session 发布的 artifacts，后者遵循组织其他共享 artifacts 的同一套保留规则。

Sessions Claude stops using are archived, not deleted. That includes a thread’s session after someone sends @Claude !restart, a session that closed because the thread’s first message was deleted before anyone replied, and the channel-level sessions Claude replaces after about an hour of quiet or a day of age. An archived session keeps its full transcript until the channel’s or workspace’s data is deleted.

Claude 停止使用的 session 被归档，而不是删除。这包括有人发送 @Claude !restart 之后的线程 session、因线程第一条消息在任何人回复之前被删除而关闭的 session，以及 Claude 在约一小时安静或一天年龄之后替换的频道级 session。已归档 session 保留完整 transcript，直到该频道或工作区的数据被删除。

Letting a plan lapse, turning Claude Tag off, or no longer using it doesn’t delete anything on its own. To delete a workspace’s data when you stop using Claude Tag, disconnect the workspace or uninstall the app.

让计划过期、关掉 Claude Tag、或不再使用它，本身都不会删除任何东西。停止使用 Claude Tag 时要删除一个工作区的数据，请断开该工作区或卸载应用。

When an action below deletes data, deletion starts right away and completes in the background. Copies can remain in routine backups for a limited period after that before they age out.

下面某个动作删除数据时，删除立刻开始，在后台完成。之后副本可能在常规备份里再留一段有限时间，然后老化退出。

What each action does to Claude-side data / 每个动作对 Claude 侧数据做什么

The first table covers actions taken in Slack, and the second covers actions taken in Claude. “Claude-side data” means the items listed under What Anthropic stores.

第一张表覆盖在 Slack 里采取的动作，第二张覆盖在 Claude 里采取的动作。「Claude 侧数据」指 Anthropic 存什么下列出的项目。

Actions in Slack / Slack 里的动作

Action	Claude-side data	Does Claude keep responding?
A Slack admin uninstalls the Claude app from a workspace	Deleted, the same as disconnecting the workspace, plus the app’s installation credential for that workspace. Access bundles, and routines members set up in direct messages, stay	No. The app is removed from the workspace
On Enterprise Grid, a Grid admin removes an org-wide installation of the app, from the whole grid or from one of its workspaces	Nothing is deleted. To delete the data, an Owner disconnects the grid, or a workspace that has its own pairing, in your Claude admin settings	No
A channel is deleted in Slack	Deleted: that channel’s sessions and transcripts, including earlier sessions Claude had archived there, its channel memory, and its scope with the routines and artifacts that belong to it. Notes Claude saved to workspace memory from a public channel aren’t tied to the channel and stay until you delete them or disconnect the workspace, as does anything created under the workspace scope rather than the channel’s own	Not applicable
A channel is archived in Slack	Nothing is deleted. Unarchiving the channel picks its memory, routines, and sessions back up	Not while the channel is archived
A public channel is made private	Nothing is deleted. Claude archives the channel’s earlier sessions, and new sessions save to the channel’s own memory store. Notes Claude saved to workspace memory while the channel was public stay there, readable from the workspace’s other channels; see Workspace memory	Yes
Someone removes Claude from a channel with `/remove @Claude`	Nothing is deleted. The channel’s memory, routines, and past sessions stay on record, and re-adding Claude picks them back up. The channel’s routines keep firing while Claude is out of the channel but can’t post there	No
Someone edits a message Claude read	Claude receives the edit as a note, and the transcript keeps both the earlier and the edited text	Yes
Someone deletes a reply, or deletes a thread’s first message after others have replied	Nothing is removed from the transcript, and Claude isn’t notified	Yes
Someone deletes a thread’s first message before anyone has replied	The session closes and is archived with its transcript, including the deleted message	No. The thread is gone
Someone deletes a file they attached in a thread Claude worked in	The copy Claude took into the session stays with the session and its transcript	Yes
A member’s Slack account is deactivated	Nothing is deleted. Their account link, direct-message conversations and notes, and their messages in channel transcripts stay. Channel routines they created keep running, and routines they set up in direct messages keep running until they’re removed from your Claude organization	Not to that member

动作	Claude 侧数据	Claude 是否继续应答？
Slack 管理员从工作区卸载 Claude 应用	删除，与断开工作区相同，外加该工作区的应用安装凭证。Access bundles，以及成员在私信里设置的 routines，留下	否。应用已从工作区移除
Enterprise Grid 上，Grid 管理员移除应用的组织级安装（整个 grid 或其中一个工作区）	什么都不删。要删数据，由 Owner 在 Claude 管理设置里断开该 grid，或断开有自己配对的工作区	否
在 Slack 里删除一个频道	删除：该频道的 session 和 transcripts（含 Claude 在那里归档过的更早 session）、其频道记忆，以及属于它的 scope 连同 routines 和 artifacts。Claude 从公开频道存到工作区记忆的笔记不绑在该频道上，会留下直到你删除它们或断开工作区；在工作区 scope 而不是频道自己的 scope 下创建的东西也一样	不适用
在 Slack 里归档一个频道	什么都不删。取消归档会把记忆、routines 和 session 捡回来	频道处于归档时否
公开频道改为私有	什么都不删。Claude 归档该频道更早的 session，新 session 存到频道自己的记忆存储。频道公开时 Claude 存到工作区记忆的笔记留在那里，可从工作区其他频道读取；见 Workspace memory	是
有人用 `/remove @Claude` 把 Claude 移出频道	什么都不删。频道的记忆、routines 和过去的 session 留在记录上，再加回 Claude 会捡回来。Claude 不在频道时，该频道的 routines 仍会触发，但不能在那里发帖	否
有人编辑 Claude 读过的消息	Claude 把编辑作为一条说明收到，transcript 同时保留更早文本和编辑后文本	是
有人删除一条回复，或在已有他人回复后删除线程第一条消息	transcript 里什么都不移除，Claude 也收不到通知	是
有人在任何人回复之前删除线程第一条消息	session 关闭并连同 transcript 归档，包括被删的那条消息	否。线程没了
有人删除自己在 Claude 工作过的线程里附上的文件	Claude 带进 session 的那份拷贝仍随 session 及其 transcript	是
成员的 Slack 账户被停用	什么都不删。其 account link、私信对话和笔记、以及频道 transcripts 里他们的消息留下。他们创建的频道 routines 继续跑；他们在私信里设置的 routines 继续跑，直到他们被移出 Claude 组织	不对该成员

Actions in Claude / Claude 里的动作

Action	Claude-side data	Does Claude keep responding?
An Owner disconnects a workspace	Deleted: the workspace’s sessions and transcripts, including members’ direct-message conversations there; its channel, workspace, and direct-message memory; the routines set up in its channels and the artifacts published from them; its scopes with their instructions and bundle bindings; and members’ account links. The Slack app and its installation credential stay so a workspace admin can pair again, and Access bundles, routines members set up in direct messages, and what Claude posted in Slack stay too. Pairing the same workspace to the same organization again within a few minutes can cancel the deletion	Stops in channels immediately. Direct messages keep working on each member’s own Claude account until the deletion removes that member’s account link
An Owner disconnects an Enterprise Grid	The same as disconnecting a workspace, for every workspace in the grid that doesn’t have its own workspace pairing, plus the app’s installation credentials for those workspaces. Workspaces you paired individually stay connected and keep their data until you disconnect them	Stops in the affected workspaces
An Owner removes a channel’s scope with Remove this scope in the Claude Tag’s access section	Deleted: the channel’s sessions and transcripts recorded up to that moment, including threads still in progress, its memory, its routines, and the artifacts published from it. The Slack channel itself is unchanged	Yes. Claude stays in the channel and, when tagged again, starts fresh under the access it inherits from the workspace. To stop it as well, run `/remove @Claude` or set the scope’s version to Off first
An Owner sets a scope’s version to Off, turns off Claude in Slack for the organization, or turns off direct messages	Nothing is deleted. Turning the setting back on resumes with the existing memory, routines, and sessions	No, in the affected scope
An Owner detaches a bundle from a scope, or deletes an Access bundle	Detaching removes the binding, and deleting a bundle removes its credentials everywhere it was attached. Memory, routines, and transcripts are unaffected	Yes, without that access
An Owner deletes entries from a scope’s memory files, or someone in the channel tells Claude to forget an entry	The entry is removed from what Claude reads and from the memory files view. Earlier versions of the scope’s memory remain stored with the scope until the scope’s data is deleted	Yes
An Owner deletes a routine from the Scheduled work tab, or someone asks Claude to delete it in the channel or direct message where it was set up	The routine and the sessions it ran are deleted. Pausing a routine there, or disabling it from the channel, keeps it on record	Yes
A member selects Disconnect in the Claude app’s Home tab in Slack	Removes the link between their Slack and Claude accounts and revokes the tokens Claude Tag held for them. Their earlier direct-message conversations and notes, and channel work they started, aren’t deleted; those go with the workspace	In channels, yes. Direct messages and personal connectors stop working for that member until they reconnect
A member is removed from your Claude organization	Nothing is deleted. They lose access within minutes, and routines they set up in direct messages are turned off. Their account link, direct-message conversations, and notes stay until the workspace is disconnected	Not to that member
A member deletes their own Claude account	On Team and Enterprise plans, deleting an individual account doesn’t remove the Claude Tag data your organization holds about that member, including their direct-message conversations and notes and their account link. A member who wants the link and its tokens removed can select Disconnect in Slack before deleting their account	Not to that member
Your Claude organization is deleted	All Claude Tag data for every paired workspace is deleted as part of the organization deletion. The Slack app isn’t uninstalled by this, and its installation credential remains until the app is uninstalled, so uninstall it from each workspace in Slack as well	No
Your organization adopts Zero Data Retention or another restricted compliance configuration after pairing	Nothing already stored is deleted. Disconnect each workspace to delete its data	No. Claude stops responding in Slack and new pairings are refused; see Restricted compliance settings block Claude Tag

动作	Claude 侧数据	Claude 是否继续应答？
Owner 断开一个工作区	删除：该工作区的 session 和 transcripts（含成员在那里的私信对话）；其频道、工作区和私信记忆；在其频道里设置的 routines 以及从它们发布的 artifacts；其 scopes 连同指令和 bundle 绑定；以及成员的 account links。Slack 应用及其安装凭证留下，以便工作区管理员可以再配对；Access bundles、成员在私信里设置的 routines，以及 Claude 在 Slack 里发过的内容也留下。几分钟内把同一工作区再配对到同一组织，可以取消这次删除	频道里立刻停止。私信继续在每个成员自己的 Claude 账户上工作，直到删除移除该成员的 account link
Owner 断开一个 Enterprise Grid	与断开工作区相同，作用于 grid 里没有自己工作区配对的每一个工作区，外加那些工作区的应用安装凭证。你单独配对过的工作区保持连接并保留数据，直到你断开它们	在受影响的工作区停止
Owner 在 Claude Tag 的 access 区用 Remove this scope 移除一个频道的 scope	删除：截至那一刻记录的该频道 session 和 transcripts（含仍在进行的线程）、其记忆、其 routines，以及从它发布的 artifacts。Slack 频道本身不变	是。Claude 留在频道里，再次被 Tag 时在从工作区继承的访问下重新开始。若也要停下它，先跑 `/remove @Claude` 或把该 scope 的版本设为 Off
Owner 把某个 scope 的版本设为 Off、为组织关掉 Claude in Slack，或关掉私信	什么都不删。把设置再打开会带着已有记忆、routines 和 session 恢复	否，在受影响的 scope 里
Owner 从某个 scope 卸下一个 bundle，或删除一个 Access bundle	卸下移除绑定；删除 bundle 会在它被绑过的所有地方移除其凭证。记忆、routines 和 transcripts 不受影响	是，只是没有那份访问
Owner 从某个 scope 的 memory files 删除条目，或频道里有人让 Claude 忘掉一条	该条目从 Claude 所读内容和 memory files 视图里移除。该 scope 记忆的更早版本仍随 scope 存储，直到该 scope 的数据被删除	是
Owner 从 Scheduled work 页删除一条 routine，或有人在设置它的频道或私信里请 Claude 删除它	该 routine 以及它跑过的 session 被删除。在那里暂停，或从频道禁用，会把它留在记录上	是
成员在 Slack 里 Claude 应用的 Home 页选择 Disconnect	移除其 Slack 与 Claude 账户之间的链接，并撤销 Claude Tag 为他们持有的 token。他们更早的私信对话和笔记、以及他们启动的频道工作不会被删；那些跟着工作区走	频道里是。对该成员，私信和个人 connectors 停止工作，直到他们重新连接
成员被移出你的 Claude 组织	什么都不删。他们在几分钟内失去访问，他们在私信里设置的 routines 被关掉。其 account link、私信对话和笔记留下，直到工作区被断开	不对该成员
成员删除自己的 Claude 账户	在 Team 和 Enterprise 计划上，删除个人账户并不会移除组织持有的关于该成员的 Claude Tag 数据，包括其私信对话和笔记及其 account link。想移除链接及其 token 的成员，可以在删账户之前在 Slack 里选择 Disconnect	不对该成员
你的 Claude 组织被删除	每个已配对工作区的全部 Claude Tag 数据作为组织删除的一部分被删除。这不会卸载 Slack 应用，其安装凭证留到应用被卸载，因此也要在 Slack 里从每个工作区卸载它	否
配对之后组织采用 Zero Data Retention 或其他受限合规配置	已经存储的什么都不删。断开每个工作区以删除其数据	否。Claude 停止在 Slack 应答，新配对被拒绝；见 Restricted compliance settings block Claude Tag

Direct messages / 私信

A direct-message conversation with Claude is stored the same way a channel thread is, as a session with a transcript, together with the notes Claude keeps for that conversation. Both are deleted with the workspace the member messaged Claude from, when that workspace is disconnected or the app is uninstalled from it, and when your Claude organization is deleted. They aren’t deleted when the member selects Disconnect in Slack, when the member’s Claude account is deleted on a Team or Enterprise plan, or when an Owner turns off direct messages.

与 Claude 的私信对话按频道线程同样的方式存储：一个带 transcript 的 session，加上 Claude 为该对话保留的笔记。二者随成员向 Claude 发过消息的那个工作区一起删除——当该工作区被断开、应用从它卸载，或你的 Claude 组织被删除时。成员在 Slack 里选择 Disconnect、Team/Enterprise 计划上删除该成员的 Claude 账户、或 Owner 关掉私信时，它们不会被删。

Routines a member set up in a direct message belong to that member’s Claude account. An Owner can delete them from the Scheduled work tab, or the member can ask Claude in the direct message to delete one. They are turned off when the member is removed from your Claude organization, and disconnecting the workspace doesn’t delete them.

成员在私信里设置的 routines 属于该成员的 Claude 账户。Owner 可以从 Scheduled work 页删除它们，或该成员在私信里请 Claude 删除一条。成员被移出 Claude 组织时它们被关掉；断开工作区并不会删除它们。

When a member first opens a direct message with Claude, the welcome Claude writes, which suggests channels based on the member’s recent public-channel activity, runs as a short session that is stored like any other.

成员第一次打开与 Claude 的私信时，Claude 写的欢迎（根据该成员近期公开频道活动建议频道）跑成一个短 session，像其他任何 session 一样被存储。

Delete data or request deletion / 删除数据或请求删除

The controls that delete Claude Tag data, from largest to smallest:

删除 Claude Tag 数据的控件，从大到小：

Disconnect a workspace or an Enterprise Grid at claude.ai/admin-settings/claude-tag, or uninstall the app from the workspace in Slack. Deletes all of that workspace’s data. See Revoke a pairing
Remove a channel’s scope in the Claude Tag’s access section. Deletes that channel’s data recorded so far
Delete a scope’s memory files, from the scope’s options menu, or tell Claude in the channel to forget an entry. See Check and correct what Claude Tag remembers
Delete a routine from the Scheduled work tab, or ask Claude to delete it in the channel or direct message where it was set up. See Audit Claude Tag activity
在 claude.ai/admin-settings/claude-tag 断开一个工作区或 Enterprise Grid，或在 Slack 里从工作区卸载应用。删除该工作区的全部数据。见 Revoke a pairing
在 Claude Tag 的 access 区移除一个频道的 scope。删除该频道迄今记录的数据
从 scope 的选项菜单删除其 memory files，或在频道里让 Claude 忘掉一条。见 Check and correct what Claude Tag remembers
从 Scheduled work 页删除一条 routine，或在设置它的频道或私信里请 Claude 删除它。见 Audit Claude Tag activity

There is no control in Slack or in your Claude admin settings that deletes a single thread’s transcript on its own. During the beta, Claude Tag session transcripts and memory aren’t included in your organization’s data exports, and the Compliance API doesn’t list or delete Claude Tag sessions. For a deletion request these controls don’t cover, contact your account team or privacy@anthropic.com.

Slack 或 Claude 管理设置里没有单独删除某一条线程 transcript 的控件。Beta 期间，Claude Tag 的 session transcripts 和记忆不包含在组织的数据导出里，Compliance API 也不列出或删除 Claude Tag session。这些控件覆盖不到的删除请求，联系你的客户团队或 privacy@anthropic.com。

Audit records for deletions / 删除的审计记录

Disconnecting a workspace or an Enterprise Grid, and removing a channel’s scope, are recorded in your organization’s audit log, which you read through the Compliance API. Deletions that start in Slack, such as deleting a channel or uninstalling the app, aren’t recorded there, and neither is a member’s Disconnect in the Home tab.

断开工作区或 Enterprise Grid，以及移除一个频道的 scope，会记入组织的审计日志，通过 Compliance API 阅读。从 Slack 开始的删除（例如删频道或卸载应用）不记在那里，成员在 Home 页的 Disconnect 也不记。

Security and data handling: sandbox isolation, credential storage, and artifact visibility
Manage workspaces and versions: the Disconnect control and what it deletes
Restrict where Claude Tag operates: the ways to quiet or remove Claude, and which keep data
What Claude Tag remembers: reading, correcting, and deleting memory
Audit Claude Tag activity: scheduled work, memory files, and network events
Security and data handling：沙箱隔离、凭证存储、artifact 可见性
Manage workspaces and versions：Disconnect 控件以及它删什么
Restrict where Claude Tag operates：让 Claude 安静或移除它的方式，以及哪些会保留数据
What Claude Tag remembers：读、纠正和删除记忆
Audit Claude Tag activity：计划工作、memory files 与网络事件

3.7 - Claude Tag settings map

官方文档 Claude Tag settings map 的中英对照

来源： Claude Tag settings map

Claude Tag settings map / Claude Tag 设置地图

Claude Tag settings map: the admin page for access and behavior, the usage page for spend limits, the in-Slack Configure link for channel instructions, and personal connectors for DMs. Claude Managed Agents is configured separately on the Claude Platform.

Claude Tag 设置地图：管访问与行为的管理页、管 spend limits 的用量页、Slack 里 Configure 链接对应的频道指令，以及私信用的个人 connectors。Claude Managed Agents 在 Claude Platform 上单独配置。

Claude Tag’s settings live on claude.ai, split across a few pages that each own a different kind of setting. Which page you need depends on what you’re changing. The table maps each surface to what it controls.

Claude Tag 的设置在 claude.ai 上，拆到几页，每页管一类设置。你需要哪一页取决于你在改什么。下表把每个面映射到它控制的内容。

Surface	Who changes it	What it controls
Claude Tag admin page	An Owner in your Claude organization	Access, behavior, and restrictions for channels, per scope
Usage page	An admin	Spend limits and each channel’s spend against them
Analytics page	Anyone who can view the Analytics dashboard	Spend trends, projections, and per-channel reports; read-only
The Configure link in the footer of any Claude reply in a channel	Channel members (unless an admin restricts editing) and channel managers for their assigned channels	One channel’s instructions and whether Claude replies there without an @-mention. Channel managers also set the channel’s default model, repositories, and connections
Customize > Connectors on your own claude.ai account	You	Which of your personal tools apply in DMs

界面	谁改	控制什么
Claude Tag 管理页	Claude 组织中的 Owner	按 scope 的频道访问、行为与限制
用量页	管理员	Spend limits，以及各频道相对限额的花费
Analytics 页	能看 Analytics 仪表盘的任何人	花费趋势、预测、按频道报告；只读
频道里任意 Claude 回复页脚的 Configure 链接	频道成员（除非管理员限制编辑）以及被指派频道的 channel managers	一个频道的指令，以及 Claude 是否在没有 @提及时回复。Channel managers 还设定该频道的默认模型、仓库和 connections
你自己 claude.ai 账户上的 Customize > Connectors	你	哪些个人工具在私信里生效

Channel memory and routines aren’t in the table because you change them by talking to Claude in the channel; see what anyone can change from the channel. Owners can review both, as each scope’s memory files and scheduled work, from the Audit page, labeled Activity in the console.

频道记忆和 routines 不在表里，因为你通过在频道里跟 Claude 说话来改它们；见频道里任何人能改什么。Owner 可以从 Audit 页（控制台里标为 Activity）审阅二者，即每个 scope 的 memory files 和 scheduled work。

The Claude Tag admin page / Claude Tag 管理页

Everything an Owner configures for channels lives at claude.ai/admin-settings/claude-tag. Settings there apply per scope (a channel, a workspace, or the whole organization). A scope without its own setting inherits from its parent, and a channel’s setting overrides its workspace’s, so two channels can run with different connections, models, and instructions. Most controls are Owner-only; the permissions table lists each action and who can take it.

Owner 为频道配置的一切都在 claude.ai/admin-settings/claude-tag。那里的设置按 scope 生效（一个频道、一个工作区或整个组织）。没有自己设置的 scope 从父级继承，频道的设置覆盖其工作区的，因此两个频道可以跑不同的 connections、模型和指令。多数控件仅 Owner 可用；权限表列出每项动作以及谁能做。

Access bundles: the connections, domain entries, repository grants, and plugins Claude uses in the channels a bundle covers. See Give Claude access.
Custom instructions: standing guidance Claude reads in every session on a scope. See Add custom instructions.
Default model: the model new sessions in a scope start on. The picker shows the models your organization allows for Claude Code, leaving out any that Claude Tag doesn’t support, so it can be missing models you see in Claude Code itself. See Choose the model for a scope.
Auto mode allow rules: plain sentences that pre-approve actions Claude’s permission checker would otherwise flag or stop in a scope’s sessions. See Auto mode allow rules.
Workspace pairing and restrictions: which Slack workspaces are paired, whether DMs are allowed, guest-channel behavior, who can invoke Claude, and which generation of the app answers in each scope (on the Team plan, a single Enable Claude Tag switch replaces the per-scope setting). See Restrict where Claude Tag operates.
Channel name rules: channel-name patterns that keep Claude out of matching channels or join it automatically to new public ones. See Block or auto-join channels by name.
Access bundles： Claude 在 bundle 覆盖的频道里使用的 connections、域名条目、仓库授权和 plugins。见 Give Claude access。
Custom instructions： Claude 在某个 scope 的每个 session 里读的常驻指引。见 Add custom instructions。
Default model： 某个 scope 里新 session 启动时用的模型。选择器显示组织允许给 Claude Code 用的模型，并去掉 Claude Tag 不支持的，因此可能缺少你在 Claude Code 本身看到的模型。见 Choose the model for a scope。
Auto mode allow rules： 用普通句子预先批准 Claude 的权限检查器否则会标记或拦住的动作，作用于某个 scope 的 session。见 Auto mode allow rules。
工作区配对与限制： 哪些 Slack 工作区已配对、是否允许私信、访客频道行为、谁能调用 Claude，以及每个 scope 由哪一代应用应答（Team 计划上，单个 Enable Claude Tag 开关代替按 scope 的设置）。见 Restrict where Claude Tag operates。
频道名规则： 频道名模式，用来让 Claude 远离匹配的频道，或自动加入新的公开频道。见 Block or auto-join channels by name。

Spend limits and usage / Spend limits 与用量

Spend limits live at claude.ai/admin-settings/usage/claude-tag, a different page than the Claude Tag admin page. It holds the organization-wide spend limit, the default spend limit for channels, per-channel limits, and each channel’s spend against its limit. If your organization bills through a reseller, this page is not available. See Set a spend limit for funding the usage balance and what users see when a limit is reached.

Spend limits 在 claude.ai/admin-settings/usage/claude-tag，与 Claude Tag 管理页不同。它容纳全组织 spend limit、频道默认限额、按频道限额，以及各频道相对其限额的花费。若组织通过经销商计费，此页不可用。如何注入用量余额、限额触达时用户看到什么，见 Set a spend limit。

Spend trends live at claude.ai/analytics/claude-tag, the Claude Tag section of the Analytics dashboard. It shows total and projected spend, spend by channel, and spend by kind of work for the period you pick, and anyone with permission to view the Analytics dashboard can open it. It has no controls; see Usage analytics.

花费趋势在 claude.ai/analytics/claude-tag，即 Analytics 仪表盘的 Claude Tag 区。它显示你所选时段的总花费与预测花费、按频道花费、按工作种类花费；有权查看 Analytics 仪表盘的人都能打开。它没有控件；见 Usage analytics。

The Configure page / Configure 页

Every Claude reply in a channel ends with a footer, and its Configure link opens a claude.ai page for that channel; replies in DMs have no Configure link. You can also send @Claude !configure in the channel, and Claude replies with a link to the same page.

频道里每条 Claude 回复都以页脚结束，其中的 Configure 链接打开该频道的 claude.ai 页；私信里的回复没有 Configure 链接。你也可以在频道里发 @Claude !configure，Claude 会回复同一页的链接。

Anyone in the channel who is also a member of your Claude organization can edit the Channel instructions field on that page, unless an admin has restricted editing to admins. The page’s Respond automatically toggle controls whether Claude replies in the channel without an @-mention; see Turn automatic replies on or off.

频道里同时也是 Claude 组织成员的人，都可以编辑该页的 Channel instructions 字段，除非管理员已把编辑限制为仅管理员。该页的 Respond automatically 开关控制 Claude 是否在没有 @提及时回复频道；见 Turn automatic replies on or off。

The page’s Tools and access tab shows the channel’s resolved connections and any allowed domains. Members can see those lists but not change them there. The same tab’s Plugins card lists the channel’s plugins, and members can add plugins there unless an admin has restricted editing to admins. A Routines tab lists the channel’s routines with each one’s schedule, status, and last run.

该页的 Tools and access 页显示频道解析后的 connections 以及任何允许的域名。成员能看见这些列表，但不能在那里改。同一页的 Plugins 卡片列出频道的 plugins，成员可以在那里添加 plugins，除非管理员已把编辑限制为仅管理员。Routines 页列出频道的 routines，含各自的日程、状态和上次运行。

The Configure page and the Custom instructions field on the scope’s panel in admin settings write the same instructions, so a change from either place is visible in the other. See Configure Claude for a channel.

Configure 页与管理设置里该 scope 面板上的 Custom instructions 字段写的是同一套指令，因此任一处的变更在另一处可见。见 Configure Claude for a channel。

On the Enterprise plan, an Owner can name channel managers for a channel. For them, the same page adds editable cards: the channel’s default model on the General tab, and its repositories and access bundles on the Tools and access tab.

Enterprise 计划上，Owner 可以为一个频道指定 channel managers。对他们，同一页会多出可编辑卡片：General 页上的频道默认模型，以及 Tools and access 页上的仓库和 access bundles。

Personal connectors on claude.ai / claude.ai 上的个人 connectors

Connectors you add to your own claude.ai account, under Customize > Connectors, apply only in DMs with Claude, because a DM runs on your own account. A channel uses only the connections an admin attached to it, and personal connectors never apply there. Slack has no connector settings of its own.

你在自己 claude.ai 账户的 Customize > Connectors 下添加的 connectors，只在与 Claude 的私信里生效，因为私信跑在你自己的账户上。频道只用管理员绑给它的 connections，个人 connectors 从不在那里生效。Slack 没有自己的 connector 设置。

See connectors on claude.ai for setting one up, and the troubleshooting entry if a connector you use on claude.ai is missing in Slack.

如何设置见 claude.ai 上的 connectors；若你在 claude.ai 上用的 connector 在 Slack 里缺失，见故障排除条目。

Claude Tag versus Claude Managed Agents / Claude Tag vs. Claude Managed Agents

Claude Managed Agents is a separate product for developers, a pre-built agent harness that runs in managed infrastructure. You configure it on the Claude Platform through the Managed Agents API, and access requires a Claude API key. An agent there is defined by its model, system prompt, tools, MCP servers, and skills. Environments choose where its sessions run (a cloud sandbox, or a self-hosted sandbox on your own infrastructure), and scheduled deployments run it on a cron schedule.

Claude Managed Agents 是面向开发者的另一款产品：跑在托管基础设施上的预构建 agent harness。你在 Claude Platform 上通过 Managed Agents API 配置它，访问需要 Claude API 密钥。那里的 agent 由其模型、系统提示、工具、MCP 服务器和 skills 定义。Environments 选择其 session 跑在哪里（云沙箱，或你们自己基础设施上的自托管沙箱），计划部署按 cron 跑它。

The two products don’t share settings. Nothing on the Claude Tag admin page configures a Managed Agent, and an agent defined on the Claude Platform doesn’t change how Claude behaves in Slack.

两款产品不共享设置。Claude Tag 管理页上没有任何东西配置 Managed Agent；在 Claude Platform 上定义的 agent 也不会改变 Claude 在 Slack 里的行为。

Customize Claude Tag: the layers that shape Claude’s behavior in a channel and who sets each one
How agent identity works: why channels and DMs use different access
Set up Claude Tag: where each setting is first created during setup
Customize Claude Tag：塑造 Claude 在频道里行为的各层，以及谁设置每一层
How agent identity works：为何频道和私信用不同访问
Set up Claude Tag：设置过程中每项设置最初在哪里创建

3.8 - Claude Tag for Claude Code users

官方文档 Claude Tag for Claude Code users 的中英对照

来源： Claude Tag for Claude Code users

Claude Tag for Claude Code users / 给 Claude Code 用户的 Claude Tag

Which parts of a Claude Code setup carry into Claude Tag, which move to admin settings, and how Slack threads map to sessions.

Claude Code 配置里哪些能带到 Claude Tag，哪些改由管理设置接管，以及 Slack 线程如何映射到 session。

Claude Tag runs the same engine as Claude Code. When you tag @Claude in Slack with a task, a session starts in a sandbox that your organization configures, not on your machine. That sandbox is the same infrastructure that runs Claude Code on the web, described in Compute and the sandbox.

Claude Tag 跑的是与 Claude Code 同一套引擎。你在 Slack 里用 @Claude Tag 一项任务时，session 在组织配置的沙箱里开始，而不是在你的机器上。那个沙箱就是网页上 Claude Code 用的同一套基础设施，见 Compute and the sandbox。

If you use Claude Code on the web, a session works the way a web session does, from a fresh clone of your repository rather than from files on your machine. The CLAUDE.md files and skills you checked into that repository apply in the session as they do in a web session.

若你用网页上的 Claude Code，session 的工作方式与 web session 相同：从仓库的全新克隆开始，而不是从你机器上的文件。你提交进该仓库的 CLAUDE.md 文件和 skills 会像在 web session 里一样应用到这个 session。

If you run Claude Code in your terminal, the settings on your own machine don’t reach a session, because the session runs in the sandbox and can’t read your machine. For most of those settings, an admin sets a channel-wide counterpart instead, and a few have no counterpart at all. This page shows what happens when a session starts, which admin settings replace your local ones, and how Slack threads map to sessions.

若你在终端里跑 Claude Code，你机器上的设置到不了 session，因为 session 跑在沙箱里，读不到你的机器。对这些设置中的大多数，管理员会设一套频道级对应物；少数完全没有对应物。本页说明 session 启动时发生什么、哪些管理设置替换你的本地设置，以及 Slack 线程如何映射到 session。

What happens when a session starts / Session 启动时发生什么

A session begins with a fresh sandbox and no repository checked out. Your repository’s Claude Code configuration takes effect only after Claude clones the repository, which happens when your message names a repository that an admin has granted to the channel.

session 从全新沙箱开始，没有检出任何仓库。你仓库里的 Claude Code 配置只有在 Claude 克隆该仓库之后才生效；这发生在你的消息点名了一个管理员已授予该频道的仓库时。

Step	What applies
You tag `@Claude` with a task	Your message is the task, and Claude starts work in a sandbox with no repository
Your message names a granted repository	Claude clones it into the sandbox
The clone completes	`CLAUDE.md`, `.claude/CLAUDE.md`, `.claude/rules/*.md`, and the skills in `.claude/skills/` load into the session

步骤	什么生效
你用 `@Claude` Tag 一项任务	你的消息就是任务，Claude 在没有仓库的沙箱里开始工作
你的消息点名了一个已授予的仓库	Claude 把它克隆进沙箱
克隆完成	`CLAUDE.md`、`.claude/CLAUDE.md`、`.claude/rules/*.md` 以及 `.claude/skills/` 里的 skills 加载进 session

Hooks in the repository’s .claude/settings.json don’t run in the session.

仓库 .claude/settings.json 里的 hooks 不会在 session 里运行。

Local settings versus admin settings / 本地设置 vs. 管理设置

A session reads configuration from your repository, not from your machine. The CLAUDE.md files and skills you checked into the repository load when Claude clones it, as described in What happens when a session starts.

session 从你的仓库读配置，而不是从你的机器。你提交进仓库的 CLAUDE.md 文件和 skills 在 Claude 克隆它时加载，见 Session 启动时发生什么。

The settings on your machine never load into a session, because a session runs in the sandbox and can’t read your machine. That includes your ~/.claude directory, your personal settings.json, your shell environment, and the MCP servers you configured locally. They still apply when you run Claude Code in your terminal.

你机器上的设置永远不会加载进 session，因为 session 跑在沙箱里，读不到你的机器。这包括你的 ~/.claude 目录、个人 settings.json、shell 环境，以及你在本地配置的 MCP 服务器。你在终端里跑 Claude Code 时它们仍然生效。

Admin counterparts for local settings / 本地设置的管理侧对应物

The table shows what takes the place of each setting from your machine. Where a counterpart exists, an admin sets it for the whole channel.

下表显示你机器上每项设置由什么替代。有对应物时，由管理员为整个频道设置。

Claude Code setting on your machine	In Claude Tag
`/model`	An admin sets the default model per channel, and you can switch models in a thread
Effort level	Not configurable. Sessions run at the model’s default effort.
MCP servers in `.mcp.json`	Not loaded, even when `.mcp.json` is checked into the repository. A session reaches external services only through the connections an admin set for the channel, and each connection holds that service’s credentials.
Secrets and API keys in your environment	An admin provisions them as channel connections. The raw key never enters the sandbox. It is added to requests at the network layer.
Environment variables	An admin sets them on the environment the channel’s sessions run on, and every session in the channel reads them. There is no per-person environment to customize. The values are readable in every session on the environment, so ask an admin to add secrets as connections instead.
A personal `settings.json`	Not loaded.
A setup script for your workspace	An admin sets a setup script on the environment the channel’s sessions run on, and what it installs is in place when each session in the channel starts. For setup that belongs to one repository, use `CLAUDE.md` install steps instead.
Permission prompts	Sessions run in auto mode, where Claude’s permission checker reviews each action and can stop it. An admin pre-approves routine actions with auto mode allow rules instead of you approving in the moment.

你机器上的 Claude Code 设置	在 Claude Tag 里
`/model`	管理员按频道设默认模型，你可以在线程里切换模型
Effort level	不可配置。Session 以模型的默认 effort 运行。
`.mcp.json` 里的 MCP 服务器	不加载，即使 `.mcp.json` 已提交进仓库。session 只通过管理员为该频道设置的 connections 到达外部服务，每条 connection 持有该服务的凭证。
环境里的 secrets 和 API keys	管理员把它们配成频道 connections。原始密钥从不进入沙箱。它在网络层被加到请求上。
环境变量	管理员设在该频道 session 所跑的 environment 上，频道里每个 session 都读它们。没有按人定制的 environment。这些值在该 environment 的每个 session 里可读，因此请管理员把 secrets 加成 connections。
个人 `settings.json`	不加载。
工作区的 setup script	管理员把 setup script 设在该频道 session 所跑的 environment 上，频道里每个 session 启动时安装内容已就位。属于某一个仓库的安装步骤，改用 `CLAUDE.md`。
权限提示	Session 跑在 auto mode，Claude 的权限检查器审阅每个动作并可以拦住。管理员用 auto mode allow rules 预先批准常规动作，而不是由你当场批准。

To change what a session can reach, ask an admin to add a connection. The change applies to every session in the channel.

要改变 session 能触及什么，请管理员加一条 connection。变更对该频道里每个 session 生效。

How Slack threads map to sessions / Slack 线程如何映射到 session

You start a session by tagging @Claude in a thread with a task, and that session gets its own sandbox. Each reply in the same thread continues the session, so there is no --continue or /resume to run, and a session stays attached to the thread it started in. See the lifecycle of a request for what happens between replies.

你在线程里用 @Claude Tag 一项任务来开始 session，该 session 有自己的沙箱。同一线程里的每条回复都继续这个 session，因此没有 --continue 或 /resume 可跑，session 一直附着在它开始的那条线程上。回复之间发生什么，见 lifecycle of a request。

Each thread is its own session with its own sandbox, so run parallel tasks in separate threads the way you would in separate terminal tabs. The sandbox is released after a quiet period, but the conversation stays in the thread, and a later reply continues the session. See what survives between replies.

每条线程是自己的 session、自己的沙箱，因此并行任务开在分开的线程里，就像开在分开的终端标签页。安静一段时间后沙箱被释放，但对话留在线程里，稍后的回复会继续这个 session。见 what survives between replies。

Whose credentials a session uses / Session 用谁的凭证

Claude Code acts with your credentials. What a session acts with depends on whether you tag Claude in a channel or in a direct message.

Claude Code 用你的凭证行事。session 用什么，取决于你在频道还是在私信里 Tag Claude。

In a channel / 在频道里

In a channel, Claude acts with credentials of its own, service accounts that an admin provisions. A pull request comes from the Claude GitHub App rather than from you, and a query against a connected service runs with the channel’s credentials no matter who asked. Access is set per channel, not per person.

在频道里，Claude 用它自己的凭证行事——管理员配好的服务账号。拉取请求来自 Claude GitHub App 而不是你；对已连接服务的查询无论谁问，都用频道的凭证。访问按频道设定，不按人。

In a direct message / 在私信里

A direct message runs on your own claude.ai account, with the connectors you added to that account rather than the connections an admin set for the channel, so a DM is the closest match to a Claude Code session on your own credentials.

私信跑在你自己的 claude.ai 账户上，用的是你加到该账户的 connectors，而不是管理员为频道设置的 connections，因此私信是最接近「用你自己凭证的 Claude Code session」的形态。

Steer a session in the thread / 在线程里转向 session

Where you would interrupt Claude Code and edit a file or reprompt, reply in the thread. Corrections and added constraints land as messages, and Claude folds them into the running task.

你会打断 Claude Code 去改文件或重写提示的地方，改成在线程里回复。纠正和追加约束作为消息落地，Claude 把它们折进正在跑的任务。

Keep instructions in channel memory / 把指令放进频道记忆

For instructions that should persist beyond one thread, use channel memory, the instructions Claude keeps for one channel and reads in every session there. Keep repository conventions in CLAUDE.md. Put channel conventions in memory by telling Claude to remember them:

应跨越一条线程持久存在的指令，用频道记忆——Claude 为某一个频道保留、并在那里每个 session 里阅读的指令。仓库惯例放在 CLAUDE.md。频道惯例放进记忆，告诉 Claude 记住它们：

@Claude remember for this channel: reports go out as tables

@Claude remember for this channel: reports go out as tables

See What Claude remembers for how memory is scoped and how to correct it.

记忆如何划定范围、如何纠正，见 What Claude remembers。

Claude Tag versus a bot you build on the API / Claude Tag vs. 你用 API 自建的机器人

A Slack bot you build on the Claude API is software your team writes and hosts. It calls the API with your key, holds its own Slack tokens, and has the tools and memory you code into it.

你基于 Claude API 自建的 Slack 机器人，是团队自己写、自己托管的软件。它用你的密钥调 API，持有自己的 Slack token，工具和记忆是你编进去的。

Claude Tag is Anthropic’s hosted Slack app. It takes care of the parts you would otherwise build.

Claude Tag 是 Anthropic 托管的 Slack 应用。它包办了你否则得自己建的那些部分。

Hosting. Each thread gets a Claude Code session in a sandbox Anthropic runs, or in the environment your organization pins, under an agent identity of its own.
Credentials. An admin gives Claude connections to your tools, and Agent Proxy attaches the credentials at the network boundary, outside the sandbox.
Customization. Custom instructions, channel memory, and routines are built in.
Governance and billing. Access controls and spend limits are set in claude.ai admin settings, and usage is billed to the organization’s usage balance.
托管。 每条线程在 Anthropic 跑的沙箱里（或组织钉住的 environment 里）获得一个 Claude Code session，落在它自己的 agent identity 下。
凭证。 管理员给 Claude 配到你们工具的 connections，Agent Proxy 在网络边界、沙箱之外附上凭证。
定制。 自定义指令、频道记忆和 routines 是内建的。
治理与计费。 访问控制和 spend limits 在 claude.ai 管理设置里设定，用量记到组织的用量余额。

How Claude Tag works: the session model this page maps your setup onto
How agent identity works: why a channel uses the agent’s access and a DM uses yours
Claude Tag settings map: where each setting your organization owns is set
Configure GitHub access: what loads from a repository and how installs work in the sandbox
How Claude Tag works：本页把你的配置映射上去的 session 模型
How agent identity works：为何频道用 agent 的访问、私信用你的
Claude Tag settings map：组织拥有的每项设置在哪里配
Configure GitHub access：从仓库加载什么，以及安装在沙箱里如何工作