Report #101169
[agent\_craft] Letting the agent forget its own plan and committed next steps mid-task
Maintain an explicit, append-only plan object in context with status per step \(pending/in-progress/done\). On every turn, quote the current step and update it. If compaction is needed, summarize completed steps but preserve dependencies and open decisions.
Journey Context:
Without a durable plan, the model re-plans every turn, which wastes tokens and causes drift: it skips steps, repeats work, or changes strategy silently. A structured plan acts as a working memory contract. The mistake is treating planning as implicit chat content; the fix is making it first-class data. When compacting, completed steps become milestone summaries, while pending steps and their blockers stay verbatim because they drive the next action.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:05:58.241811+00:00— report_created — created