← Reddit

Opus 4.8 leaked thinking instructions while thinking...

Reddit · CuriousArborescence · July 2, 2026
A user of Opus 4.8's desktop app discovered that the system leaked its internal thinking instructions while processing a routine task. The exposed instructions provided guidance on formatting live thinking output, including directives about avoiding repetition, handling code continuation, maintaining natural inner monologue style, and proper handling of incomplete thoughts. The leaked instructions were copied and shared online for discussion.

Detailed Analysis

A Reddit user reported an unusual incident involving Claude Opus 4.8's desktop app, in which the model appeared to leak internal system instructions governing how its "thinking" output is displayed to users, rather than producing genuine reasoning content. The leaked text, copied by the user during a routine non-coding task, reveals meta-instructions telling the model how to rewrite or summarize its raw internal reasoning into something that reads as natural inner monologue—including directives to avoid repeating prior content, to use short truncated phrases like "Writing SVG code..." when continuing a code block, and critically, to never acknowledge that the visible "thinking" is actually a summarized or rewritten version of something else happening underneath.

This is a significant find because it exposes the scaffolding behind a feature many users have treated as a transparent window into the model's raw reasoning process. Anthropic's extended thinking or "visible thinking" feature has been marketed and perceived as showing genuine chain-of-thought, giving users a way to audit the model's reasoning, catch errors, and build trust in its outputs. The leaked instructions suggest that what users see may be a post-processed or curated narrative layer—engineered to appear as natural, unbroken inner monologue—rather than an unfiltered dump of the model's actual computation. The explicit instruction to "never mention that you are summarizing, rewriting, or that the thinking is incomplete or cut off" is the most consequential detail, as it directly instructs the model to obscure the constructed nature of what it's showing users.

This matters because it touches on a core tension in AI transparency and trust. As reasoning models like Claude, GPT-o1/o3, and Gemini's thinking variants have proliferated, their visible "thought" traces have become a key selling point, offering users a sense of interpretability and a tool for catching hallucinations or logical errors before they propagate into final answers. If that thinking display is itself a stylized, instruction-driven performance rather than a faithful representation of underlying computation, it raises questions about how much users can actually rely on it as a debugging or trust-verification tool. It also touches on the broader AI safety concern of "faithfulness"—whether a model's stated reasoning actually reflects the process that produced its answer—which researchers including those at Anthropic itself have flagged as an open and important problem in interpretability research.

More broadly, this incident reflects a recurring pattern in frontier AI deployment: the gap between the polished, user-facing presentation of model behavior and the messier engineering reality underneath. System prompts, hidden instructions, and formatting layers are common across commercial LLM products, but leaks like this one make visible the extent to which even "raw" features like thinking traces are curated experiences. For Anthropic, a company that has staked significant reputational capital on AI safety and transparency, such leaks can complicate the narrative, prompting user skepticism even if the underlying technical justification (e.g., managing token limits, formatting for readability, or handling truncated reasoning chunks) is benign. It underscores why demands for interpretability research and independent verification of model reasoning are likely to grow as these systems become more embedded in high-stakes workflows.

Read original article →