[{"data":1,"prerenderedAt":45},["ShallowReactive",2],{"$f4edOBTDBi0xd-KYFXHtnNlhIRyo9W-jzwd2mugUlRME":3},{"date":4,"generated_at":5,"picks":6,"candidates_scanned":44,"candidates_scored":16},"2026-05-06","2026-05-06T06:00:00.000000+00:00",[7,20,31],{"rank":8,"title":9,"source":10,"url":11,"category":12,"tldr":13,"score":14,"scores":15,"why":19},1,"[Release] anthropics/claude-agent-sdk-python: v0.1.74","GitHub anthropics/claude-agent-sdk-python","https://github.com/anthropics/claude-agent-sdk-python/releases/tag/v0.1.74","Release","- Hook events (PreToolUse, PostToolUse, Stop) now stream into your Python agent code — set `include_hook_events=True` on `ClaudeAgentOptions` and get `HookEventMessage` objects in your message stream, closing a long-standing gap with the TypeScript SDK\n- A new `\"defer\"` hook decision lets your code pause a tool call mid-stream, consult an external system or human, then return go/no-go — enables proper human-in-the-loop patterns without blocking the whole agent loop\n- `strict_mcp_config=True` makes your agent ignore all project/user/global MCP configs and only use servers you explicitly pass — essential for reproducible, isolated runs in CI or staging\n- New `\"xhigh\"` effort level on `ClaudeAgentOptions` targets Opus 4.7's highest reasoning tier (falls back to `high` on other models)\n- Subprocess cleanup on atexit: live `claude` subprocesses are now terminated when the parent Python process exits, preventing orphaned processes leaking in the background",74,{"direct_claude_relevance":16,"practical_utility":17,"novelty":18,"source_credibility":18},28,20,13,"The hook event streaming and deferred tool use features close a long-standing gap between the Python and TypeScript SDKs, making Python agents first-class for permission workflows and human-in-the-loop patterns. The xhigh effort level for Opus 4.7 and strict_mcp_config for isolated runs address two specific pain points — maxing out reasoning on critical tasks, and making agent runs deterministic in CI environments. This is the most feature-dense Anthropic SDK release today and covers ground not touched by yesterday's auth-focused SDK updates.",{"rank":21,"title":22,"source":23,"url":24,"category":12,"tldr":25,"score":26,"scores":27,"why":30},2,"v2.1.129","Claude Code Releases","https://github.com/anthropics/claude-code/releases/tag/v2.1.129","- The `skillOverrides` setting now actually works: set a skill to `off` to hide it from both the model and the `/` command list, `user-invocable-only` to keep it out of model context but still accessible via slash command, or `name-only` to collapse its description\n- Fixed: `/context` was secretly dumping a ~1,600-token ASCII visualization grid into your conversation every single call — a significant hidden token cost for anyone using it to manage context budget\n- Ctrl+R history search reverts to pre-2.1.124 behavior: searches all prompts across all projects by default; press Ctrl+S to narrow to the current session",69,{"direct_claude_relevance":16,"practical_utility":17,"novelty":28,"source_credibility":29},6,15,"The /context token-waste bug is a meaningful fix for anyone who runs /context regularly to monitor context budget — it was burning the budget it was meant to help track. The skillOverrides setting going live unlocks real control over skill visibility, which was documented but silently broken. Novelty is penalized since Claude Code v2.1.128 was yesterday's top pick, but the content is different enough to warrant coverage.",{"rank":32,"title":33,"source":34,"url":35,"category":36,"tldr":37,"score":38,"scores":39,"why":43},3,"I asked Claude to investigate its own token burn. The receipts go back six months.","Reddit r/ClaudeAI","https://www.reddit.com/r/ClaudeAI/comments/1t4gchn/i_asked_claude_to_investigate_its_own_token_burn/","Guide","- A community dev built `cc-cache-monitor` — a 50-line tool that reads the JSONL Claude Code already writes locally and shows your per-turn cache hit rate in your statusline in real time\n- Claimed actionable mitigations: avoid `--resume`/`--continue` (may invalidate cache on first turn), run one Claude Code session at a time during dense work, don't disable telemetry",52,{"direct_claude_relevance":40,"practical_utility":29,"novelty":41,"source_credibility":42},22,10,5,"The cc-cache-monitor GitHub tool fills a real gap: Claude Code writes per-turn cache data locally but the UI never surfaces it, so users have no way to see when caching silently breaks. The specific mitigations are actionable today without waiting for Anthropic fixes. Note that the root-cause claims (specific binary bugs, telemetry-TTL coupling) are unverified community investigation — treat the tool and mitigations as useful, the bug analysis as speculative.",40,1778043852573]