claude-code - 💡(How to fix) Fix [Feature Request] Make ※ recap: line scannable: break single long sentence, reduce entity density, add structural hierarchy

Context

Claude Code auto-injects a session-state line prefixed ※ recap: between turns (toggleable via /config, per #48642). When kept enabled, the current format has compounding readability issues that go beyond color/contrast (already raised in #51593).

Real example (from a session today)

※ recap: Stiamo riallineando OSuite Studio (validation MVP, v4 su disco) con i due doc strategici già committati nel repo omega-suite. Prossima azione: scrivere §1.5 "Coordinate con Strategic Positioning" in v4 e proporti l'edit al positioning memo prima di pushare. (disable recaps in /config)

Why it reads poorly (compounding factors, in addition to color)

1. Glyph ※ (Japanese kome, reference mark) is unusual to Latin-script readers — forces a micro-parse at the first character. A neutral › or • would do the same job without the friction.

2. Single ~50-word sentence merging two concerns: state recap + next-action. No mid-sentence period → no place for the eye to land.

3. Entity density: 7 named bindings packed in two lines (project name, version, repo, section number, doc title, doc category, config command). Each one is a context re-binding that costs attention.

4. Aggressive code-switching (in multilingual sessions): natural-language verbs in user's language ↔ English technical labels ↔ slash commands. 5-6 language-mode switches in <50 words.

5. Two parentheses with different semantic roles using identical syntax: (validation MVP, v4 su disco) is clarification; (disable recaps in /config) is operational instruction. Reader can't instinctively know which to skim.

6. Color/contrast (already in #51593): "bright black" + cursive in dark themes reduces legibility further on top of all the above.

7. No visual hierarchy to signal "this is metadata, scan if relevant". The ※ tries, but isn't strong enough alone.

Suggested layout

Two parallel rows with neutral glyph, label column, action marginalized:

› Recap   OSuite Studio — riallineo MVP v4 ↔ doc strategici (omega-suite repo).
› Next    §1.5 in v4 + edit positioning memo, poi push.
                                              [/config to disable]

Same information, ~30 words instead of ~50, two landing points instead of zero, parens reserved for the operational instruction (and marginalized to the right).

Why this matters

The recap fires between turns, so the user reads it briefly while deciding what to type next. A line that takes 4 seconds to parse instead of 1 second adds friction at exactly the wrong moment.

Related

• #51593 — semantic color customization (complementary; color is reason #6 of 7 above)
• #48642 — opt-out toggle (closed/resolved; this issue is for users who keep recaps enabled)

Environment

• Claude Code: Opus 4.7 (1M context), session-injected recap
• Platform: darwin
• Format observed: single-line ※ recap: <state>. <next action>. (disable recaps in /config)