Claude Code 2.1.132

💡

`CLAUDE_CODE_SESSION_ID` is now exposed to Bash subprocesses, and `CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1` lets you opt out of the fullscreen renderer. Plus a wide round of stability fixes — graceful shutdown on external SIGINT, blank fullscreen after sleep/wake, 10GB+ RSS growth from stdio MCP servers, scroll regressions in Cursor/VS Code/JetBrains terminals, and Bedrock/Vertex 400s when `ENABLE_PROMPT_CACHING_1H` is set.

#Claude Code#Update
🔗 Official announcement →

This article is a summary based on official documentation.

What changed

Claude Code 2.1.132 shipped on May 6, 2026 (UTC). It pairs three new features with a wide round of stability, rendering, and IDE-integration fixes — covering external SIGINT handling, blank-screen issues after sleep/wake, vim operators corrupting NFD-decomposed accents, grapheme-aware cursor motion in fullscreen, unbounded RSS growth from misbehaving stdio MCP servers, and Bedrock/Vertex 400 errors with ENABLE_PROMPT_CACHING_1H.

New features

  • CLAUDE_CODE_SESSION_ID exposed to Bash subprocesses

    Hooks already received a session_id, but Bash tool subprocesses had no way to identify the same session. The Bash tool now sets CLAUDE_CODE_SESSION_ID in the subprocess environment, matching the value passed to hooks.

  • CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 — opt out of the fullscreen renderer

    The fullscreen alternate-screen renderer leaves no transcript in the terminal’s scrollback once it exits. Setting this env var keeps the conversation in the terminal’s native scrollback instead.

  • “Pasting…” footer hint during Ctrl+V image paste

    Reading an image from the clipboard previously gave no feedback, so users couldn’t tell whether the paste registered. A “Pasting…” hint now shows in the footer while the clipboard read is in progress.

Improvements

  • /tui fullscreen startup banner expanded

    The banner now describes the additional benefits of the alternate-screen renderer — lower memory usage, mouse support, and auto-copy on select — at the moment users opt in.

  • Visual consistency in slash command and account dialogs

    Spacing and alignment in slash command dialogs and the /login, /upgrade, and /extra-usage flows have been tightened for consistency.

Bug fixes

Sessions, resume & shutdown

  • External SIGINT (e.g. IDE stop button, kill -INT) not running graceful shutdown — terminal modes are now restored and the --resume hint is printed instead of an abrupt exit.
  • Uncaught exception when the terminal is closed or SSH disconnects mid-session under the native build — fixed.
  • --resume failing with no low surrogate in string when a tool error truncation split an emoji — pre-corrupted sessions are now sanitized on load.
  • --permission-mode flag being ignored when resuming a plan-mode session with -p --continue/--resume, and plan mode not being re-applied after ExitPlanMode within the same session — fixed.

UI & rendering

  • Fullscreen mode showing a blank screen after laptop sleep/wake or Ctrl+Z/fg until the next keystroke or stream output — fixed.
  • Cursor landing mid-grapheme on Ctrl+E/A/K/U or arrow keys when an Indic conjunct or ZWJ emoji wraps across lines — fixed.
  • vim operators corrupting text containing decomposed (NFD) accented characters — fixed.
  • Pasting text starting with / silently swallowing the input or triggering an unknown-command reply — fixed.
  • Pasting dumping stray escape sequences into the prompt when focus events or mouse-tracking reports interleave with the bracketed paste — fixed.
  • Slash command autocomplete popup capped at ~3–5 visible commands instead of scaling with terminal height — fixed.
  • Statusline context_window token counts reflecting cumulative session totals instead of current context usage — fixed.
  • Alt+T (thinking toggle) not working on macOS terminals without “Option as Meta” enabled (iTerm2, Terminal.app defaults) — fixed.

IDE & terminal integrations

  • Mouse wheel scrolling too fast in Cursor and VS Code 1.92–1.104 — fixed (upstream xterm.js bug).
  • Scroll-wheel handling in JetBrains IDE 2025.2 terminals — fixed (spurious arrow keys, wrong-direction events, runaway acceleration).
  • /usage Ctrl+S hanging when copying the stats screenshot to the clipboard on Linux/X11 — fixed.
  • /terminal-setup showing a contradictory error in Windows Terminal — Shift+Enter is natively supported there; the message has been corrected.
  • Dead keyboard input on Windows after re-opening a background session from claude agents — fixed.

Settings & status

  • /effort picker not reflecting the CLAUDE_CODE_EFFORT_LEVEL env var override — fixed.
  • /status showing the wrong default model for some users — fixed.

MCP & connectors

  • Unbounded memory growth (10GB+ RSS) when a stdio MCP server writes non-protocol data to stdout — fixed.
  • MCP servers that connect but fail tools/list silently showing 0 tools — they now retry once and show “connected · tools fetch failed” in /mcp.
  • Unauthorized claude.ai MCP connectors showing as “failed” instead of “needs auth”, and headless -p mode retrying non-transient 4xx connection failures — fixed.
  • Bedrock and Vertex 400 errors when ENABLE_PROMPT_CACHING_1H is set — fixed.

Notes

  • CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 — set this if you want the conversation to remain in your terminal’s scrollback after Claude Code exits. You’ll lose the alternate-screen renderer’s memory, mouse, and auto-copy benefits in exchange.
  • CLAUDE_CODE_SESSION_ID for Bash workflows — shell commands and hook scripts run via the Bash tool can now read the same session_id hooks see, which simplifies per-session logging and tracing.
  • stdio MCP memory leak resolved — non-protocol data on a server’s stdout could push client RSS past 10GB. The client-side leak is fixed in this release.
  • ENABLE_PROMPT_CACHING_1H on Bedrock/Vertex — the 400 errors that blocked 1-hour caching on these providers are resolved. Existing setups should now work without changes.
  • JetBrains 2025.2 / Cursor / VS Code 1.92–1.104 users — the mouse wheel scroll regressions are resolved purely by upgrading; no settings change needed.