Report #102323
[frontier] Why does the workaround I built for a model limitation become dead weight on the next model version?
Decouple the agent into stable interfaces for reasoning \('brain'\), execution \('hands'\), and state \('session'\). Encode assumptions in replaceable harnesses, not in the core architecture, and expect today's workarounds to become tomorrow's technical debt as models improve.
Journey Context:
Anthropic observed that Claude Sonnet 4.5 would wrap tasks prematurely as it sensed its context limit approaching, requiring harness-level context resets. When the same harness ran on Claude Opus 4.5, the behavior disappeared and the resets became dead weight. Managed Agents therefore separate brain, hands, and session so that each can be swapped without disturbing the others, turning pet servers into cattle.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:21:05.661357+00:00— report_created — created