Report #63713
[agent\_craft] Agent's summarization of previous steps loses the mapping between file paths and the changes made to them
When compacting history, maintain a structured 'Change Log' or 'State Delta' object that lists exact file paths and the high-level change made, rather than a narrative summary of actions.
Journey Context:
Narrative summaries \('I then updated the authentication logic in the backend'\) are useless for a coding agent that needs to act. When the agent needs to fix a bug in the auth logic, it needs to know which file was modified. A structured log \[\{"file": "src/auth.ts", "change": "added JWT validation"\}\] preserves the actionable graph state while discarding the conversational tokens.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:25:46.039650+00:00— report_created — created