[Bug] /insights command: Model omits file:// link from "output exactly" message block

Resolved 💬 2 comments Opened Apr 8, 2026 by Reywedian Closed Apr 8, 2026

Bug Description
Title: /insights command: model omits "output exactly" message block, drops report file:// link

Summary:
When running /insights, the slash command's prompt ends with an instruction Now output the
following message exactly: followed by a <message>...</message> block containing the report file
path and a follow-up question. The model (Opus 4.6 1M context) outputs only the trailing question
and silently drops the first two lines containing the file:// link to the generated report.

Environment:

  • Claude Code v2.1.96
  • Model: Opus 4.6 (1M context) — claude-opus-4-6[1m]
  • Platform: Windows 11 Pro, bash shell
  • No custom /insights override (~/.claude/commands/ empty, no relevant plugins)

Steps to reproduce:

  1. Run /insights in a project with enough session history to generate a report.
  2. Observe model's text response.

Expected behavior:
Model outputs the full <message> block verbatim, including:
Your shareable insights report is ready:
file://C:\Users\lukak\.claude\usage-data\report.html

Want to dig into any section or try one of the suggestions?

Actual behavior:
Model outputs only:
Want to dig into any section or try one of the suggestions?
The file:// link is silently omitted. Reproduced twice in the same session.

Likely root cause:
The /insights prompt includes a Here is what the user sees: section that already contains the
rendered report with the file:// link near the end. The model appears to classify the second copy
in the <message> block as redundant and elides it under output-efficiency heuristics ("don't
restate what the user already saw"), overriding the literal output exactly instruction.

Suggested fix (Anthropic side):
Either (a) strengthen the /insights prompt wording to make literal compliance non-negotiable (e.g.
wrap in a fenced verbatim block, or repeat the "exactly, do not omit any line" constraint
immediately before the <message> tag), or (b) tune model behavior so that explicit output exactly
/ verbatim instructions always defeat output-efficiency heuristics, regardless of perceived
redundancy with surrounding context.

Impact:
User loses direct access to the generated HTML report path and has to either inspect the rendered
insights output manually or ask the model to retrieve it. Breaks a previously-reliable affordance
of /insights.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.96
  • Feedback ID: 035e19a8-81cd-485a-a185-530fe789c4d6

Errors

[]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