Channels 'not currently available' on Teams plan despite admin enablement
Status Closed — not planned
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 20 comments · opened Mar 21, 2026 · closed Jun 1, 2026
Same issue as #36503 — channels admin-enabled but "not currently available"
Environment:
- Claude Code v2.1.81, macOS (darwin)
- Teams plan, org: Brandlight
- Auth: Claude Team Account (OAuth, not API key/Console)
- Terminal: Warp
What I did:
- Enabled Channels in admin UI at claude.ai → Admin Settings → Claude Code
- Installed telegram plugin:
/plugin install telegram@claude-plugins-official - Ran:
claude --channels plugin:telegram@claude-plugins-official
What happened:
--channels ignored (plugin:telegram@claude-plugins-official)
Channels are not currently available
Diagnostic findings:
- No
managed-settings*.jsonfiles exist in~/.claude/— the server never delivers them - Local
settings.jsonhas nochannelsEnabledkey (and setting it locally has no effect per docs) - Tested with and without a local API proxy (
ANTHROPIC_BASE_URL) — same result claude auth status --textconfirms Claude Team Account login
Question: Is Channels currently gated to Enterprise plans only, or should it work on Teams? The admin UI exposes the toggle but the client never receives the managed setting.
Showing cached comments. Read the full discussion on GitHub ↗
19 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
+1 , teams account , admin has enabled channels, same issue.
+1 — Same on individual Max 20x. Filed #37184.
Session: Morpheus (ae19) | Task: 6gChXr7Cp3fPP5RG
same here, ubuntu (22.04 and 24.04), teams plan, channels are enabled by admin
+1 on Team plan
+1 on Team plan
+1 on Ream plan
+1 on Team plan
+1 on enterprise plan and same issue
+1 on Team plan
+1 on Team plan
Same issue here.
same here
discord plugin configured as described in docs
+1 , teams account , admin has enabled channels, same issue.
for me, deleting the line
"DISABLE_TELEMETRY": "1",in the setting did the trickUpdate: Confirmed working on Team plan as of March 24, 2026.
The
tengu_harborfeature flag is now enabled for Team accounts. After runningclaude plugins marketplace updateand relaunching with--channels, everything works — bidirectional Telegram messaging, inbound notifications, reply tool.Also confirmed: you can run multiple Telegram bots simultaneously on the same Team account by overriding
TELEGRAM_BOT_TOKENas an env var per session. Each bot connects to a different working directory. The plugin'sserver.tschecks env var first before falling back to~/.claude/channels/telegram/.env.For anyone still blocked: make sure your admin has enabled channels in claude.ai → Admin Settings → Claude Code → Channels, then update the marketplace cache.
Closed my related issue #37251.
This also worked for me. Thank you
Still broken on v2.1.126 (Team plan, organization "Yating"). Tried both workarounds from this thread:
env.DISABLE_TELEMETRYfrom~/.claude/settings.jsonentirelyclaude plugins marketplace update→ success~/.claude/statsig/cache to force feature-flag re-evaluationAfter restart still see
Channels are not currently availablefor--channels plugin:discord@claude-plugins-official.---
Note: I'm using the Discord plugin, not Telegram. The "fixed" confirmation upthread (2026-03-24) only verified Telegram. So either the fix didn't cover Discord, or the underlying gate is broader than
tengu_harbor.State observations:
~/.claude/remote-settings.jsoncorrectly shows{"channelsEnabled": true}(admin enablement is reaching the client)~/.claude/statsig/is not recreated — client may not be re-fetching feature flags at allClosing for now — inactive for too long. Please open a new issue if this is still relevant.