Feature request: color-code messages by type (working vs needs-attention)

Problem

When working with Claude Code in the terminal, all messages look visually the same — whether Claude is executing tools, thinking, or presenting output that requires my attention (questions, results, errors). This makes it hard to quickly scan and find what I need to read vs. what's just execution noise.

Proposed solution

Color-code (or otherwise visually distinguish) different message types in the CLI output. For example:

• Dim/muted — tool execution logs, intermediate steps, "working" output
• Normal/bright — final results, summaries, code output
• Highlighted/accent color — messages that need user attention (questions, confirmations, errors)

This could be implemented as:

1. Built-in default color scheme for message types
2. Configurable via settings (e.g., messageColors in settings.json)
3. Or exposed as metadata in the status line JSON so users can build their own indicators

Why this matters

In longer sessions with many tool calls, it's easy to lose track of where Claude's output ends and where the actionable message begins. Visual differentiation would significantly improve the CLI experience, especially for power users running complex multi-step tasks.

Alternatives considered

• Status line — currently doesn't expose message type or Claude's activity state
• Output styles — change format but not visual styling per message type
• Theme — only controls light/dark, not per-message colors