[{"data":1,"prerenderedAt":47},["ShallowReactive",2],{"$fMfofUdMWHcCoVCyLhln9JCel1fRL9PDbuyXh-sDQl-4":3},{"date":4,"generated_at":5,"picks":6,"candidates_scanned":45,"candidates_scored":46},"2026-04-02","2026-04-02T05:30:00.000000+00:00",[7,21,34],{"rank":8,"title":9,"source":10,"url":11,"category":12,"tldr":13,"score":14,"scores":15,"why":20},1,"v2.1.90","Claude Code Releases (GitHub)","https://github.com/anthropics/claude-code/releases/tag/v2.1.90","Release","- Claude Code v2.1.90 ships `/powerup` — an interactive, animated tutorial system that teaches you Claude Code features in-context; great onboarding shortcut if you've been skipping the docs\n- The long-running `--resume` cache bug is fixed: since v2.1.69, resuming a session with MCP servers, deferred tools, or custom agents triggered a full prompt-cache miss on the first request, quietly burning up to 11.5× more tokens than expected every single time\n- Auto mode now correctly honors explicit user boundaries ('don't push', 'wait for X before Y') — before this fix those instructions were silently ignored even when the action was otherwise allowed\n- Three quadratic-time performance regressions fixed in one release: SSE transport large-frame handling, SDK session transcript writes, and per-turn MCP tool schema lookups are all now linear\n- PowerShell security hardened: four distinct bypass techniques (background job `&`, `-ErrorAction Break` debugger hang, archive-extraction TOCTOU, parse-fail deny-rule degradation) were all patched simultaneously",90,{"direct_claude_relevance":16,"practical_utility":17,"novelty":18,"source_credibility":19},33,26,16,15,"This release quietly fixes one of the most costly regressions in recent Claude Code history — the --resume cache miss bug that has been burning extra tokens for every MCP-heavy user since v2.1.69. On top of that, three separate quadratic-time performance bugs land in the same release, meaning sessions with long conversations, many MCP tools, or heavy SSE use will feel noticeably faster. The new /powerup command is the most visible addition: animated feature demos inside the terminal are a genuinely novel way to close the gap between what Claude Code can do and what most users actually know about.",{"rank":22,"title":23,"source":24,"url":25,"category":12,"tldr":26,"score":27,"scores":28,"why":33},2,"anthropic-sdk-python v0.88.0 / anthropic-sdk-typescript v0.82.0","GitHub anthropics/anthropic-sdk-python & anthropic-sdk-typescript","https://github.com/anthropics/anthropic-sdk-python/releases/tag/v0.88.0","- Both the Python and TypeScript SDKs now return `structured stop_details` on message responses — instead of inferring why a generation stopped, you get a typed object telling you exactly whether it was `tool_use`, `end_turn`, `max_tokens`, or another reason\n- Bedrock now supports API key authentication in both SDKs, removing the AWS credential ceremony for teams that want simpler Bedrock access\n- A new `aws-sdk` package lands in the TypeScript SDK (v0.2.0) for first-class AWS-native integration",70,{"direct_claude_relevance":29,"practical_utility":30,"novelty":31,"source_credibility":32},25,20,12,13,"Structured stop_details fills a long-standing gap for developers building conditional logic on top of the API — stop reason was previously a plain string that required pattern-matching, and a typed object makes branching on tool_use vs. end_turn vs. max_tokens both cleaner and more reliable. The Bedrock API key auth addition matters for teams on AWS who've been working around the full IAM credential requirement; it lowers the bar for Bedrock adoption substantially. Both SDKs shipping these in lockstep suggests this is a deliberate API surface expansion rather than a one-off.",{"rank":35,"title":36,"source":37,"url":38,"category":39,"tldr":40,"score":41,"scores":42,"why":44},3,"I investigated Claude Code's --resume cache bug. Here's what was actually happening","Reddit r/ClaudeAI","https://www.reddit.com/r/ClaudeAI/comments/1sa5ch4/i_investigated_claude_codes_resume_cache_bug/","Guide","- A developer traced the v2.1.69–v2.1.90 `--resume` regression to its root cause: session state was silently dropping `deferred_tools_delta` and `mcp_instructions_delta` records on save, so resume reconstructed a different cache key and triggered a full miss every time\n- Real cost numbers: ~11.5× higher token spend on the first resumed request; one heavy MCP user estimated 12.6M extra tokens burned and ~$43.56 in wasted API value over 27 days — with a broader community midpoint around $285K",58,{"direct_claude_relevance":29,"practical_utility":19,"novelty":31,"source_credibility":43},6,"This post does the mechanistic work the official changelog skipped — it explains exactly why the resume cache miss happened, not just that it was fixed. If you were on an MCP-heavy setup between v2.1.69 and v2.1.90 and your usage costs felt inexplicably high, this is the explanation. The community surfacing and diagnosing the regression before the fix shipped is also a useful signal: the --resume path and MCP session state serialization deserve more scrutiny in future releases.",48,28,1776402243150]