Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Windows] --dangerously-load-development-channels does not enable inbound channel notifications [2 comments, 2 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#46125•Fetched 2026-04-11 06:28:25
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
1
Author
KullendorffKullendorff
Participants
github-actions[bot]github-actions[bot]KullendorffKullendorff
Timeline (top)
labeled ×4commented ×2cross-referenced ×1

--dangerously-load-development-channels reliably enables inbound channel notifications on macOS but silently fails on Windows. The MCP server connects, outbound tools work, but notifications/claude/channel is never delivered to the conversation.

Error Message

| 2 | --dangerously-load-development-channels server:telegram | No error, but inbound silent |

Root Cause

--dangerously-load-development-channels reliably enables inbound channel notifications on macOS but silently fails on Windows. The MCP server connects, outbound tools work, but notifications/claude/channel is never delivered to the conversation.

Code Example

claude --dangerously-load-development-channels server:telegram --debug
RAW_BUFFERClick to expand / collapse

Summary

--dangerously-load-development-channels reliably enables inbound channel notifications on macOS but silently fails on Windows. The MCP server connects, outbound tools work, but notifications/claude/channel is never delivered to the conversation.

Environment

  • OS: Windows 11 Home (10.0.26200)
  • Shell: Git Bash (also tested concept in PowerShell)
  • Claude Code: 2.1.97
  • Auth: claudeAiOauth, Max plan, default_claude_max_5x rate-limit tier
  • Plugin: telegram@claude-plugins-official v0.0.4
  • MCP server name: telegram (matching server:telegram in flag)

Steps to reproduce

  1. Configure Telegram MCP server in .mcp.json with name telegram
  2. Run: 
    claude --dangerously-load-development-channels server:telegram --debug
  3. Verify MCP server connects (/mcp → telegram · ✔ connected)
  4. Send a message to the bot from Telegram

Expected behavior

Inbound message is delivered to the Claude conversation via notifications/claude/channel.

Actual behavior

  • ✅ MCP server connects successfully
  • ✅ Outbound reply tool sends messages to Telegram
  • ✅ Bot shows "typing..." in Telegram (MCP server receives the inbound message)
  • ❌ notifications/claude/channel never reaches the conversation
  • ❌ Claude session shows no indication of an incoming message

The bot receiving the message and showing "typing..." confirms the MCP server processes the inbound message and sends the notification — but Claude Code drops it silently.

What I've tested

#WhatResult
1--channels plugin:telegram@claude-plugins-official--channels ignored
2--dangerously-load-development-channels server:telegramNo error, but inbound silent
3--dangerously-load-development-channels plugin:telegram@...No effect
4Plugin versions 0.0.1 → 0.0.4No difference
5Claude Code versions 2.1.81 → 2.1.97No difference
6Disabled official plugin to avoid duplicate MCP conflictSame result

Cross-platform comparison

  • macOS: --dangerously-load-development-channels bypasses tengu_harbor feature flag — confirmed working by multiple users on 2.1.92–2.1.96
  • Windows: Same flag with same auth level does not enable inbound notifications

Hypothesis

Windows stdio handling differs from macOS/Linux (line ending conversion, buffering behavior), which may affect how JSON-RPC notifications are delivered over the MCP subprocess pipe. The notification is sent by the MCP server but never processed by Claude Code on Windows.

Related issues

  • #36503 — Main channels/tengu_harbor discussion (this issue was filed at the request of community members there)
  • #36460 — tengu_harbor feature flag deep-dive
  • #36964 — MCP server dies on Windows (another Windows-specific channel issue)

extent analysis

TL;DR

  • Investigate Windows-specific differences in stdio handling to resolve the silent failure of inbound channel notifications.

Guidance

  • Verify that the issue is not related to the telegram plugin by testing with a different plugin or a minimal setup.
  • Check the JSON-RPC notification format and handling in Claude Code to ensure it is compatible with Windows stdio behavior.
  • Test the --dangerously-load-development-channels flag with a different MCP server or a custom implementation to isolate the issue.
  • Review the related issues (#36503, #36460, #36964) for potential clues or workarounds.

Example

  • No specific code example is provided due to the lack of explicit code references in the issue.

Notes

  • The issue seems to be specific to Windows, and the hypothesis points to differences in stdio handling between Windows and macOS/Linux.
  • Further investigation is needed to confirm the root cause and develop a fix.

Recommendation

  • Apply workaround: Investigate and implement a workaround to handle the differences in Windows stdio behavior, such as modifying the JSON-RPC notification format or implementing custom buffering logic.
  • Reason: The issue is likely related to Windows-specific behavior, and a workaround may be necessary to resolve the issue until a proper fix is developed.

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…

FAQ

Expected behavior

Inbound message is delivered to the Claude conversation via notifications/claude/channel.

#request error#file not found#serialization error#model compatibility#GPU setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING