claude-code - 💡(How to fix) Fix [Bug] Official Telegram plugin requests incorrectly classified as third-party, bypassing subscription limits [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#49577Fetched 2026-04-17 08:37:11
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Error Message

[{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n at Socket.onChildStdout (node:child_process:484:14)\n at Socket.emit (node:events:509:20)\n at addChunk (node:internal/streams/readable:564:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:515:3)\n at Readable.push (node:internal/streams/readable:395:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-04-16T22:45:10.537Z"}]

Code Example

[{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n    at Socket.onChildStdout (node:child_process:484:14)\n    at Socket.emit (node:events:509:20)\n    at addChunk (node:internal/streams/readable:564:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:515:3)\n    at Readable.push (node:internal/streams/readable:395:5)\n    at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-04-16T22:45:10.537Z"}]
RAW_BUFFERClick to expand / collapse

Bug Description Server-side classifier is misflagging requests from --channels plugin:telegram@claude-plugins-official as third-party, routing them to Extra Usage instead of my Max 20x subscription. Subscription is at only 21% weekly usage. Same binary + session works without --channels. This breaks the official Anthropic Telegram plugin. Support conversation ID: 215473950123453. Please fix the classifier.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.112
  • Feedback ID: 2bace53a-55aa-44d9-81b2-2b193a3e7ccf

Errors

[{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n    at Socket.onChildStdout (node:child_process:484:14)\n    at Socket.emit (node:events:509:20)\n    at addChunk (node:internal/streams/readable:564:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:515:3)\n    at Readable.push (node:internal/streams/readable:395:5)\n    at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-04-16T22:45:10.537Z"}]

extent analysis

TL;DR

The issue may be resolved by adjusting the server-side classifier configuration to correctly identify requests from the Telegram plugin as first-party requests.

Guidance

  • Investigate the classifier configuration to determine why requests from the --channels plugin:telegram@claude-plugins-official are being misflagged as third-party.
  • Verify that the Max 20x subscription is correctly configured and that the weekly usage is indeed at 21%.
  • Check the official Anthropic Telegram plugin documentation to ensure that it is compatible with the current version (2.1.112) and platform (darwin).
  • Review the error log to determine if the RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER] is related to the misflagging issue.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The provided error log suggests a potential issue with the child process stdout buffer, but it is unclear if this is directly related to the misflagging issue. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Adjust the classifier configuration to correctly identify requests from the Telegram plugin as first-party requests, as this is the most likely cause of the issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Bug] Official Telegram plugin requests incorrectly classified as third-party, bypassing subscription limits [1 participants]