claude-code - 💡(How to fix) Fix [FEATURE] Channel notifications in status line are truncated with no way to see full content [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#45418Fetched 2026-04-09 08:05:53
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×4
  • Channel notifications are a research preview feature (docs)
  • The status line already handles other notification types (tool calls, progress) — channels reuse the same constrained space
  • The message content is fully available in Claude's context, so this is purely a user-facing visibility issue
  • Tested with custom MCP channel server using experimental_capabilities: {"claude/channel": {}}

Error Message

Channel push (notifications/claude/channel) is designed for external processes (training scripts, cron jobs, CLI tools) to send data into a running session. Users need to see what arrived — especially when messages contain metrics, error details, or actionable content that gets cut off.

Root Cause

Channel push (notifications/claude/channel) is designed for external processes (training scripts, cron jobs, CLI tools) to send data into a running session. Users need to see what arrived — especially when messages contain metrics, error details, or actionable content that gets cut off.

Code Example

← gem: I changed my password to 'incorrect' so whenever I forget i…
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

Written by Claude

Problem

When a message arrives via an MCP channel (e.g. notifications/claude/channel), the status line displays a truncated preview:

← gem: I changed my password to 'incorrect' so whenever I forget i…

The status line is a single fixed-width line, so longer messages are cut off with . There is no way for the user to:

  • Expand the notification to see the full message
  • Configure the display length
  • View a history of channel notifications

The full message does arrive in Claude's context, but the user has no visibility into what was received beyond the truncated preview.

Why this matters

Channel push (notifications/claude/channel) is designed for external processes (training scripts, cron jobs, CLI tools) to send data into a running session. Users need to see what arrived — especially when messages contain metrics, error details, or actionable content that gets cut off.

Context

  • Channel notifications are a research preview feature (docs)
  • The status line already handles other notification types (tool calls, progress) — channels reuse the same constrained space
  • The message content is fully available in Claude's context, so this is purely a user-facing visibility issue
  • Tested with custom MCP channel server using experimental_capabilities: {"claude/channel": {}}

Proposed Solution

Suggested solutions

Any of these would help:

  1. Multi-line or expandable notification — allow the status area to temporarily expand for channel messages (e.g. show full message for 3-5 seconds before collapsing)
  2. Notification log — a /notifications command to review recent channel messages as the user sees them
  3. Configurable truncation length — a setting like channelNotificationMaxLength to control how much is shown in the status line
  4. Wrap instead of truncate — use 2-3 status lines for longer messages instead of hard truncating

Alternative Solutions

I have to intercept all received messages and read it like that, inconvenient that's all.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Implement a feature to display full channel messages, such as a multi-line or expandable notification, to improve user visibility.

Guidance

  • Consider implementing a notification log feature, allowing users to review recent channel messages via a command like /notifications.
  • Introduce a configurable truncation length setting, enabling users to control how much of the message is shown in the status line.
  • Explore the option to wrap instead of truncate longer messages, utilizing 2-3 status lines to display the full content.
  • Evaluate the feasibility of a temporary expansion of the status area for channel messages, showing the full message for a short duration before collapsing.

Example

No specific code example is provided, as the issue focuses on proposing solutions rather than implementing them.

Notes

The chosen solution should prioritize user experience and visibility, considering the constraints of the status line and the importance of displaying full channel messages.

Recommendation

Apply a workaround, such as implementing a notification log or configurable truncation length, to improve user visibility into channel messages, as a full solution may require significant changes to the existing system.

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