Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Channel permission protocol: add 'always_allow' behavior option [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52255•Fetched 2026-04-24 06:12:02
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
fpalssonfpalsson
Participants
fpalssonfpalsson
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

Currently the notifications/claude/channel/permission protocol only supports behavior: 'allow' | 'deny'. There's no way for a channel plugin (e.g. Telegram) to signal that a permission should be permanently allowed.

Proposed Solution

Add behavior: 'always_allow' so Claude Code can handle the persistence natively, the same way the terminal "Always Allow" option does.

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

Channel heavy work can be VERY repetitive when not beeing able to always allow some permissions.

Additional Context

No response

extent analysis

TL;DR

Add a new behavior option 'always_allow' to the notifications/claude/channel/permission protocol to enable permanent permission allowance.

Guidance

  • Review the current implementation of the notifications/claude/channel/permission protocol to understand how the 'allow' and 'deny' behaviors are handled.
  • Consider the potential impact of introducing a new 'always_allow' behavior on existing channel plugins, such as Telegram.
  • Evaluate how the persistence of permissions will be handled natively by Claude Code, similar to the terminal "Always Allow" option.
  • Discuss the proposed solution with the development team to ensure it aligns with the project's requirements and architecture.

Example

No code snippet is provided as the issue lacks specific technical details.

Notes

The proposed solution assumes that adding a new behavior option will not introduce significant complexity or compatibility issues with existing channel plugins.

Recommendation

Apply workaround: Introduce the 'always_allow' behavior option to the notifications/claude/channel/permission protocol, as it addresses the specific use case of repetitive permission requests in channel-heavy work.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#training loop#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING