[{"data":1,"prerenderedAt":46},["ShallowReactive",2],{"$fHz8alRy2mt-QvPlJ64yv7PkB58wF5l0_PPNkVuztClk":3},{"date":4,"generated_at":5,"picks":6,"candidates_scanned":45,"candidates_scored":30},"2026-04-29","2026-04-29T06:00:00.000000+00:00",[7,21,33],{"rank":8,"title":9,"source":10,"url":11,"category":12,"tldr":13,"score":14,"scores":15,"why":20},1,"v2.1.122","Claude Code Releases","https://github.com/anthropics/claude-code/releases/tag/v2.1.122","Release","- New `ANTHROPIC_BEDROCK_SERVICE_TIER` env var lets you pick `default`, `flex`, or `priority` service tier on AWS Bedrock — sent as the `X-Amzn-Bedrock-Service-Tier` header, useful for teams managing cost vs. latency tradeoffs on Bedrock\n- Paste any PR URL directly into the `/resume` search box and Claude Code will find the session that created it — works across GitHub, GitHub Enterprise, GitLab, and Bitbucket\n- `/mcp` now shows claude.ai connectors that were silently hidden by a manually-added server with the same URL, with a hint to remove the duplicate (finally explains that mystery disappearing connector)\n- OpenTelemetry gets two improvements: numeric attributes on `api_request`/`api_error` events now emit as actual numbers instead of strings, and a new `claude_code.at_mention` event tracks `@`-mention resolution\n- A malformed `hooks` entry in `settings.json` no longer invalidates the whole file — bad entries are now skipped gracefully instead of breaking all hooks\n- Image resize bug fixed: newer models were being sent 2576px images instead of the correct 2000px maximum, which could affect vision quality and token cost",84,{"direct_claude_relevance":16,"practical_utility":17,"novelty":18,"source_credibility":19},33,25,12,14,"v2.1.122 is one of the larger Claude Code releases this week — the Bedrock service tier env var alone unblocks teams that need to route specific workloads to flex capacity, and the `/resume` PR URL lookup addresses a long-standing navigation friction point for agentic CI workflows. The `settings.json` hooks fix is immediately valuable for anyone who has ever had a typo silently kill their entire hooks configuration. Official GitHub release from the Anthropic team makes this the authoritative source.",{"rank":22,"title":23,"source":24,"url":25,"category":12,"tldr":26,"score":27,"scores":28,"why":32},2,"[Release] anthropics/claude-agent-sdk-python: v0.1.71","GitHub anthropics/claude-agent-sdk-python","https://github.com/anthropics/claude-agent-sdk-python/releases/tag/v0.1.71","- New fields in `SandboxNetworkConfig`: `allowedDomains`, `deniedDomains`, `allowManagedDomainsOnly`, and `allowMachLookup` — brings Python SDK to full parity with the TypeScript schema\n- If your agents need tight network sandboxing (allow only specific domains, block everything else), this is now expressible with proper type hints in Python\n- Install: `pip install claude-agent-sdk==0.1.71`",73,{"direct_claude_relevance":29,"practical_utility":30,"novelty":18,"source_credibility":31},28,20,13,"Domain allowlists for sandboxed Claude agents are a production-readiness feature, not a developer convenience — teams running agents that touch internal infrastructure need to be able to specify exactly which domains are permitted. The Python SDK lagging behind TypeScript on this config surface has been a real gap for Python-first teams, and v0.1.71 closes it with full type coverage. Official Anthropic GitHub release.",{"rank":34,"title":35,"source":36,"url":37,"category":38,"tldr":39,"score":40,"scores":41,"why":44},3,"Compared 11 popular Claude Code workflow systems in one table — here's the canonical pipeline of each","Reddit r/ClaudeAI","https://www.reddit.com/r/ClaudeAI/comments/1sybpya/compared_11_popular_claude_code_workflow_systems/","Guide","- Side-by-side comparison of 11 Claude Code workflow systems (OpenSpec, BMAD, and 9 others) mapped to their canonical step-by-step pipelines\n- Yellow tags = sub-loops (tasks that repeat until verified), blue = top-level steps — pipeline *length* turns out to be a personality trait: OpenSpec ships in 3 steps, BMAD runs 12\n- Full table and sources on GitHub: `shanraisshan/claude-code-best-practice`",63,{"direct_claude_relevance":42,"practical_utility":42,"novelty":31,"source_credibility":43},22,6,"The Claude Code workflow ecosystem has exploded in 2026 and there's been no single reference comparing the major systems at the pipeline level. This table fills that gap — showing exactly which steps each system uses, which ones run as sub-loops, and how the overall complexity of each approach compares. For any team trying to pick or adapt a workflow system, seeing the full pipeline structure side-by-side is more useful than reading each system's individual docs. The GitHub link gives full detail beyond the Reddit image.",38,1777439055036]