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. 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.
从今天起，Claude Code 可以将工作进度捕捉为 artifact（工件），把 Claude Code 的工作转化为实时、可分享的可视化页面——包括 PR walkthroughs、system explainers、dashboards 和 release checklists——并且会随着你的 session（会话）推进而自动更新。一次 Claude Code session 的范围可以从排查 incident（事故/故障），到重构某项 service（服务），再到分析数月的数据。artifacts 会把这些工作转化为任何人都能打开并探索的网页，比如 pull request walkthrough、可筛选和排序的 dashboard，甚至是在工作完成过程中会自动补全的 release checklist。artifacts 让围绕共享工作的协作变得更容易，因此团队可以把更多时间花在构建上，而不是沟通状态更新上。基于你 session 中的上下文，Claude Code 会利用完整上下文来构建 artifact，包括你的 codebase、你的 connectors，以及对话本身。单个 incident 页面可以把你代码中的失败测试及其背后的函数、连接的监控工具中的错误激增，以及你刚刚运行的 session 中关于根因的推理整合到一起。有了 artifacts，你不需要手动连接数据源，也不需要搭建基础设施。你只要提出想要一个页面，Claude Code 就会基于现有内容把它构建出来。可原地更新的实时页面：当 Claude Code 更新 artifact 时，已打开的页面会原地刷新，队友会在发布的瞬间看到更新。每次发布都会在同一个链接上生成一个新版本，并附带版本历史，因此你随时都可以恢复；同时还有一个 gallery（画廊）让你浏览和管理你创建的所有 artifacts。根据我们的内部测试，最常见的用例之一是调试。典型流程通常是这样：一位工程师在 standup 之前启动一次 incident 调查。Claude Code 处理日志并发布一个 artifact：其中包含时间线、可疑提交以及错误率图表。她从页面标题栏把链接分享给团队。等 standup 开始时，随着调查推进，Claude 已经重新发布了两次，并纳入了最新信息。有了 artifacts，团队成员和相关 stakeholder（利益相关方）不必再让别人“带我们过一遍 agent（智能代理）发现了什么”，因为大家看到的是同一个视图，拥有相同的上下文。仅限你的组织内部：每个 artifact 默认仅对作者私有。准备好后，你可以直接从页面把它分享给队友和你的组织。artifacts 仅供你所在 org（组织）中通过身份验证的成员查看，且不能公开。管理员可以通过组织级开关和基于角色的范围控制来管理访问权限，设置保留策略，并通过 compliance API 在整个组织范围内获得可见性。开始使用：让你的 session 创建一个 artifact——或者只是要求做一些可视化内容，这里按角色提供一些思路。Legal / open source：对每个 dependency（依赖）进行 license（许可证）审计，直接从 repo 标记 copyleft（著佐权）内容。“构建一个 artifact，列出每个第三方 dependency 及其 license，并标记任何 copyleft 项。”Privacy：绘制 personal data（个人数据）在代码中被收集、存储和记录日志的位置与流向图。“追踪我们在整个 codebase 中如何接触 personal data，并生成一个用于隐私审查的 artifact。”Security：将发现结果链接到精确代码行，使修复目标毫无歧义。“把这次审查中的 auth（认证）发现构建成一个 artifact，并让每项都链接到代码。”FinOps / platform finance：从 infrastructure-as-code（基础设施即代码）中映射 cloud resources（云资源）和成本驱动因素。“从 Terraform 中映射我们的 cloud resources 到一个 artifact 中，按 service 分组，并标出主要成本驱动项。”Software engineers：构建一个审查者真正能跟下来的 PR 或 bug walkthrough，内容来自 diff 及其周围代码。“做一个 artifact 来讲解这个 PR——包括 diff、背后的推理，以及我测试了什么。”Designers & frontend engineers：针对某个界面给出多个 UX 方向，每一个都基于你的真实组件构建，因此选中的方案可以直接交付上线。“给我一个 artifact，里面包含这个 signup form 的 5 种 UX 变体，基于我们的 component library 构建。”Staff engineers & architects：绘制某个 service 实际如何组合在一起的地图，来源是真实的 import graph，而不是白板图。“根据代码，把 payments service 如何组合在一起映射成一个 artifact。”SRE & on-call：构建一个随着调查推进不断扩展、最终成为 postmortem（事后复盘）的 incident 页面。“把这次 incident 变成一个 artifact——包含时间线、可疑提交、来自我们监控系统的错误激增——并在我推进调查时持续重新发布。”Engineering managers：构建一个页面，展示团队这周实际交付了什么，内容来自已合并的 PR。“根据 PR 构建一个 artifact，展示我团队本周合并了哪些内容，并按项目分组。”Claude Code 会构建页面并给你一个链接。你可以在浏览器或桌面 app 中打开它，并从标题栏分享——更新会自动发布到同一个 URL。可用性：Artifacts 目前以 beta 形式向 Claude Team 和 Enterprise orgs 开放，可通过 Claude Code CLI 和桌面 app 使用，页面可在任意浏览器中查看。今天就开始使用 Claude Code。