Claude Code Digest — 2026-04-08 00:39:59
Version updates
Anthropic released version 2.1.94 on April 7, pushing major API integrations and shifting compute defaults. The headline feature is support for Amazon Bedrock powered by Mantle via the CLAUDE_CODE_USE_MANTLE=1 environment variable. The release defaults API-key, direct provider, Team, and Enterprise users to "high" effort level. A minor UI update introduces a compact, clickable Slack channel header.
What the docs reveal
Ending the AWS API fragmentation
Mantle introduces the most significant infrastructure shift for enterprise developers. Previously, running Anthropic models on AWS required adapting to Bedrock's proprietary Invoke API structure. The new Mantle endpoint exposes the native Anthropic API shape directly on top of AWS infrastructure.
Anthropic built this for enterprise teams trapped behind AWS perimeters. By adding CLAUDE_CODE_SKIP_MANTLE_AUTH, the team explicitly supports downstream LLM gateways like LiteLLM. You can now route Claude Code traffic through internal proxy services without tripping on AWS SigV4 authentication layers. Developers can configure hybrid setups, maintaining legacy Bedrock Invoke streams while running modern native tools via Mantle.
Context hygiene and subagent isolation
Context window bloat destroys LLM reasoning. Anthropic addressed this by aggressively walling off subagents and filtering standard output. Subagents now execute in independent context realms. They share zero file-reading history with your main session, returning a synthesized summary upon task completion.
The tool pipeline implements equal discipline. The system now ignores standard output (exit code 0). If you want data to reach Claude's context, your hook must return JSON formatted in an additionalContext field. Standard error (exit code 2) still breaches the context window, alerting Claude to immediate failures. This architectural split delegates raw execution logs to your terminal while keeping the LLM focused entirely on actionable data. You write better tools when you decouple noisy standard outputs from semantic context injections.
The economics of effort
Claude Code adjusts its baseline intelligence based on how you pay. The documentation clarifies that Pro and Max customers—who pay flat subscription rates—default to "medium" effort. Users paying explicitly for usage (via API keys, Team, Enterprise, or Foundry plains) now default to "high" effort. Anthropic shields its server costs on flat-rate plans while maximizing capability for customers who bear the compute expense.
For precision tasks, developers gain the "ultrathink" keyword. Injecting this string into any prompt forces a single-shot high-effort reasoning cycle. You avoid the friction of toggling the /effort command for isolated complex problems.
Monorepo workflow enhancements
Handling complex repositories required tedious directory switching. The /resume session picker now natively spans all git worktrees within a repository. Selecting a session bound to an alternate worktree instantly forces a directory change. Developers juggling concurrent feature branches via worktrees gain seamless session continuity. Active headless sessions trigged by claude -p or the SDK deliberately vanish from the picker to reduce clutter. You must reconnect to them explicitly via their session IDs.
Developers also gain a dedicated Ctrl+L shortcut to clear the prompt input buffer. This stops you from accidentally deleting terminal history when you only intend to rewrite your current query.
Retention vectors and plaintext hazards
Local session management trades security for convenience data. The ~/.claude/ directory retains plaintext session transcripts, file histories, and pre-modification code snapshots for 30 days. Anthropic warns that tool outputs frequently leak credentials or proprietary database fragments into these local transcripts.
If an attacker compromises your machine, they possess a searchable 30-day index of your entire codebase interactions. Enterprise administrators mandate zero-trust environments; they should enforce the --no-session-persistence flag across standard developer environments. For standard instances, aggressively lower the cleanupPeriodDays variable.
Garbage collection received a necessary strictness bump. Claude Code caches installed plugin versions in independent directories to ensure long-running sessions remain stable. The system purges orphaned plugin code after seven days. This approach avoids tearing down active tool states mid-session while preventing silent disk bloat.