todai
Wednesday, 10 June
4 min read · 733 words

ACTION NEEDED

  • Update Claude Code to v2.1.170 for Fable 5 access: npm install -g @anthropic-ai/claude-code
  • Review Anthropic's new privacy policy (effective July 8) — a "good faith belief" clause allows sharing conversation data with law enforcement without a court order. Details: https://old.reddit.com/r/ClaudeAI/comments/1u0kq84/

TODAY'S ITEMS

1. Claude Fable 5: Anthropic's Most Capable Model Goes Public

Anthropic released Claude Fable 5, a Mythos-class model made safe for general use. State-of-the-art on nearly all benchmarks, with Stripe reporting it compressed months of engineering into days in a 50M-line codebase, priced at $10/$50 per million tokens.

2. Anthropic's New Privacy Policy Lets Them Share Data Without a Court Order

A clause in Anthropic's updated privacy policy (effective July 8) replaces the previous legal-process requirement with a "good faith belief" standard for sharing conversation data with law enforcement. The term appears once with no defined threshold or independent oversight.

  • Source: r/ClaudeAI (1,030 upvotes, 196 comments)
  • Why it matters: Review what you share in Claude conversations before July 8, because disclosure decisions will happen internally without court oversight.
  • Emerging

3. Microsoft's Open Source Tools Hacked to Steal AI Developer Credentials

Hackers compromised 70+ Microsoft GitHub repos including Azure tools used by Claude Code, Gemini CLI, and VS Code developers. The injected malware steals credentials when opened in AI coding apps, and this is Microsoft's second breach in weeks.

YOUR STACK — UPDATES

REDDIT SIGNAL

NEW TOOL / PRODUCT SPOTLIGHT

  • addyosmani/agent-skills — Production-grade engineering skills for AI coding agents from Addy Osmani. Seven slash commands (/spec, /plan, /build, /test, /review, /code-simplify, /ship) that encode senior engineer workflows into any Claude Code project. 49,687★ | /plugin marketplace add addyosmani/agent-skills | https://github.com/addyosmani/agent-skills

PROMPT OF THE DAY

Before I merge your changes, put on a code reviewer hat — pretend you've never seen this codebase:

1. Walk through every file change and flag anything where the intent isn't obvious from the code alone
2. List every library, abstraction, or pattern you introduced that wasn't already here — justify each one
3. Identify "just in case" code: error handling, type checks, or fallbacks guarding against scenarios this project will never hit
4. Write a one-paragraph summary a non-technical PM could read to understand what changed and why

AI code review for Claude Code — catch complexity creep before it becomes technical debt.

Source: Inspired by "Cleaning up after AI rockstar developers" (HN 384 pts, 278 comments) | https://www.codingwithjesse.com/blog/rockstar-developers/

LANDSCAPE NOTES