↓Skip to main content
Zeitgeist — a spike by Chris Gathercole
  1. Topics/
  2. Claude-Specific Expertise/

Gather — 5 April 2026

Security & Vulnerabilities #

Quota & Rate-Limit Crisis #

SDK & Platform Updates #

  • Claude Agent SDK (renamed from Claude Code SDK) (GitHub - anthropics) — SDK rename with migration guide. New features: structured outputs with JSON schema validation, betas option for 1M-context window, plugins field, MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), in-process MCP servers via Python decorators.
  • Agent SDK Overview (Claude API Docs) — Canonical reference for the renamed SDK.
  • Claude Code by Anthropic — Release Notes (Releasebot) — Aggregated changelog; notable: /powerup interactive lessons, resume/performance improvements, PowerShell permissions fixes.

Workflow Patterns #

Author Updates #

  • AI Impact on Society The source leak + quota crisis are trust-erosion events worth tracking as governance/transparency signals.
  • Vibe Coding Approaches Boris Cherny’s 5-parallel-terminals workflow + “plan mode → one-shot” pattern are canonical vibe-coding practices.
  • Open vs Closed AI Ecosystems Accidental source leak of a flagship closed-model product is a notable irony — worth watching for second-order effects on open-weights arguments.
  • Data, IP & Training Rights Source-code leak raises questions about what else Anthropic’s tooling exposes; supply-chain vuln CVEs touch on trust in closed tools.

Meta-observations #

  • Emerging theme: Security is now a first-class concern for Claude Code — both vulnerabilities (CVEs, hook abuse, config-file trust) and product positioning (Claude Code Security GA). Two months ago this was absent from the journal.
  • Emerging pattern: AGENTS.md proposed as agentic counterpart to CLAUDE.md — watch whether this becomes convention or remains one author’s term.
  • Emerging pattern: Worker-Critic adversarial pairing (critics never create, creators never self-score) — an architectural pattern distinct from evaluator-optimizer because of the strict role separation.
  • Keyword suggestion: “claude code CVE” or “claude code security vulnerability” — security-incident reporting is a new recurring category.
  • Keyword suggestion: “claude code quota” / “claude code rate limit” — operational/economic issues now get more coverage than technique posts some weeks.
  • Author to watch: Filippo Valsorda (words.filippo.io) — serious cryptographer, rare high-signal case study on Claude Code in security-critical contexts.
  • Author to watch: Gergely Orosz (newsletter.pragmaticengineer.com) — already in vibe-coding config; his Boris Cherny interview warrants adding here too.
  • Source to watch: howborisusesclaudecode.com — dedicated site from Claude Code’s creator, no other aggregator covers it.
  • Source to watch: lennysnewsletter.com — landed a substantive Boris Cherny interview; worth monitoring for more insider perspectives.
  • Gap: swyx search returned no Claude Code 2026 content — watch_authors list may need pruning (swyx has been less active on this specifically). Consider replacing with Filippo Valsorda or Gergely Orosz.
  • Noise pattern: “Claude Code Tips X” articles proliferate — Substack and Medium each surface 3-4 listicles per week. Strong filter needed: prefer named practitioners (Boris, Simon, Filippo, Gergely) over SEO-driven roundups.