Changes
This is a patch release with two fixes. It removes a warning that every user saw at each session start, and it stops prompt nudges on messages that the harness makes.
Fixed
- No more startup warning (#47, #48):
hooks/hooks.jsonhad adescriptionkey in each matcher group. The hook loader accepts onlymatcherandhooksthere, so every session start printedunknown keys "description" ... ignored. The description is now at the top level of the file. Thanks @Phantomn. - Install paths that contain a space (#48):
${CLAUDE_PLUGIN_ROOT}is now in quotes in each hook command. - No nudges on harness machine events (#45): Claude Code also sends some machine messages through
UserPromptSubmit:<task-notification>,<command-name>,<command-message>,<local-command-stdout>,<local-command-stderr>,<local-command-caveat>, and<system-reminder>. These messages no longer get prompt nudges. Before, each background event received the full evaluation wrapper (about 200 tokens), and a workflow task notification also received workflow guidance. Thanks @phsb5321.
Changed
- The machine-event prefix list lives once in
nudge_builtins.is_machine_event. The engine default bypass and theimproveandworkflowhandlers all use it. - Bumped plugin version to 0.6.2.
Tests
test_hooks_json_schemaguards the hooks.json schema.claude plugin validatedoes not catch unknown matcher-group keys.- New engine and handler tests for each machine-event prefix. 115 tests pass.
Installation
claude plugin marketplace add severity1/severity1-marketplace
claude plugin install prompt-improver@severity1-marketplace