High
Claude Code v2.1.318 — Auth expiry visibility, config safety, background subagents, AWS cost attribution, 100+ fixes
What changed
Auth expiry added to claude auth status and claude -p JSON output; non-interactive launches now fail (not silently fix) on invalid ~/.claude.json; IDE extension no longer auto-installs when started from an IDE terminal; background subagents promote shell commands to background after 3 minutes; gateway gains AWS assume_role for multi-account setups and per-developer cost attribution; $.model.fork gains an effort option; CLAUDE_RUNNER_SPAWN_REASON env var added to spawn-runner hook; self-hosted runner log format changed (see BREAKING section); 100+ bug fixes spanning cloud sessions, auth, MCP, permissions, shell, VSCode, and remote control.
TL;DR
Claude Code v2.1.318 (Nov 4) is a large production-hardening release: auth expiry warnings starting 10 days before expiry, config safety that prevents silent ~/.claude.json corruption, background subagent shell promotion, AWS multi-account cost attribution on the gateway, and over 100 bug fixes.
- Auth expiry visibility:
claude -p JSON output now includes credential_expires_at, and text output prints a stderr warning 10 days before a stored claude.ai sign-in expires. For unattended agents with scheduled sessions, add monitoring for this warning to avoid silent authentication failures mid-run.
- Config safety: Non-interactive (
claude -p, SDK) launches no longer silently replace an invalid ~/.claude.json with defaults — they now fail with an error explaining how to restore. If your CI or automated runner starts Claude Code with a corrupted config, it will now fail loudly. Good for reliability; check that your runner handles this exit code.
- IDE extension auto-install removed: Claude Code started from an IDE terminal no longer installs or updates the IDE extension. Use
/ide from an external terminal or your editor's extensions view instead. This may break any setup scripts that relied on the auto-install path.
- Background subagent shell promotion: Shell commands in background subagents automatically move to the background after 3 minutes to prevent prompt-cache expiry. For long-running agentic tasks, this reduces cold-restart costs. No config change needed — it's the default behavior now.
- Gateway
assume_role: mantle upstreams in Claude apps gateway now support assume_role for a role in another AWS account and for per-developer cost attribution on AWS. Update your gateway config if you need cross-account access or charge-back tracking.
$.model.fork effort option: You can now specify effort: "low" on $.model.fork to run a fork at lower reasoning effort regardless of the parent session's effort setting. Useful for quick side tasks (e.g., generating a short file name) that don't need full reasoning effort.
Affects you ifYou run Claude Code in unattended/headless mode; manage a Claude apps gateway; use self-hosted runners with log-based monitoring; run background subagents with long shell commands; use $.model.fork in mod scripts.EffortModerate (update runner monitoring for auth expiry warnings; update log parsers for log format change; remove reliance on IDE extension auto-install; update gateway config for assume_role if needed)
High
Pydantic AI v2.66.0 — 10 security advisories + OpenSandbox, RenderSandbox, Azure Durable Task
What changed
10 security advisories patched (see BREAKING section for the two requiring credential rotation); new OpenSandbox for self-hosted agent workspaces; new RenderSandbox for Render-hosted sandboxes; Azure Durable Task durability for pydantic_ai_harness; Pixeltable tools and memory storage in Harness; include_instructions on the MCP capability to omit server instructions from agent instructions; Anthropic 20260209 web tools now called directly on the Anthropic API when citations are requested; ModalSandbox compatibility fixed for Modal 1.6 (which removed FilesystemExecutionError); Cohere streaming now works; 20+ additional bug fixes.
TL;DR
Pydantic AI v2.66.0 (Nov 4) is primarily a security release patching 10 advisories including two HIGH-severity DoS issues and multiple credential-exposure paths; it also ships new sandbox backends (OpenSandbox, RenderSandbox) and Azure Durable Task durability.
- Upgrade now — the two HIGH advisories create DoS vectors from crafted JSON (deeply nested expansion in web_fetch_tool) and crafted secret-matching text (exponential regex in secret redaction). These affect apps where attackers can influence fetched URLs or submitted text.
- New sandbox options:
OpenSandbox and RenderSandbox give you hosted sandbox options if E2B, Modal, or Daytona don't fit your deployment. Check the GitHub PRs (#11841, #10238) for config details.
include_instructions: false on MCP capability — if your MCP server instructions are noisy or not useful to your agent, you can now suppress them without changing the server. Add include_instructions=False to the MCP capability in your agent config.
- Modal 1.6 compatibility — if you use
ModalSandbox and upgraded to Modal 1.6, this release fixes the AttributeError on FilesystemExecutionError that broke sandbox execution.
- Citations + Anthropic web tools — if you use Anthropic's
20260209 web tools and request citations, those tools are now called directly on the Anthropic API (not proxied). This may change latency and response format slightly — test before deploying.
Affects you ifYou use Pydantic AI with web_fetch_tool or the WebFetch capability against internet content; you have OTel enabled for embedding spans; you use ModalSandbox with Modal 1.6; you use AG-UI or Vercel AI adapters with untrusted message history.EffortModerate (upgrade package; rotate credentials if OTel or MCP URL creds were exposed; validate web_fetch_tool behavior with citations; test ModalSandbox on Modal 1.6)
Notable
E2B v2.63.0 — Strict pause semantics for unresponsive sandboxes
What changed
pause() gains a strict option (default false). With strict=True, pausing is refused with ServiceBusyError while the guest agent (envd) is unresponsive — the sandbox keeps running rather than taking a potentially corrupted snapshot. With strict=False (default), the snapshot is taken but marked envd_unresponsive_at_pause. Resuming a marked sandbox without on_resume="reboot" now raises GuestUnresponsiveError.
TL;DR
E2B v2.63.0 (Nov 4) adds explicit error types for the case where a sandbox's guest agent is unresponsive at pause time — previously a silent failure path that could produce corrupted or unresumable snapshots.
Developer signal
If you pause sandboxes and resume them later (a common pattern for long-running agentic tasks), you should now handle GuestUnresponsiveError on resume — it means the sandbox was paused while envd was unresponsive. Pass on_resume="reboot" to force a clean restart, or handle the error and provision a fresh sandbox. For high-reliability workloads, consider using strict=True on pause — the sandbox stays running if envd is unresponsive, so you don't create a corrupt snapshot. Update your sandbox exception handling in both the JS SDK (e2b@2.63.0) and Python SDK (@e2b/python-sdk@2.63.0).
Affects you ifYou pause and resume E2B sandboxes in long-running agent workflows; you use E2B in production where sandbox reliability matters.EffortQuick (handle GuestUnresponsiveError and ServiceBusyError in exception handlers; optionally set strict=True for high-reliability pause semantics)