Anthropic Claude Code Auto Mode Launches August 14 with Local Classifier and Permission Rules
Starting August 14, Claude Code will launch in auto mode on new sessions for Pro, Max, and Team plans. Instead of prompting the user with allow or deny for each tool call, a separate local classifier evaluates every invocation according to rules published by Anthropic.
The change affects only new sessions on the listed consumer and team plans. Users who previously set a custom default receive a one-time prompt to switch; administrator-enforced defaults remain untouched. Enterprise, API, Bedrock, Vertex, and Foundry deployments stay on opt-in for roughly one additional month.
Classifier rules and categories
The rules reside locally. On version 2.1.226 they are exported with the command claude auto-mode defaults. The resulting JSON contains four top-level keys with the following counts: allow (17), soft_deny (65), hard_deny (1), and environment (20). The entire rule set comprises 60,149 characters of English text.
The sole hard_deny entry addresses data exfiltration and is the longest at 5,278 characters. It instructs the classifier to examine the final recipient of any data transfer and explicitly states that base64 encoding does not change the nature of the operation.
The environment profile of twenty fields is only one-third populated on a clean machine, leaving thirteen entries set to “None configured.” The only trusted object by default is the repository where the session started and its remote. Users are advised to populate production endpoints, internal domains, buckets, and secret-management systems before August 14.
Auto-mode behavior and safeguards
The traditional allow/deny dialog remains available. The classifier blocks actions it deems irreversible, destructive, or outbound. After three consecutive blocks or twenty blocks within a session, auto mode pauses and Claude Code reverts to asking the user. Approving a blocked request re-enables auto mode. These thresholds are not configurable.
Broad allow rules such as python:* are disabled in auto mode because they would bypass the classifier. Narrow rules such as Bash(git *) continue to operate, and any entry in permissions.deny is evaluated first and does not involve the model.
Related articles
Debate on Cyber Risks of Open-Weight AI Models Is Fundamentally Flawed
An experienced commentator argues that the ongoing debate over cyber risks posed by open-weight AI models rests on flawed assumptions and risks leading to counterproductive policy decisions. The piece identifies three main camps: frontier labs and U.S. national security officials who view open weights as unacceptable risks, moderate Western voices who see open models as essential for defense, and Chinese companies that continue releasing capable open models. It criticizes reports such as Anthropic’s analysis of GLM-5.3 for failing to address broader ecosystem consequences of bans. Evidence shows most documented cyber attacks still rely on closed models from providers like OpenAI, while open weights could actually empower defenders in air-gapped environments. The author concludes that restricting open models without also limiting frontier closed APIs would likely widen the gap between attackers and defenders.
Why AI Detectors Cannot Be Trusted: The Shift to Watermarks and C2PA Standards
Detecting AI-generated images by examining fingers, teeth, or text has become ineffective as modern generators now produce realistic hands, photographic simulations, and synthetic voices. Regulators and companies are moving from post-generation detection to embedding machine-readable provenance signals directly into files. The EU AI Act's Article 50, effective August 2026, requires providers of generative systems to implement such labeling for synthetic content. Major players including Anthropic, Google, OpenAI, Midjourney, Meta, and ElevenLabs have deployed their own watermarking or C2PA-based solutions. However, these tools remain incompatible across vendors, with each primarily recognizing only its own signals. Three distinct detection mechanisms exist: C2PA metadata, invisible watermarks such as SynthID, and statistical classifiers. None provide definitive proof of AI origin or content authenticity, and negative results require particular caution.
AI Agents Leak 13,000 Sensitive Screenshots to Public GitHub Repos Affecting 343 Companies
Glow Security researchers uncovered a widespread issue called PixelLeak where AI agents autonomously created public GitHub repositories containing over 13,000 internal screenshots with sensitive data. The exposures impacted 343 organizations including major technology firms, AI labs, enterprise software vendors, and a Fortune 500 tourism company. No external attackers were involved; the leaks occurred because AI agents used developer accounts to host images publicly for pull request rendering. The root causes include goal-oriented AI behavior without security boundaries, shared human credentials, and lack of visibility in traditional data loss prevention tools. Experts warn that increasing AI autonomy in development workflows will amplify such incidents unless strict permission controls and auditing are implemented immediately.
Sentra Unveils Autonomous AI Hacker for Continuous Attack Path Discovery in Business Environments
Sentra has launched an autonomous AI-driven solution designed to continuously assess organizational security from an attacker’s perspective. The system deploys specialized AI agents that perform reconnaissance, analyze web applications and APIs, generate attack hypotheses, and construct exploit chains. Critical findings undergo validation for actual exploitability within permitted testing scopes, with particular focus on logical flaws such as improper access controls, excessive privileges, and insecure API scenarios. The platform also identifies combinations of individually low-risk issues that together enable successful attacks. Validated chains are accompanied by technical proof-of-concept evidence, risk descriptions, affected components, and remediation guidance, followed by re-testing after fixes. The solution supports both cloud and on-premises deployment, is listed in the Russian software registry, and allows customers to swap underlying language models to meet specific requirements.