[{"data":1,"prerenderedAt":48},["ShallowReactive",2],{"$f-kobzgXeqE0BqlJ1xhw-H4rVMo97rdpYENe0GP7aDpw":3},{"date":4,"generated_at":5,"picks":6,"candidates_scanned":46,"candidates_scored":47},"2026-04-03","2026-04-03T05:30:00.000000+00:00",[7,20,32],{"rank":8,"title":9,"source":10,"url":11,"category":12,"tldr":13,"score":14,"scores":15,"why":19},1,"v2.1.91","Claude Code Releases (GitHub)","https://github.com/anthropics/claude-code/releases/tag/v2.1.91","Release","- MCP tool results can now be up to 500K characters (up from ~50K) by setting `_meta[\"anthropic/maxResultSizeChars\"]` on the tool annotation — no more silent truncation of large DB schemas or file dumps\n- Plugins can now ship executables under `bin/` and invoke them as bare commands from the Bash tool, making plugin-packaged CLIs a first-class citizen\n- Multi-line prompts in `claude-cli://open?q=` deep links now work — encoded newlines (`%0A`) are no longer rejected\n- A bug where `--resume` could silently lose conversation history when async transcript writes fail is fixed\n- Plan mode no longer loses track of the plan file after a container restart in remote sessions, which was causing spurious permission prompts and empty plan-approval modals\n- The Edit tool now uses shorter `old_string` anchors, reducing output token count on every file edit",87,{"direct_claude_relevance":16,"practical_utility":17,"novelty":18,"source_credibility":18},33,26,14,"The MCP result size increase from ~50K to 500K is the standout change: large tool results like full database schemas or long file contents were being silently truncated before, which caused subtle agent failures that were hard to diagnose. The plugin `bin/` support opens a new surface for distributing tooling alongside skills without requiring separate installs. The Edit tool anchor optimization is a quiet win that compounds over long coding sessions — every file edit now costs slightly fewer output tokens.",{"rank":21,"title":22,"source":23,"url":24,"category":12,"tldr":25,"score":26,"scores":27,"why":31},2,"Claude Code GitHub Action v1.0 — Now Generally Available","GitHub anthropics/claude-code-action","https://github.com/anthropics/claude-code-action/releases/tag/v1","- The Claude Code GitHub Action hits v1.0 GA — the action that lets you trigger Claude Code on PRs, issues, and CI events with `@claude` mentions or automation rules\n- Configuration is drastically simplified: `mode`, `direct_prompt`, `override_prompt`, and `custom_instructions` are all replaced by a single `prompt` input and a `claude_args` passthrough for CLI flags\n- Now supports AWS Bedrock and Google Vertex AI natively, so teams with cloud-provider constraints can use it without routing through the Anthropic API\n- Breaking changes from v0.x — check the migration guide before upgrading",82,{"direct_claude_relevance":28,"practical_utility":29,"novelty":30,"source_credibility":18},30,22,16,"GA status matters here: v1.0 signals API stability, meaning teams can now depend on this action in production CI/CD pipelines without worrying about breaking changes between minor versions. The unified `prompt` + `claude_args` interface removes the confusion between `direct_prompt`, `override_prompt`, and `custom_instructions` that tripped up many early adopters. The Bedrock and Vertex support is significant for enterprise teams whose security policies prevent direct Anthropic API calls.",{"rank":33,"title":34,"source":35,"url":36,"category":37,"tldr":38,"score":39,"scores":40,"why":45},3,"Follow-up on usage limits","Reddit r/ClaudeAI (ClaudeOfficial)","https://www.reddit.com/r/ClaudeAI/comments/1sat07y/followup_on_usage_limits/","Announcement","- Anthropic's official account explains what's been driving faster usage burn: peak-hour limits tightened and 1M-context sessions got larger, not a billing bug\n- Key tips: use Sonnet 4.6 instead of Opus on Pro (Opus burns ~2× as fast), turn off extended thinking when you don't need it, start fresh sessions rather than resuming idle ones, and set `CLAUDE_CODE_AUTO_COMPACT_WINDOW=200000` to cap context growth",65,{"direct_claude_relevance":41,"practical_utility":42,"novelty":43,"source_credibility":44},28,20,8,9,"This is the closest thing to an official explanation for the usage limit complaints that dominated r/ClaudeAI this week. The concrete env var tip (`CLAUDE_CODE_AUTO_COMPACT_WINDOW`) is directly actionable for Claude Code users hitting limits mid-session, and the Opus vs. Sonnet burn rate clarification (roughly 2× difference) is something many Pro users likely didn't know. The post is from the verified ClaudeOfficial Reddit account, making it a semi-official communication even if Reddit isn't the ideal channel.",50,24,1776402243140]