Report #101396
[frontier] Accumulated context pollutes the agent's reasoning in long autonomous loops
Spawn a fresh session per task iteration; keep all progress in files, not transcript; re-read specs and git state at the start of every iteration; never nest same-session and fresh-context drivers.
Journey Context:
The Ralph pattern \(Flow-Next\) inverts the usual stop-hook loop: instead of keeping Claude alive in one session, an external bash loop starts a fresh \`claude -p\` for each unit of work. Failed attempts evaporate with the session, and the agent re-anchors from \`.flow/specs/\` every time. This trades conversation continuity for reliability. In 2026 this is becoming the default for overnight autonomous runs, while same-session mode is reserved for bounded tasks where context actually helps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:29:10.218015+00:00— report_created — created