Skip to content
Plymouth AI Lab

Daily Frontier Digest ·

Claude Code's auto mode takes permission from what you type, not from what Claude says

Curated by Alfredo Borrás · Plymouth AI Lab

Anthropic's docs show Claude Code's auto mode approves actions from your messages and Claude's commands, not Claude's explanations; a physicist and GPT-6 Astra propose a lattice definition of the Standard Model; Domyn shows how EUROPA's 951.9B-parameter trials ran on a shared supercomputer; and a LessWrong post argues some alignment monitors must never touch training.

The story today

Claude Code's auto mode takes permission from what you type, not from what Claude says

Over the weekend Claude Code users compared notes on X about auto mode, where a classifier instead of a person approves each action the agent wants to take. One user reported on 15 November that an action auto mode had refused went through once they told the classifier, in their own message, that they approved it. Simon Willison said he unblocked a refused run in the Claude app the same way, with one sentence granting permission. Mark Lundeberg replied that his short "yep" answers work only when the intent is already clear from what Claude was asking to do.

Anthropic's documentation answers most of the argument. In Claude Code, the classifier reads your messages and the commands Claude runs, not the output of those commands. Anthropic's March write-up on how it built auto mode adds that Claude's own prose and tool results are removed on purpose: the agent cannot talk the classifier into a bad call, and text injected into a web page or file never reaches it. The classifier does see each proposed command, which may be why a bare "yep" sometimes passes, but not Claude's explanation of it. For a one-off action you really meant, the docs say to state that intent in your next message and let Claude retry; for anything that must never happen, use deny or ask rules, because a boundary stated only in chat can be lost when the context is compacted.

Caveats: the users' findings are anecdotes. Anthropic's own numbers show the trade-off. On 10,000 real internal tool calls the full two-stage pipeline wrongly blocked 0.4%, but it let through 17% of 52 real overeager actions and 5.7% of 1,000 synthetic data-exfiltration attempts. In most of the misses Anthropic examined, the classifier saw the danger but took approval-shaped wording, such as "clean up the PR", as consent for something larger like a force-push.

Why it matters: In auto mode your own messages are the authorisation record. When you approve something, name the exact action and its target; be careful what you paste into the same turn, since anything in your message reads as you; and put irreversible actions behind deny or ask rules rather than relying on the classifier or on a sentence in chat.

Sources: Claude Code docs: Configure auto mode · Anthropic: How we built Claude Code auto mode · X: notcatra on talking to the auto-mode classifier

Highlights

  1. A physicist and GPT-6 Astra propose a lattice definition of the full Standard Model

    In the first guest post on OpenAI's science blog (15 November), Nathaniel Craig, head of UC Santa Barbara's particle theory group and a visiting scientist at OpenAI, explains an October preprint offering a candidate way to define the Standard Model on a spacetime grid without relying on perturbation theory. The hard part is the weak force, which treats left- and right-handed particles differently: simple grids add partner particles nobody asked for, and the rule for fixing the resulting phase across the full theory had been open for more than 25 years. Craig supplied the strategy of comparing states on ever finer grids; he says Astra proposed key steps and took the lead on the detailed proof, which three outside lattice theorists questioned. It is a candidate that holds at finite grid spacing under a bound on field strength, still needs expert scrutiny, and is not yet usable for practical simulations.

    researchai-for-scienceSource: OpenAI: A step toward defining the Standard Model on a lattice

  2. Domyn details how EUROPA's 951.9B-parameter trials run on a shared EU supercomputer

    Domyn, which leads the EUROPA consortium picked for the EU's Frontier AI Grand Challenge, published its trial setup on 12 November: a mixture-of-experts model with 951.9 billion parameters, 32.8 billion active per token (8 of 384 experts), 74 layers and 65,536-token sequences, trained on 384 GH200 chips per copy on JUPITER, where it has only user-level access alongside hundreds of other projects. Fixes such as moving the Muon optimizer's main computation to the GPU (step time 41.7 s to 2.2 s), FP8 weight transfers and bf16 gradient exchange took throughput from 90 to about 1,300 tokens per second per GPU, about 43 billion tokens a day per copy or 150 billion with four copies on 1,536 GPUs. Domyn says values may change before the main run, its early runs suggest one load-balancing rule can hurt training, and there are no weights, benchmarks, data details or release date yet. Its fixes went back into PyTorch and TorchTitan.

    open-weightsinfrastructureSource: Domyn: Training a 1T-Parameter MoE on EU public infrastructure with PyTorch and TorchTitan

  3. Keep some alignment checks out of training, the way ML keeps a test set

    A LessWrong post by draganover (15 November) argues that every alignment technique can either shape a model or measure it, but not both. Chain-of-thought monitors, deception probes, honeypots, human feedback and automated audits can all be trained against; once they are, the model has learned to avoid exactly what that check catches, so a clean result says little. The ask is that labs deliberately reserve some techniques for evaluation only, as researchers hold out a test split. It is an argument without experiments, and commenters question it: one suggests using holdouts temporarily to compare training methods instead of keeping them untouched forever.

    safetyevalsSource: LessWrong: Alignment 'train/test splits' should be sacred

