Claude Code Daily Briefing - 2026-05-31

Release Summary

VersionDateKey Changes
v2.1.1585/30Auto mode now on Bedrock, Vertex, and Foundry (Opus 4.7/4.8)
v2.1.1575/29.claude/skills auto-loading, claude plugin init scaffolding, --agent override
v2.1.1565/29Opus 4.8 thinking-block fix (prevents API errors)

Full release notes


New Features & Practical Usage

v2.1.158 — Auto mode arrives on Bedrock, Vertex, and Foundry (5/30)

A small, focused follow-up to yesterday’s v2.1.157 (.claude/skills auto-loading), v2.1.158 extends Auto mode to cloud-hosted model endpoints.

You can now use Auto mode with Opus 4.7 and Opus 4.8 on Amazon Bedrock, Google Vertex AI, and Microsoft Foundry. Until now, the unattended (auto-approve permissions) mode was limited to Anthropic’s first-party API — this opens it up to enterprises that host Claude through their own cloud accounts.

It’s a one-line, opt-in environment variable:

# Enable Auto mode on Bedrock / Vertex / Foundry
export CLAUDE_CODE_ENABLE_AUTO_MODE=1
claude

Teams that run Claude exclusively on their own cloud (Bedrock/Vertex/Foundry) for compliance or security reasons can now build overnight-batch and CI unattended workflows on that same footprint.

GitHub v2.1.158


Developer Workflow Tips

Unattended runs on cloud endpoints — pair Auto mode with guardrails

v2.1.158 unlocks unattended Auto mode for Bedrock/Vertex/Foundry users, but since permissions are auto-approved, the real win comes from bounding it.

A practical pattern:

  1. Turn on Auto mode with CLAUDE_CODE_ENABLE_AUTO_MODE=1, but restrict the toolset to the minimum with --allowedTools.
  2. Combine it with sandboxing (check status via /status) to narrow file and network access.
  3. Split one large job into smaller units so an error loop can’t silently burn through tokens during an unattended run.

Self-hosted cloud endpoints have different rate limits and billing from the first-party API, so confirm the quota in that cloud’s console before kicking off an unattended run.

GitHub v2.1.158

Preserving context — CLAUDE.md compaction rules + subagent delegation

In long sessions, the most common cause of degraded quality is important context getting dropped during compaction (automatic summarization). Two practical techniques guard against it.

1. Spell out compaction-preservation rules in CLAUDE.md. Tell Claude what to keep, and it survives the summary:

<!-- CLAUDE.md -->
When compacting, always preserve the full list of modified files
and any test commands used in this session.

2. Delegate exploration to subagents. When Claude explores a codebase it reads many files and burns main-window context. Subagents run in a separate context window and return only a summary — keeping the main session lean so it stays coherent longer.

Best practices for Claude Code


Security & Limitations

June 15 Programmatic Usage Credits take effect — 15 days out

Starting June 15, Claude Agent SDK and claude -p (headless) usage will be separated from your plan’s general usage limits. Instead, it draws from a dedicated monthly Agent SDK credit (e.g., $20 on Pro, varying by plan), billed at standard API rates, with no rollover.

Interactive Claude Code sessions are unaffected, but anyone making heavy programmatic calls — via the SDK, headless mode, or third-party agents — should review their budget before the switch. Once the credit is exhausted, additional usage is charged at standard API rates (if you’ve enabled usage credits).

The Decoder


Ecosystem & Plugins

Official Resend plugin ships — MCP server + 5 skills in one install (5/26)

Email API provider Resend released an official Claude Code plugin that bundles its MCP server and five skills into a single install, letting Claude Code send mail, manage templates, and process inbound email directly.

What’s bundled: resend (SDK/APIs), react-email (template building), email-best-practices (deliverability), agent-email-inbox (inbound processing), and resend-cli (shell/CI workflows). Relevant skills activate automatically based on the task at hand.

# Install from the official marketplace
claude plugin install resend@claude-plugins-official

After installing, add RESEND_API_KEY under env in ~/.claude/config.json. It’s another data point in the trend — following Notion, Stripe, Cloudflare, Slack, and Vercel — of first-party (official) MCP plugins growing in number.

Resend changelog


Community News


Minor Changes



Interesting Projects & Tools