Skip to content

[claude-code v2.1.159] hooks-schema: drift detected #112

Description

@github-actions

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.

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.kt start() 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

  1. 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.
  2. 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:

References

Filed automatically by the drift watcher (.github/workflows/claude-code-drift.yml); triaged manually.

Metadata

Metadata

Assignees

No one assigned

    Labels

    claude-code-driftDrift between Claude Code and ClawDEA's integration with it

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions