Claude Code (Team/Enterprise): two transcript notices per session from hooks cc-plugin-sec-default skips
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
The issue points to hooks/mod/register.ts where the classic.PermissionRequest hook is registered unfiltered, and hooks/hooks.json where command hooks live. First read those files to see the guard and hook ordering, then filter the mod hook to ExitPlanMode and add a SessionStart command hook for the Inbox reminder. Done means no skipped-hook lines appear in cc-plugin-sec-default sessions and the reminder still shows.
Written by the indexing model from the issue text.
Description
Under cc-plugin-sec-default, every session on our machines prints these two lines:
plannotator: its prompt.context hook was skipped. "cc-plugin-sec-default" runs first and sent the event on past it.
plannotator: its classic.PermissionRequest hook was skipped. "cc-plugin-sec-default" runs first and sent the event on past it.
Thanks to #2043 the plan flow works, so the lines report nothing users can act on.
They still read as a fault, and people ask about them.
The second line comes from the first permission prompt for any tool, not just ExitPlanMode.
The mod's classic.PermissionRequest hook is registered unfiltered (hooks/mod/register.ts) and returns next(e) for every tool except ExitPlanMode.
Two changes would end both lines:
- Send the Inbox reminder from a
SessionStartcommand hook inhooks/hooks.json, next to the existingPermissionRequestandPreToolUsecommand hooks.
The guard skips mod hooks but not command hooks, so the reminder would also reach these sessions again.
Today the guard drops it. - Filter the mod's
classic.PermissionRequesthook toExitPlanMode, so the guard only skips it during a plan approval.
There the #2043 record answers.
Seen with Plannotator 0.28.27.
0.28.30 registers both hooks the same way.
Follow-up to #2007.
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 649
- Avg merge
- 4h 10m
- Merged PRs (30d)
- 429
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from backnotprop/plannotator
-
Annotate documentation omits per-file version history and privacy controlsMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
backnotprop/plannotator#1086 · 2 comments ·
Maintainers usually reply within 1 day
-
Plannotator review pull request handle multiple authenticated github usersPossibly taken @backnotprop claimed this today. Openenhancement triage
Difficulty 3/5 1-2 days Newbie friendliness 30/100
backnotprop/plannotator#2157 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
backnotprop/plannotator#1972 ·
Maintainers usually reply within 1 day
-
Monospace numbers render as superscriptPossibly taken @backnotprop claimed this 8 days ago. Openbug
Difficulty 3/5 Half a day Newbie friendliness 68/100
backnotprop/plannotator#1961 ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
backnotprop/plannotator#1949 ·
Maintainers usually reply within 1 day
All issues in backnotprop/plannotator
Similar issues
-
[Bug]: Device screenshot fails with 500 on iPhone Duo (Xcode 27.2): serve-sim calls simctl without --displayPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
pingdotgg/t3code#24900 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inu-appcenter/UNIDorm-web#411 ·
Maintainers usually reply within 1 day
-
🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ranxianglei/billion-context#4720 ·
Maintainers usually reply within 1 day
-
area:arcade game p3-medium ready-for-agent type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
fderuiter/deruiter.dev#2840 ·
Maintainers usually reply within 1 day