hermes - 💡(How to fix) Fix [Feature]: memory tool needs read action, better error messages, and pressure warnings [1 participants]

The memory tool currently only supports add/replace/remove. When memory is full or nearly full, the agent has no way to inspect the current state (entry sizes, usage breakdown) and the error messages are too vague to take corrective action.

• Error messages on add/replace failure only say "would exceed limit" without showing available space or per-entry sizes

1. Improve error messages on add/replace failure: show current usage, available space, entry sizes with index, and specific overshoot amount Commit: feat(memory): add read action, improve error messages, and add pressure warning on fork GongShi5201/hermes-agent

TL;DR

Implement the proposed solution by adding a read action, improving error messages, introducing an event-driven pressure warning, and doubling the default limits to provide better memory management and error handling.

Guidance

• Review the implementation changes in tools/memory_tool.py, hermes_cli/config.py, and tests/tools/test_memory_tool.py to understand the proposed solution.
• Verify that the new read action returns the expected information, including entry sizes, usage breakdown, and previews.
• Test the improved error messages to ensure they provide sufficient information for corrective action, including available space, per-entry sizes, and specific overshoot amounts.
• Check the event-driven pressure warning is emitted at 80%+ usage and saves tokens by not being included in the system prompt schema description.

Example

No code snippet is provided as the issue already includes a detailed description of the proposed solution and implementation.

Notes

The proposed solution assumes that the current implementation of the memory tool is correct and the changes will fix the existing issues. However, it's essential to thoroughly test the new functionality to ensure it works as expected.

Recommendation

Apply the proposed workaround by implementing the changes outlined in the issue, as they provide a comprehensive solution to the existing problems with memory management and error handling. The changes are already tested and seem to address the issues, making them a suitable solution.