Anthropic: Claude Code v2.1.140 fixes /goal hang, hot-reload and Read offset validation

Anthropic released Claude Code v2.1.140 (commit 6b070c3) on May 12, 2026 — the second consecutive patch release following v2.1.139 published the day before. This release primarily delivers bug fixes and one significant improvement to Agent tool behavior, with no new features.

Which bugs does this version fix?

Version 2.1.140 resolves ten bugs in the Claude Code CLI. The most important is a fix for the /goal command, which was hanging silently when disableAllHooks or allowManagedHooksOnly enterprise settings were active — a clear message is now shown to the user. The second critical fix addresses a hot-reload regression in which symlinked settings.json files produced incorrectly attributed change events and spurious ConfigChange hooks.

Three fixes target enterprise scenarios: claude --bg no longer crashes with “connection dropped mid-request” when the background service enters idle-exit mode, startup on machines with enterprise endpoint security agents gets more time, and managed settings now retry once with a force-refreshed token on 401 errors.

What changed in Agent tool subagent_type matching?

The Agent tool now accepts case- and separator-insensitive values for the subagent_type parameter. The changelog example: "Code Reviewer" correctly resolves to the canonical code-reviewer agent, which was not the case before. Anthropic also updated the agent color palette and added development warnings for plugin configurations where plugin.json silently ignores default component folders such as commands/.

Minor fixes

Other fixes include a Windows event-loop stall on missing executables (e.g. gh) that triggered synchronous where.exe re-spawns, validation of Read calls with the offset parameter as a whitespace-padded or +-prefixed string, native terminal cursor stability when the terminal loses focus, and a /loop performance fix that eliminates redundant wakeup scheduling for background task polling. The extraKnownMarketplaces auto-update policy now correctly persists in known_marketplaces.json.