/ Claude Code v2.1.139

Bash safety analysis now detects ambiguous heredoc terminators, including <<- tab-prefixed delimiters and heredoc body lines that can be mistaken for terminators with shell metacharacters. Evidence: heredoc safety checks (search for "ambiguous heredoc terminator", "Heredoc uses <<- with a tab-prefixed delimiter")

Plugin ZIP loading now handles archives with a wrapper directory instead of failing or choosing the wrong root. Evidence: inline plugin ZIP handling (search for "Inline plugin zip had wrapper directory; using")

Missing plugin errors are more actionable and now suggest claude plugin list or --plugin-dir <path>. Evidence: plugin lookup error (search for "not found. Run claude plugin list to see installed plugins")

Marketplace plugin cache misses now explain that the plugin may have been removed and tell users to disable it via /plugin. Evidence: plugin source cache-miss message (search for "the plugin may have been removed. Disable it via /plugin to clear this warning")

Settings-file watching now tracks symlink targets so atomic-save edits to the target file are detected. Evidence: symlink target watcher (search for "also watching", "so atomic-save edits to the target are detected")

Plugin directory copying now handles cyclic symlinks, non-regular symlink targets, and symlinks escaping the containment root more carefully. Evidence: symlink materialization safeguards (search for "copyDir: skipping cyclic symlink target", "copyDir: skipping symlink escaping containment root")

HTTP/SSE transport now aborts streams that exceed the body limit without an SSE event boundary, preventing unbounded memory growth when a server returns non-protocol data. Evidence: SSE body overflow guard (search for "without an SSE event boundary", "HttpBodyOverflowError")

Proxy and TLS connection setup now has explicit timeout/failure errors for gateway-style connections. Evidence: connection error strings (search for "TLS connection timed out", "proxy CONNECT failed", "proxy CONNECT timed out")

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agree/plugin installed-plugin details now show hook event names and MCP server names cleanly

See this entry in the whole of v2.1.139 →

The build it came inv2.1.139

11 May 2026 · 13 entries, this one is #12.

Either side of it

v2.1.138Older
v2.1.140Newer

Open the release →

Names in this entry

cli--plugin-dir
Load a plugin from a directory or .zip archive, or several from a folder of plugins, for this session only. Each flag takes one path. Repeat the flag for more paths: --plugin-dir A --plugin-dir B.zip. Passing a folder of plugins requires Claude Code v2.1.265 or later
slash/plugin
Manage Claude Code plugins. Run with no argument to open the plugin menu, or pass a subcommand such as list, install, enable, or disable to act directly. Claude Code can activate a plugin during the install; the install summary tells you whether it did or whether to run /reload-plugins

Anthropic's note

Upstream's own release notes for v2.1.139 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

/plugin installed-plugin details now show hook event names and MCP server names cleanly

Is this right?