Problem
The cockpit's live workers panel reads .claude/state/worker-tools.jsonl, written by a PostToolUse hook (Bash|Edit|Write → log-worker-tool.sh, issues #71/#84). That hook exists ONLY in reCode's repo-local .claude/settings.json. The plugin's hooks/hooks.json ships just three hooks (guard-git-add, lint gate, stop test gate) — a plugin's bundled settings.json is inert for consumers. Result observed 2026-07-16: reDeploy's cockpit launches but the workers panel is permanently empty.
Do
- Add the tool-mirror PostToolUse entry to
hooks/hooks.json using ${CLAUDE_PLUGIN_ROOT}/scripts/log-worker-tool.sh (script already resolves the consumer root via resolve-roots.sh).
- While in there, verify in ONE real consumer that the agents'
log-event.sh breadcrumbs actually land in the consumer's events.jsonl (reDeploy had no events file at all as of 2026-07-16 despite plugin agents carrying the instruction).
🤖 Generated with Claude Code
Problem
The cockpit's live workers panel reads
.claude/state/worker-tools.jsonl, written by a PostToolUse hook (Bash|Edit|Write→log-worker-tool.sh, issues #71/#84). That hook exists ONLY in reCode's repo-local.claude/settings.json. The plugin'shooks/hooks.jsonships just three hooks (guard-git-add, lint gate, stop test gate) — a plugin's bundledsettings.jsonis inert for consumers. Result observed 2026-07-16: reDeploy's cockpit launches but the workers panel is permanently empty.Do
hooks/hooks.jsonusing${CLAUDE_PLUGIN_ROOT}/scripts/log-worker-tool.sh(script already resolves the consumer root via resolve-roots.sh).log-event.shbreadcrumbs actually land in the consumer'sevents.jsonl(reDeploy had no events file at all as of 2026-07-16 despite plugin agents carrying the instruction).🤖 Generated with Claude Code