[eejd]

Summary

• update the Claude native hook response so every updatedInput payload includes permissionDecision: "allow"
• add a regression test for the emitted JSON shape
• update the hook permission-model docs to reflect the current Claude hook validator contract

Why

Current Claude hook validation rejects PreToolUse responses that return updatedInput without an explicit allow decision:

PreToolUse hook returned updatedInput without permissionDecision:allow

RTK's Claude hook previously omitted permissionDecision for default/ask rewrites. That makes the rewrite payload invalid even though the rewritten command itself is fine.

This change keeps deny/defer passthrough behavior unchanged, but when RTK does return a rewritten updatedInput, it emits:

{
  "hookSpecificOutput": {
    "hookEventName": "PreToolUse",
    "permissionDecision": "allow",
    "permissionDecisionReason": "RTK auto-rewrite",
    "updatedInput": { "command": "rtk git status" }
  }
}

Scope

This PR branch was created from upstream/master and contains only one commit. Diff is limited to:

• src/hooks/hook_cmd.rs
• src/hooks/README.md

Testing

On the fork branch that originally carried this change:

/opt/local/bin/cargo test hooks::hook_cmd

passed: 77 hook tests.

On a clean branch based directly on upstream/master, the same test command currently fails before running tests due to pre-existing upstream dead-code warnings unrelated to this PR:

error: constant `FILTERS_TOML` is never used
error: associated function `load` is never used

I also verified the runtime payload shape locally with:

printf '%s\n' '{"tool_name":"Bash","tool_input":{"command":"git status","description":"Check repo status"}}' | rtk hook claude

and confirmed the response includes permissionDecision: "allow" next to updatedInput.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[rtk-release-bot]

Automatic message from CI checks : It seems like this branch is targeting the wrong branch, any contribution should target develop branch.

See CONTRIBUTING.md for details.

[KuSh]

Thank you for working on this. Closing as no longer applicable: the situation this change describes does not hold anymore, so the hook no longer needs to emit an explicit allow with every updatedInput. If you still see that validator error on a recent build, please comment with the Claude Code version and this can be reopened.