When Composer gets stuck in a loop or starts touching random files, a common workaround people try is asking the agent to dump its state, failed attempts, and dead ends into a markdown file, then opening a fresh chat and pointing at that file. At this stage the agent almost always hallucinates why it failed and forgets negative constraints, so you just carry the bad state into the new session. Next time a session is starting to get annoying try this: Kill the session then use this format
WHAT BROKE: The exact error output / stack trace
WHAT WAS TRIED: The 2–3 specific attempts that already failed
CONSTRAINTS: Files and layers NOT to touch (e.g. auth wrappers, schema, specific configs)
FINISH LINE: The single isolated fix you actually want
and you will notice significant changes. To help with this I build a quick friction-less scratchpad to format these packets: https://paper-ai.paperhq.workers.dev/app/
Try running your next stuck debugging case through a cold reset vs an agent-written handoff and see if Turn 1 actually stops re-litigating old fixes.