[FEATURE] Allow for updated input in `PermissionRequest:ExitPlanTool:Approve` hook

Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 18 comments · opened Jan 1, 2026 · closed Aug 17, 2026
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I would like to be able to send additional feedback along with approval of a plan with PermissionRequest hook responds with behavior:allow (for tool ExitPlanMode). For instance, accepting a plan but guiding Claude with additional instructions for the plan. This is useful for users who work with spec-driven development.

See a user request here: https://github.com/backnotprop/plannotator/issues/7

Related to #15755

Proposed Solution

Within the hook tool call sequence for approving a plan, iePermissionRequest:ExitPlanTool:Approve, please add the ability to submit extra context.

"hookSpecificOutput": {
"hookEventName": "PermissionRequest",
"decision": {
"behavior": "allow",
"updatedInput": {
"plan": "{full_plan}", // or:
"appendToPlan": "{extra details}"
}
}
}
}

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

Plugin, check it out.

https://github.com/backnotprop/plannotator/issues/7

Additional Context

_No response_

View original on GitHub ↗

18 Comments

bradennapier · 9 months ago

https://github.com/bradennapier/ai-model-registry/tree/main/docs/specs

  • Incremental spec driven dev <3
  • stateful and resumable

---

It prob makes most sense to just allow sending a message property so that it works the same way as deny works today.

backnotprop · 9 months ago

This may have been completed in v2.1.7 as well. wow big update to close 2 issues.

backnotprop · 9 months ago
• Added ability to provide feedback when accepting permission prompts
backnotprop · 9 months ago

Never mind. It's in the UI, but not for hooks.

ray-amjad · 8 months ago

+1 This feature! It'd be really helpful in my workflow.

gaodes · 8 months ago

+1

Jassu225 · 8 months ago

+1

Ro444elle · 8 months ago

yes, +1. would be very useful to give feedback on plan- on localhost review

metodn · 7 months ago

+1

annikovk · 7 months ago

+1

backnotprop · 7 months ago

+1

backnotprop · 6 months ago

+1

balaji-dutt · 4 months ago

Only adding a +1 to this issue because @backnotprop asked me to 😉

Jassu225 · 3 months ago

+1

ckelsoe · 3 months ago

+1

bcherny collaborator · 1 month ago

You can do this today. The PermissionRequest hook's decision object accepts updatedInput alongside "behavior": "allow", and for ExitPlanMode the hook input already includes the full plan text and planFilePath. Return the plan with your extra guidance appended:

{"hookSpecificOutput":{"hookEventName":"PermissionRequest","decision":{"behavior":"allow","updatedInput":{"plan":"<original plan>\n\n## Extra guidance\n..."}}}}

The edited plan becomes the approved plan Claude implements (and is written back to the plan file). If you'd rather not rewrite the plan, a PreToolUse hook can return additionalContext to give Claude instructions alongside the approval. Docs: https://code.claude.com/docs/en/hooks#permissionrequest-decision-control

🤖 Generated with Claude Code

backnotprop · 1 month ago

ah preesh

github-actions[bot] · 8 days ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.