Concept of the day

Reasoning-blind classifier

A reasoning-blind classifier is a safety check that judges what an agent does without reading what the agent says about it. Claude Code's auto mode works this way: it sees the user's messages and the bare commands, while the agent's explanations and anything returned by tools are removed. The benefit is that a persuasive justification, or instructions hidden in a fetched page, cannot sway the verdict. The cost is that the check depends on the user's own words to know what was intended, which is why vague approvals are its weak spot.

Source: Anthropic: How we built Claude Code auto mode

Models released

ModelMakerSizeNotes
X3Guard-150MAxiomic Labs149MPrompt screener that returns two scores at once: how likely a prompt is harmful and how likely it is a jailbreak or prompt injection. On the lab's own tables its harm F1 is 0.818 (Llama Guard 4 12B: 0.662), while on adversarial prompts it ranks fifth (0.673). Prompts only, mainly English, 1,024-token limit, needs trust_remote_code. Apache 2.0.
LongCat-Video-Avatar-1.6Meituan LongCatNot statedAudio-driven talking-head and multi-person video, with claimed fixes for exaggerated mouth movement and drift in videos over 10 minutes, plus faster inference. In Meituan's own preference study (33,051 votes) it ranks second of six, behind OmniHuman-2.0. MIT.

Local models

  1. Basalt 0.4.0 runs a 4-bit Qwen 3.8 27B on one RTX 5090

    The developer of Basalt, a hobby inference engine, says version 0.4.0 adds its first dense model, Qwen 3.8 27B in NVFP4, at up to 776 tokens a second on structured output, 262 in conversation and 194 on prose, single stream, with 12,000 tokens a second of prefill at 4K context. Its top token matches the full BF16 model 92.8% of the time (KL divergence 0.0262). Since the previous update it has also gained multi-model routing and video input. These are the author's own measurements; check on your own long tasks before trusting the quality figure.

    localinferenceSource: r/LocalLLaMA: Basalt 0.4.0 release post

  2. A voltage-glitch mod unlocks 80 GB on a CMP 170HX mining card

    A r/LocalLLaMA user reports finishing the CMP 170HX voltage-glitch mod first described about five days earlier, reaching 80 GB of VRAM and 126 SMs after nearly 15 hours of work, with GPT-6 Astra writing the script for the restricted write step. It is one person's result with no inference benchmarks or stability data yet, and hardware mods like this can permanently damage the card.

    localhardwareSource: r/LocalLLaMA: CMP 170HX voltage glitch, 80 GB

Try this

  1. NVIDIA SkillEvaluator: check whether an agent skill earns its place

    SkillEvaluator is an Apache 2.0 tool that grades agent skills (folders of instructions under the Agent Skills spec) in three tiers: static quality and safety checks, overlap with other skills, and live runs comparing agent results with and without the skill. Install with pip install skillevaluator; the first tier runs without an API key, and the bundled example scores 86.2 out of 100. It can also be wired into CI or added to Claude Code or Codex as a skill.

    harnessestry-thisSource: GitHub: NVIDIA/SkillEvaluator

  2. Google's Stitch skills let a coding agent design screens

    Google Labs publishes a set of Agent Skills plugins for Stitch, its UI design tool, which work through the Stitch MCP server with Codex, Antigravity, Gemini CLI, Claude Code, Cursor and OpenCode. Plugins are split into design, build and utilities; for Claude Code the README gives npx plugins add google-labs-code/stitch-skills --scope project --target claude-code. You need the Stitch MCP set up first.

    harnessestry-thisSource: GitHub: google-labs-code/stitch-skills

  3. inside-llm: watch two quantisations of a model disagree, token by token

    inside-llm is an MIT-licensed tool built on llama.cpp that loads one or two GGUF models and shows in your browser each token's probability, the candidates it dropped, what each sampler stage removed, and, with two models sharing a tokenizer, the divergence at every position and the exact token where their outputs split. It runs locally as a single binary for Linux or Windows on CUDA or Vulkan, with no accounts or telemetry, and there is a recorded demo to try first.

    localtry-thisSource: GitHub: manuelgscom/inside-llm

Every item is checked against its primary source before it appears here. Figures we could not confirm are left out.

Related service: AI automation services for logistics

All daily issues

Five Agent Tricks, latest: Issue #5 (16 Nov 2026) · Subscribe free

From data points to pathways.

Book a 1:1 intro call and see how a small AI system could work on the data your business already has.

Book a call