{"version":"2.1.307","anchor":"claude-test-helper-messages-added","canonical_anchor":"new-hidden-claude-test-write-tool-rendering","heading":"Claude Test gains a spec author agent, a draft-writing tool and a stricter explorer","tier":"use","area":"Claude Test","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/claude-test-helper-messages-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Claude Test gains a spec author agent, a draft-writing tool and a stricter explorer\n\nThe bundled Claude Test plugin adds an author agent with a `claude_test_write` tool, limits its explorer and adds new helper messages\n\n**What**\n\nClaude Test is a plugin bundled with Claude Code for browser-based testing, started with `\/claude-test`. This release changes it in several ways:\n\n- A new agent, 'Claude Test's background spec author', writes draft test specs into proposed\/. It may only use Read, Glob, ToolSearch and `claude_test_write`.\n\n- `claude_test_write` is shown as 'Write Claude Test draft', and `mcp__plugin_claude-test_browser__claude_test_write` is on a pre-approved list, so it runs without asking. A renderer for draft results is also added.\n\n- The explorer agent's instructions now say it has only Read, Grep and Glob, must not read .env files, keys, credentials or ~\/.ssh, and must stay inside the project folder. Before, those credential rules sat in an author section, with no separate author agent.\n\n- The run skill now fills in a second sandbox value and a list of background commands, alongside the sandbox value and user settings path it used before.\n\n- New messages tell you to type \/claude-test when the browser helper is not ready, such as 'Claude Test did not run this request. Type \/claude-test to run the tests.'\n\n- A new helper checks the macOS sandbox network setting `allowLocalBinding` and reports 'allowed', 'refused' or 'refused-fixed'. It sits beside a `${CLAUDE_TEST_LISTEN}` placeholder that nothing else in the code uses yet.\n\nThe ToolSearch tool's own description is unchanged in this release.\n\n**Why**\n\nClaude Test can now draft test specs in the background, and its explorer is kept away from secrets and from files outside your project.\n\n- Area: Claude Test\n- Names: `\/claude-test`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}