I ran 4.8 the same way I ran 4.7 for the first week. Tight coding loops, direct conversation, shorter sessions. It felt paranoid. Kept re-reading files I hadn’t touched, flagged prompt injections that weren’t there, burned tokens on verification cycles I never asked for. Then I read the system card. The headline improvement in 4.8 isn’t code generation. It’s long-context graph traversal: GraphWalks BFS F1 jumped from 76.9% to 85.9% at 256K context. Those are gains in reasoning across graph-structured memory, not in tight single-file edits. The prompt injection paranoia has a number behind it too: 4.8 is measurably more suspicious by design, slightly worse than 4.7 on coding injection without safeguards, because it was calibrated to handle indirect injection from tool results and external data at scale. 4.8 pairs with dynamic workflows: Claude writes a JS orchestration script, fans out to sub-agents, intermediate results live in script variables not the context window, resumable within session. The re-reading behavior makes sense in that architecture, since an orchestrator managing hundreds of sub-agents needs to confirm state before routing. In a tight conversation loop, that same behavior reads as regression. My read: most of what people are calling “paranoid” is 4.8 doing exactly what it was calibrated to do, in a usage pattern it wasn’t built for. That’s from an Enterprise/Team/Max context where dynamic workflows actually run. If you’re on Pro, the plan-tier gate silently degrades to solo mode anyway, so you get 4.8’s overhead with none of the architectural benefit. Haven’t tested that path myself. submitted by /u/Unlikely_Ad_8060
Originally posted by u/Unlikely_Ad_8060 on r/ClaudeCode
You must log in or # to comment.