Auto mode is now the default in Claude Code
Auto mode is now the default in Claude Code
Claude Code 的自动模式现已成为默认设置
Auto mode is now the default in Claude Code for Pro, Max, and Team plans. Claude Code will soon run auto mode by default for Pro, Max, and Team plans, enabling longer-running autonomous work, and catching more dangerous commands than manual review in our testing. 对于 Pro、Max 和 Team 计划，Claude Code 的自动模式现已成为默认设置。Claude Code 即将为这些计划默认开启自动模式，从而支持更长时间的自主工作，且在我们的测试中，它比人工审核能拦截更多危险指令。
We’re making auto mode the default in Claude Code. Starting on August 14, new sessions on Pro, Max, and Team plans will run in auto mode. If you’ve already set a different default yourself, you may get a one-time prompt asking whether you want to switch to auto mode. If you have a pinned default, nothing changes for you. The auto mode classifier uses a small number of extra tokens per tool call, and we’re no longer charging Claude Code users on Pro, Max, and Team plans for that classifier overhead, effective today. 我们正在将自动模式设为 Claude Code 的默认选项。从 8 月 14 日起，Pro、Max 和 Team 计划的新会话将默认以自动模式运行。如果您之前已自行设置了其他默认模式，系统可能会弹出一次性提示，询问您是否要切换到自动模式。如果您已固定了默认设置，则不会有任何变化。自动模式分类器在每次工具调用时会消耗少量额外 Token，即日起，我们不再向 Pro、Max 和 Team 计划的 Claude Code 用户收取该分类器的额外费用。
Auto mode remains opt-in for now on Claude Enterprise, the Claude API, Claude Platform on AWS, Amazon Bedrock, Google Cloud’s Agent Platform, and Microsoft Foundry, giving admins time to review the change. In the coming month, working with our cloud partners, we plan to make it the default across all of these and no longer charge for classifier overhead. In the meantime, Enterprise admins can make Claude Code’s auto mode the default through managed settings. 目前，Claude Enterprise、Claude API、AWS 上的 Claude Platform、Amazon Bedrock、Google Cloud Agent Platform 以及 Microsoft Foundry 仍需手动开启自动模式，以便管理员有时间评估这一变更。在接下来的一个月里，我们将与云合作伙伴协作，计划在所有这些平台上将其设为默认，并取消分类器开销费用。在此期间，企业管理员可以通过托管设置将 Claude Code 的自动模式设为默认。
Auto mode is designed to balance users’ desire not to be interrupted with a system that helps avoid harmful actions: instead of prompts, it routes each tool call through a classifier targeted at blocking actions that are irreversible, destructive, or aimed outside your environment. When the classifier blocks something, Claude usually finds a safer way to proceed on its own or asks you directly for the go-ahead; if it can’t make progress—three blocks in a row, or twenty across a session—Claude Code falls back to manual approvals. 自动模式旨在平衡用户“不希望被打断”的需求与“避免有害操作”的系统要求：它不再频繁弹出提示，而是将每次工具调用通过一个分类器进行过滤，旨在拦截不可逆、具有破坏性或针对环境外部的操作。当分类器拦截某项操作时，Claude 通常会自行寻找更安全的路径，或直接询问您是否继续；如果无法推进（连续拦截三次，或单次会话累计拦截二十次），Claude Code 将回退到人工审批模式。
We spent the last several months testing whether auto mode is as safe or safer than an average user clicking through prompts. We ran internal red-teaming, third-party red-teaming and prompt-injection evaluations, a controlled study with 1,053 paid testers, and analysis of real production sessions. On every measure we tested, auto mode matched or outperformed manual review. 过去几个月，我们一直在测试自动模式是否比普通用户点击确认提示更安全。我们进行了内部红队测试、第三方红队测试和提示词注入评估，开展了一项包含 1,053 名付费测试人员的对照研究，并分析了真实的生产会话。在所有测试指标中，自动模式的表现均达到或超过了人工审核。
Auto mode also lets Claude work autonomously for longer stretches. This makes models built for long-running work, like Claude Opus 5, more practical to leave running for hours on large tasks. Reducing overhead for users also increases output. Among Teams & Enterprise adopters, auto mode users ship about 25% more PRs. Unblocking Claude allows tasks to run longer uninterrupted and get more work done. Teams at Adobe, Nuro, Gusto, and Garner Health already run auto mode as their production default. 自动模式还让 Claude 能够更长时间地自主工作。这使得像 Claude Opus 5 这样专为长任务设计的模型，在处理大型任务时运行数小时变得更加实用。减少用户的操作开销也提高了产出。在 Teams 和 Enterprise 用户中，使用自动模式的用户提交的 PR 数量增加了约 25%。解除对 Claude 的限制使其能够更长时间地不间断运行，从而完成更多工作。Adobe、Nuro、Gusto 和 Garner Health 的团队已将自动模式作为其生产环境的默认设置。
Comparing manual review to auto mode
人工审核与自动模式的对比
Data suggests that manual review can become habitual: users approve 97% of permission prompts in Claude Code. While most prompts are likely for safe, routine commands, an approval rate that high suggests many users are clicking through reflexively rather than reviewing each command. These prompts ask developers to make dozens or hundreds of important security decisions every day, often in the middle of projects, which places the review burden on users and increases the chance that something important slips through the cracks. 数据显示，人工审核容易流于形式：用户在 Claude Code 中批准了 97% 的权限提示。虽然大多数提示可能确实是安全、常规的指令，但如此高的批准率表明，许多用户是在下意识地点击，而非真正审核每条指令。这些提示要求开发者每天在项目进行中做出数十甚至数百次重要的安全决策，这给用户带来了沉重的审核负担，也增加了遗漏重要风险的可能性。
Data also suggests that users more frequently scrutinize and push back on other types of dialogues: for example, when Claude presents a plan for approval, users reject 39% of them. But for individual permissions requests, the rejection rate is only 3%. 数据还显示，用户在面对其他类型的对话时会更频繁地进行审查和拒绝：例如，当 Claude 提交计划供审批时，用户会拒绝其中的 39%。但对于单独的权限请求，拒绝率仅为 3%。
Improving safety with auto mode
通过自动模式提升安全性
Research conducted internally and through several third parties suggests that auto mode is safer than how a typical user engages with permission prompts today. We tested auto mode against what developers actually approve when they’re clicking through permission prompts. Across each of these measures—internal red-teaming, third-party penetration testing, and analysis of real-world sessions—auto mode matched or outperformed human approval. 内部及多家第三方机构的研究表明，自动模式比目前典型用户处理权限提示的方式更安全。我们将自动模式与开发者在点击权限提示时实际批准的内容进行了对比。在内部红队测试、第三方渗透测试和真实会话分析等各项指标中，自动模式的表现均达到或超过了人工审批。
Auto mode outperforms manual permissions on safety
自动模式在安全性上优于人工权限审批
In a controlled experiment with 1,053 paid professional testers, human review caught just 13.6% of dangerous commands, while auto mode caught 89%. 在一项包含 1,053 名付费专业测试人员的对照实验中，人工审核仅拦截了 13.6% 的危险指令，而自动模式拦截了 89%。