You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reframed from the auto-filed body into a concrete triage decision.
ClawDEA status: deliberately opts out of hook events
ClawDEA does not pass --include-hook-events to the Claude Code CLI. This is an intentional decision (umbrella #11, originally "#94 — implement --include-hook-events parsing or explicitly disable", resolved as disable) and is enforced so it can't regress:
CliProcess.ktstart() carries the explicit comment "We deliberately do NOT pass --include-hook-events."
CliProcessHookEventsOmissionTest fails the build if either CliProcess or ClaudeGateway ever adds the flag.
Because ClawDEA consumes none of these events, raw hooks-schema churn (new event types, decision-control semantics, $CLAUDE_EFFORT, etc.) is not actionable today.
How ClawDEA should be adapted
Downgrade the watchlist tier (the real fix for the recurring noise). Change the hooks-schema entry in scripts/drift/watchlist.yaml from triage: issue to triage: noise. As long as ClawDEA opts out of hooks, schema drift should append to the rolling [drift-noise] rolling Claude Code drift signal #33, not file a standalone Tier-1 issue every release.
Revisit consumption only if a specific hook becomes compelling. The v2.1.159 snapshot surfaced a few items that could justify reversing the opt-out — reopen as a scoped implementation issue (and delete the omission test) if/when one is pursued:
Surface: Claude Code hooks schema — https://docs.claude.com/en/docs/claude-code/hooks
Latest detected against: Claude Code v2.1.159
Supersedes (closed): #82, #43, #39, #35 — older per-version snapshots of this same surface.
ClawDEA status: deliberately opts out of hook events
ClawDEA does not pass
--include-hook-eventsto the Claude Code CLI. This is an intentional decision (umbrella #11, originally "#94 — implement--include-hook-eventsparsing or explicitly disable", resolved as disable) and is enforced so it can't regress:CliProcess.ktstart()carries the explicit comment "We deliberately do NOT pass --include-hook-events."CliProcessHookEventsOmissionTestfails the build if eitherCliProcessorClaudeGatewayever adds the flag.Because ClawDEA consumes none of these events, raw hooks-schema churn (new event types, decision-control semantics,
$CLAUDE_EFFORT, etc.) is not actionable today.How ClawDEA should be adapted
hooks-schemaentry inscripts/drift/watchlist.yamlfromtriage: issuetotriage: noise. As long as ClawDEA opts out of hooks, schema drift should append to the rolling [drift-noise] rolling Claude Code drift signal #33, not file a standalone Tier-1 issue every release.SessionStart→reloadSkills(re-scan skills/commands after a hook installs them) — relevant toSkillScanner/ tier-3: extend SkillScanner to scan ~/.claude/agents/, ~/.claude/commands/, ~/.claude/rules/ #23.SessionStart→sessionTitleand its interplay with--name//rename— relevant to tier-2: use --name <name> for session display in /resume picker and terminal title #13.PostToolBatch,TeammateIdle,TaskCreated,TaskCompleted,WorktreeCreate/WorktreeRemove,MessageDisplay.References
CliProcess.kt,CliProcessHookEventsOmissionTest.ktFiled automatically by the drift watcher (
.github/workflows/claude-code-drift.yml); triaged manually.