You can never really sympathise with other’s pain until you walk a mile in their shoes. Since Mythos news and the release of Opus 4.7, I’ve seen this problem mentioned here and there by others. Now I have finally came across it myself. I have a research agent I kickoff for technical research for grounding. For this particular research, it seems the cyber-content classifier triggered on something in the agent’s research path (likely the supply-chain attack / post-mortem references). I had to relaunch three times. Third time being a clean retry with the supply-chain-incident framing removed from the prompt. The research in question? Research findings on the current (2025-2026) frontend, meta-framework, component library, styling, state management, build tool, package manager, BFF runtime, and type system landscape, evaluated against the project’s specific structural requirements. Surface options, structural properties that make each option load-bearing, production validation at scale, performance envelopes, accessibility ergonomics, supply-chain attack surface and ownership, multi-tenant ergonomics, real-time streaming integration, and tradeoffs. I guess we are not allowed to secure our own software by researching and grounding the model against researched information. That’s only reserved for the special project Glassdoor participants. submitted by /u/mystic_unicorn_soul
Originally posted by u/mystic_unicorn_soul on r/ClaudeCode