[FEATURE] Channel notifications in status line are truncated with no way to see full content

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] 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_