Everything new in Claude, handed to you each morning.
A small handpicked brief from the edges of the Agent SDK, skills, hooks, and MCP — filtered, deduped, and rebuilt every morning. Hit the copy button on any card to take an idea straight to your project.
Anthropic quietly dropped Claude Mythos — cybersecurity and zero-day capabilities surface
r/ClaudeAI and r/singularity are reacting in real time to Anthropic's Mythos preview: a new frontier model that hit 70.8% on AA-Omniscience (surpassing previous SOTA on SimpleQA) and — more striking — is apparently capable of finding and exploiting zero-day vulnerabilities. Several threads are arguing the cybersecurity demonstration is a bigger deal than the benchmark, and at least one op-ed is framing Anthropic's slow public rollout as a warning sign. This is the top story across the Claude subreddits today.
Why it mattersA new model preview that leads AA-Omniscience and demonstrates real zero-day-discovery capability.
A pre-compiled wiki cuts Claude context from 47,450 → 360 tokens (99% drop)
A Reddit post (+151) builds on Andrej Karpathy's 'LLM Knowledge Bases' idea and ships `npx codesight --wiki` — a tool that pre-compiles your codebase into a Claude-ready wiki so every new session reads 360 tokens instead of 47,450. The author claims the pattern applied to a 40-file FastAPI project cuts per-session context cost by more than 99%.
Why it mattersAn open-source CLI implementing Karpathy's Knowledge Base pattern.
Matt Pocock: `claude --worktree` for everything now
Matt Pocock (@mattpocockuk) posted a new video arguing that `claude --worktree` should be the default way to run Claude Code — every task gets its own git worktree, Claude's changes stay isolated, and you can run multiple Claude sessions in parallel without them stepping on each other. He also has a companion video — '5 Claude Code skills I use every single day' — walking through his actual daily skill stack.
Why it mattersWorktrees as a per-task isolation boundary, not just a branch convenience.
Claude Code 2.1.89 adds `defer` for headless PreToolUse hooks
Headless runs used to have to accept or deny every tool call on the spot. In 2.1.89 a PreToolUse hook can now return a `defer` permission decision — the session pauses at the tool call and resumes later with `-p --resume`, at which point the hook re-evaluates with fresh context. A new `PermissionDenied` hook also fires after auto-mode classifier denials, and returning `{retry: true}` tells the model it can try again.
Why it mattersHooks can pause a headless run and hand the decision back to a human or external process.
Claude Code 2.1.94 ships Bedrock-via-Mantle and flips default effort to high
The 2.1.94 release adds Amazon Bedrock powered by Mantle behind `CLAUDE_CODE_USE_MANTLE=1`, and changes the default effort level from medium to high for API-key, Bedrock/Vertex/Foundry, Team, and Enterprise users. You can still control it with `/effort`. Also notable: a compact `Slacked #channel` header with a clickable link for Slack MCP tool calls, and plugin skills now use the skill's frontmatter `name` for invocation instead of the directory basename.
Why it mattersDefault effort is now `high`, and Bedrock has a new Mantle-backed code path.
Dangerously: run Claude Code autonomously inside your Docker Compose stack
A Show HN submission points at `sayil/dangerously`, an open-source pattern for running Claude Code as a service inside an existing Docker Compose stack. The agent runs headless against a project volume, with its permissions scoped to what Compose grants, so you can wire Claude into a longer pipeline (build, test, deploy) the same way you'd wire in any other service. The name is deliberately blunt about the risk.
Why it mattersA packaged way to run Claude Code as a Compose service, scoped by volume and network permissions.
A Claude skill that reads Apple Instruments performance traces
A Show HN from @jlreyes publishes `instruments-analyzer`, a Claude Code skill that ingests Apple Instruments traces from iOS and macOS profiling sessions and summarizes the hot paths. It's the first skill I've seen that's specifically about native Apple perf engineering — the existing AI-coding surface is overwhelmingly web/backend. Niche but a sign of where specialized skills are heading.
Why it mattersA domain-specific skill for Apple Instruments performance data.
Matt Pocock: don't run `claude /init` (and what to do instead)
Another Matt Pocock video, and this one's a contrarian take: `/init` — the command that generates CLAUDE.md — is actively harmful for most projects because it fills your repo with generic boilerplate that Claude then re-reads every session. Pocock's alternative is to hand-write a much shorter CLAUDE.md focused on the *non-obvious* project rules and let Claude explore the rest on demand.
Why it mattersA well-argued case against using /init for a CLAUDE.md bootstrap at all.