Claude Code 现已支持 Artifacts
英文标题：Claude Code now supports artifacts
Claude Code 现在可将工作进度捕获为 Artifact，生成实时、可分享的可视化页面，涵盖 PR 走查、仪表盘、发布清单等场景。Artifact 会基于会话上下文（代码库、连接器、对话）自动构建，无需额外数据源配置。页面支持原地更新与版本历史，默认仅组织内成员可见，增强了协作效率与信息安全。该功能目前已以 Beta 版向 Claude Team 和 Enterprise 组织开放，为开发者团队提供了更流畅的成果分享和状态同步方式。
13.5 KB
403 B
27.9 KB
19.3 KB
13.7 KB
22.7 KB
51.7 KB
中文
从即日起，Claude Code 可以将工作进度捕获为 artifact，将 Claude Code 的工作成果转化为实时、可分享的可视化页面——包括 PR 走查、系统讲解、仪表盘和发布检查清单——这些页面会随你的会话进展自动更新。
Claude Code 会话可以涵盖从调查事故、重构服务到分析数月数据等各种场景。Artifact 将工作转化为任何人都能打开并探索的网页，例如可筛选和排序的仪表盘，或者能在工作完成过程中自动填写的发布检查清单。Artifact 让共享工作的协作更加轻松，使团队能花更多时间构建，减少状态同步的沟通成本。
[视频：Claude Code Artifacts 功能演示]
基于会话上下文构建
Claude Code 利用会话的完整上下文来构建 artifact，包括你的代码库、连接器以及对话本身。一个单独的故障页面可以将失败的测试及其背后的函数从代码中提取出来，关联来自已连接监控工具的错误尖峰，并结合你刚刚执行的会话中的根因推理。使用 artifact，你无需接入数据源或搭建基础设施。你只需请求一个页面，Claude Code 就会根据现有信息自动构建。
实时更新、原地刷新
当 Claude Code 更新 artifact 时，打开的页面会原地刷新，团队成员在发布时就能立刻看到更新。每次发布均为同一链接的新版本，并提供版本历史，方便你随时恢复。画廊视图则让你能浏览和管理所有已创建的 artifact。
根据我们的内部测试，最常见的用例之一是调试。典型场景如下：一位工程师在站会前启动事故调查。Claude Code 梳理日志并发布一个 artifact：包含时间线、可疑提交和错误率图表。她通过页面头部将链接分享给团队。到站会开始时，Claude 已根据调查进展重新发布了两次，并纳入了最新信息。借助 artifact，团队成员和利益相关者无需再“让我们一步步看 agent 发现了什么”，因为他们都在同一视图下，共享相同的上下文。
组织内私有
默认情况下，每个 artifact 仅对其创建者可见。当你准备好时，可以直接从页面上分享给团队成员和整个组织。Artifact 仅限组织中经过身份验证的成员查看，无法公开。管理员通过组织级开关和基于角色的范围来管理访问权限，设置保留策略，并通过合规 API 获得组织范围内的可见性。
快速上手
在会话中向 Claude 索要一个 artifact——或者直接请求可视化内容。以下是一些按角色分类的思路：
- 法务 / 开源：直接从仓库中审计所有依赖项的许可证，标记出 copyleft 许可证。"构建一个 artifact，列出所有第三方依赖及其许可证，并标记任何 copyleft 的内容。"
- 隐私：绘制个人数据在代码中收集、存储和记录位置的数据流图。"追踪我们代码库中涉及个人数据的地方，生成一个用于隐私审查的 artifact。"
- 安全：将发现链接到具体代码行，使修复一目了然。"根据此次审查构建一个 artifact，列出身份认证相关发现，并分别链接到对应代码。"
- FinOps / 平台财务：从基础设施即代码中映射出云资源及主要成本驱动因素。"从 Terraform 中映射我们的云资源为一个 artifact，按服务分组，并标出主要成本驱动因素。"
- 软件工程师：基于 diff 及其周围代码，生成审查者真正能够理解的 PR 或 Bug 走查。"创建一个介绍这次 PR 的 artifact——包含差异、推理以及我测试的内容。"
- 设计师与前端工程师：为一个界面提供多种 UX 方案，均基于你的真实组件构建，选中的那个即可交付。"给我一个 artifact，包含基于我们组件库构建的注册表单的 5 种 UX 变体。"
- Staff 工程师与架构师：根据真实的导入关系图，而非白板绘制，展示服务实际上如何组合在一起。"根据代码绘制支付服务如何组合在一起的 artifact。"
- SRE 与值班人员：一个随调查展开而不断完善的故障页面，最终可成为事后复盘报告。"把这个故障转化为 artifact——包含时间线、可疑提交、我们监控中的错误尖峰——并在我推进调查时重新发布。"
- 工程经理：根据已合并的 PR，生成实际交付内容概览。"根据这周团队的 PR 构建一个 artifact，展示本周合并的内容，按项目分组。"
Claude Code 会构建页面并提供一个链接。你可以在浏览器或桌面应用中打开，通过页面头部进行分享——更新会自动发布到同一 URL。
可用性
Artifacts 现以 Beta 版向 Claude Team 和 Enterprise 组织用户开放，可通过 Claude Code CLI 和桌面应用使用，页面可在任何浏览器中查看。
立即开始 使用 Claude Code。
English / 原文
Starting today, Claude Code can capture work progress as an artifact, which turn Claude Code's work into live, shareable visual pages— including PR walkthroughs, system explainers, dashboards, and release checklists—that update themselves as your session works.
A Claude Code session can range from investigating an incident to refactoring a service to analyzing months of data. Artifacts translate the work into a web page anyone can open and explore, like a pull request walkthrough, a dashboard you can filter and sort, or even a release checklist that fills itself out as work gets done. Artifacts make it easier to collaborate on shared work, so teams can spend more time building and less time communicating status updates.
VIDEO
Built on the context from your session
Claude Code builds an artifact using the full context of your session, including your codebase, your connectors, and the conversation itself. A single incident page can bring together the failing test and the function behind it from your code, the error spike from a connected monitoring tool, and the root-cause reasoning from the session you just ran. With artifacts, you don't need to wire up data sources or stand up infrastructure. You ask for a page, and Claude Code builds it from what already exists.
Live pages that update in place
When Claude Code updates an artifact, the open page refreshes in place and teammates see the updates the moment they’re published. Every publish is a new version at the same link, with version history so you can restore at any time, and a gallery lets you browse and manage all artifacts you've made.
From our internal testing, one of our most common use cases has been debugging. These typically look something like: An engineer kicks off an incident investigation before standup. Claude Code works through the logs and publishes an artifact: a timeline, the suspect commits, and an error-rate chart. She shares the link with her team from the page header. By the time standup begins, Claude has republished it twice as the investigation progressed, incorporating the latest information. With artifacts, team members and stakeholders don’t have to "walk us through what the agent found" because they're all looking at the same view, with the same context.
Private to your organization
Every artifact is private to its author by default. When you're ready, share it with your teammates and your organization directly from the page. Artifacts are viewable only by authenticated members of your org and cannot be made public. Admins manage access with an org-level toggle and role-based scoping, set retention policies, and get org-wide visibility through the compliance API.
Getting started
Ask your session for an artifact — or just ask for something visual, h ere are some ideas by role:
- Legal / open source : A license audit of every dependency, flagging copyleft, straight from the repo. "Build an artifact listing every third-party dependency and its license, flagging anything copyleft."
- Privacy : A data-flow map of where personal data is collected, stored, and logged across the code. "Trace where we touch personal data across the codebase into an artifact for the privacy review."
- Security : Findings that link to the exact line, so the fix is unambiguous. "Build an artifact of the auth findings from this review, each linked to the code."
- FinOps / platform finance : Cloud resources and cost drivers mapped from your infrastructure-as-code. "Map our cloud resources from the Terraform into an artifact, grouped by service, with the big cost drivers."
- Software engineers : A PR or bug walkthrough reviewers can actually follow, pulled from the diff and the code around it. "Make an artifact walking through this PR — the diff, the reasoning, and what I tested."
- Designers & frontend engineers: Several UX directions for a screen, each built from your real components so the one you pick is shippable. "Give me an artifact with 5 UX variations of this signup form, built from our component library."
- Staff engineers & architects: A map of how a service actually fits together, drawn from the real import graph instead of a whiteboard. "Map how the payments service fits together into an artifact, from the code."
- SRE & on-call: An incident page that grows as you investigate and becomes the postmortem. "Turn this incident into an artifact — timeline, suspect commits, error spike from our monitoring — and republish as I work through it."
- Engineering managers : A page of what actually shipped, built from the merged PRs. "Build an artifact of what merged on my team this week from the PRs, grouped by project."
Claude Code builds the page and gives you a link. Open it in your browser or the desktop app, share it from the header—updates publish to the same URL automatically.
Availability
Artifacts is available in beta to Claude Team and Enterprise orgs, from the Claude Code CLI and desktop app, with pages viewable in any browser.
Get started today** with Claude Code.**