openclaw - 💡(How to fix) Fix MEMORY.md bootstrap truncation silently drops context with no warning [1 participants]

TL;DR

Implementing a truncation notice in the agent context is the most straightforward fix to ensure the agent is aware of potential missing memory entries.

Guidance

• Identify the current limit (12000 chars) and assess whether raising it is feasible and sufficient to accommodate typical MEMORY.md file sizes.
• Consider adding a user-facing warning when the file approaches or exceeds the limit to prompt users to manage their memory files.
• Inject a truncation notice into the agent context to notify it of potential incomplete memory, as suggested in Option 3 of the issue.
• Evaluate the impact of silently dropped memory entries on agent functionality and user experience to determine the best long-term solution.

Example

No specific code example is provided due to the lack of implementation details, but the fix would involve modifying the code that handles the injection of the workspace bootstrap file into the agent context to include a notice when truncation occurs.

Notes

The ideal solution depends on the typical size of MEMORY.md files and the consequences of truncation. Raising the limit might be a temporary fix if files continue to grow, while surfacing a warning to the user or injecting a truncation notice provides more immediate feedback on potential issues.

Recommendation

Apply workaround: Inject a truncation notice into the agent context. This approach ensures the agent is aware of potential missing entries without requiring immediate changes to the limit or user-facing warnings, addressing the immediate need for the agent to not silently assume its memory is complete.