Wednesday, 22 April
5 min read · 875 words

1. Amazon Commits $25B to Anthropic — Locks In $100B AWS Deal Over 10 Years

  • Amazon will invest $5B immediately, with up to $20B more tied to commercial milestones — total potential commitment ~$33B. Anthropic in return commits $100B in AWS spending over 10 years; Claude remains the preferred model for AWS customers across 27 Bedrock regions.
  • Source: aboutamazon.com
  • Source: Reuters
  • Why it matters: Anthropic won't be pivoting cloud providers — for enterprise teams planning multi-year AI infrastructure on AWS, this is as close to a stability guarantee as you'll get. The milestone structure means AWS/Anthropic alignment deepens as your Claude usage grows.
  • Verified

2. Claude Cowork: Live Artifacts Now Available — Dashboards That Persist and Refresh

  • Cowork can now build live artifacts: dashboards and trackers connected to your apps and files that refresh with current data every time you open them. All artifacts persist across sessions in a new Live Artifacts tab with full version history; available on all paid plans today.
  • Source: Anthropic (official r/ClaudeAI post)
  • Why it matters: Cowork moves from session-only collaboration to a persistent workspace — build a project tracker or metrics dashboard today and it's still live and updated tomorrow without rebuilding. Update via claude.com/download.
  • Verified

3. Claude Code Apr 20: /resume 67% Faster, Thinking Progress, Security Fix

  • Three things from the April 20 release: (1) /resume on large (40MB+) sessions is 67% faster with better handling of dead-fork entries; (2) thinking spinner now shows inline progress ("still thinking" / "almost done thinking") instead of a separate row; (3) security — sandbox auto-allow no longer bypasses the dangerous-path check for rm/rmdir targeting /, $HOME, or critical system directories.
  • Source: GitHub anthropics/claude-code releases
  • Why it matters: The security fix is the one to act on — if you've been running sessions with broad sandbox permissions on projects that touch home-directory paths, update now and review your .claude/settings.json allowlist. The 67% resume speedup is an immediate gain on any project with a large session history.
  • Verified

4. Anthropic Engineering: Infrastructure Config Swings SWE-bench by 6 Points

  • New Anthropic engineering post: resource configuration alone (hard-kill vs. soft-ceiling limits in Kubernetes) caused up to 6 percentage points of variance in Terminal-Bench 2.0 — more than the gap between top models on many leaderboards. The culprit: hard memory ceilings OOM-kill containers during normal transient spikes; the official leaderboard uses lenient sandboxing that allows temporary overallocation.
  • Source: Anthropic Engineering Blog
  • Why it matters: If you run agentic coding evals in-house, set resource limits as soft floors not hard-kill ceilings — you may be suppressing your actual model performance by 3–6 points. For production agents: unexplained task failures may be infra kills, not model errors; add resource headroom before assuming model regression.
  • Verified

  • Simon Willison's Claude Token Counter now supports side-by-side multi-model comparison (Opus 4.7 vs 4.6, Sonnet 4.6, Haiku 4.5) — useful follow-up to yesterday's tokenizer cost story if you want to benchmark your specific payloads. https://tools.simonwillison.net/claude-token-counter

Analyse this codebase for production risk. List the top 5 files
most likely to cause an incident.

For each file output:
- Path
- Risk score 1–10 and the single root cause
- The specific function, pattern, or assumption that creates
  the hazard
- One concrete change to reduce that risk by >50%

Focus on: unchecked exceptions, missing input validation,
unsafe external calls, and tight coupling that blocks fast
rollback. Skip test files and build scripts.

Run this in Claude Code on any codebase before a production push — gives you a ranked risk register in under 30 seconds. Original — not community-sourced.