What probably matters to youSection of the release
Unclear It is not clear whether the check that claude-test runs only in an interactive terminal was removed or only moved elsewhere.
What
The built-in claude-test plugin was reworked. A plugin is a bundle of extra abilities Claude Code can load.
It registers a claude-test command and a skill hook, and connects a browser helper MCP server (an add-on that gives Claude tools to drive a browser).
When it fails to start, it now shows a specific fix, for example "Claude Test did not start: its browser helper is switched off for this project."
It records draft and run usage from saved.json and results.json.
If another copy of claude-test is installed, the message now says to disable or uninstall that one on the Installed tab of /plugin, keep the built-in one on, and restart Claude Code. Before, it pointed to the other copy's marketplace name and asked for a new session.
The message saying Claude Test needs an interactive Claude Code session in a terminal, and the "Claude Test cannot run in this session yet" message, are gone from where they were.
Why
If Claude Test fails to start, the error now says what to change. The findings suggest it may no longer be limited to interactive terminal sessions.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether the check that claude-test runs only in an interactive terminal was removed or only moved elsewhere.
Anthropic's release notes agreeFixed /plugin's Discover tab showing a marketplace name unquoted in its "Checking … for new plugins" line when its rows already show that…
