Claude Code v2.1.200 to v2.1.201 Major Updates

This is Ishikawa from the Cloud Business Division. I'd like to summarize the updates for Claude Code v2.1.200 through v2.1.201 (both released on 2026-07-03).

Update Summary

This covers 2 versions (v2.1.200 / v2.1.201, both released on 2026-07-03) with a total of 18 changes. The majority of changes are stability fixes related to background sessions and background agents, along with improvements to screen reader support. Please also note that two default behavior changes have been introduced: the default behavior of the AskUserQuestion dialog and the display name for permission modes.

Notable Updates

• Bug fix: Fixed an issue where background sessions would silently stop mid-turn after sleep/resume or when reopening a paused session (v2.1.200). This release is primarily focused on stability fixes of this kind for background-related functionality.

Target Versions and Period

Improvements

• Screen reader output has been improved. Decorative glyphs are now hidden, transcript symbols are announced as short labels, and nested tables are announced as Header: value. lines (v2.1.200).
• The installation script has been improved to explain when installation was forcibly terminated due to insufficient system memory (v2.1.200).
• Changed Claude Sonnet 5 sessions to no longer use mid-conversation system role for harness reminders (v2.1.201).

Fixes (Major)

The following is a selection of fixes primarily related to stability and usability.

• Fixed background session stopping mid-turn: Fixed an issue where sessions would silently stop mid-turn after sleep/resume or when reopening a paused session (v2.1.200).
• Fixed startup crash caused by invalid MCP configuration: Fixed a crash on startup when disabledMcpServers or enabledMcpServers in .claude.json was set to a non-array value (v2.1.200).
• Fixed re-execution of cancelled turns: Fixed an issue where background sessions would re-execute turns that had been cancelled with Esc after restarting from a paused state (v2.1.200).
• Fixed agent startup failure caused by stale daemon.lock: Fixed an issue where background agents could never start again because the OS reused the PID from a daemon.lock left behind by a crash (v2.1.200).
• Fixed background agent roster corruption: Fixed multiple issues including temporary corruption permanently disabling orphan cleanup, old binaries not retaining fields written by newer versions, and socket authentication tokens being removed on daemon restart (v2.1.200).
• Fixed sub-agent empty response on rate limit: Fixed an issue where a sub-agent that was cut off by a rate limit before generating any text output would return an empty result instead of failing gracefully (v2.1.200).
• Fixed plugin loading issues in git worktrees: Fixed an issue where project-scoped plugins were not loaded correctly from git worktrees of the same repository (v2.1.200).
• Fixed rendering flicker in tmux 3.4 and later: Fixed rendering flicker in tmux 3.4 and later by enabling synchronized terminal output (v2.1.200).
• In addition, numerous minor bugs have been fixed, including daemon takeover detection, control byte display in agent view, --plugin-dir flag ordering, screen reader focus tracking in /mcp listings, and misleading error messages for voice input (v2.1.200).

Breaking Changes / Deprecations

Both changes affect default behavior and display. Please review them in advance as they may impact your workflow.

• AskUserQuestion dialog no longer auto-continues by default (v2.1.200). A new askUserQuestionTimeout setting has been added to control this behavior, with a default value of "never" (wait until answered). Note that when auto-continuing on idle timeout, the option selected is whichever option you currently have selected (or no selection if nothing has been chosen), not the "Recommended" option. If you wish to use auto-continue, explicitly opt in by specifying "60s" / "5m" / "10m" in the "Question auto-continue timeout" (askUserQuestionTimeout) setting under /config. If you have unattended or automated workflows that depend on dialog auto-continue, you will need to review your configuration.
• The display name for "default" permission mode has been changed to "Manual" (v2.1.200). The display name has changed across the CLI, --help, VS Code, and JetBrains. Note that --permission-mode manual and "defaultMode": "manual" are interchangeable with the previous default, and existing configurations will continue to work (backward compatible).

Closing

v2.1.200 and v2.1.201 are both releases published on 2026-07-03, centered on stability improvements for background functionality. Numerous high-impact bugs have been resolved, including background session/agent stopping, re-execution, and startup failures. In addition, default behavior changes have been made to AskUserQuestion auto-continue and the permission mode display name, so if you have unattended workflows or runbooks, it is worth verifying the impact. If any of these changes are of interest, please update and check them out.

References

https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

https://code.claude.com/docs/en/changelog

https://code.claude.com/docs/en/configuration