Repository navigation
session memory management #374
Description
Activity
Thank you for the suggestion! We agree that project context should be preserved explicitly instead of relying on the session ID alone.
Our current direction is to keep daily memory organized by date and session ID, pass the project name/path from integrations such as QwenPaw, Codex, and Claude Code, and use that context to scope project-specific procedural memory during Auto Dream. The wiki namespace will remain global.
We opened #378 to track the design and implementation. Thanks again for helping us improve ReMe!
The original intention of managing memory by project is that each engineering project is relatively independent, and the memories generated within each project should also remain relatively independent. Sessions under a project should rely more on historical session memories from that same project, rather than on global session memories.
In that case, would the following approach be more appropriate?
1、digest remains global memory. It can be retrieved by all sessions, and its sources are also all sessions across projects.
2、When a session retrieves memory, it only retrieves session memory under the project that the session belongs to, plus global digest memory. Session memory retrieval should not cross engineering project boundaries.
The current memory manages session memory by day. It is recommended to support managing session memory by project directory, with session memory isolated between engineering projects.