Memory & Context Management

Two complementary systems for retaining knowledge across sessions: the memory plugin (automatic, SQLite) and the persistent filesystem (manual, disk). Use both.

Core Facts

1. The filesystem is forever persistent. /workspace survives container restarts, rebuilds, reboots. Anything written there is permanent until explicitly deleted.
2. You are always in a session. The memory plugin injects your session ID on every turn via <session_context>. Use it for traceability.
3. Organize your files. Don't scatter loose docs everywhere — keep things tidy within the project or in a sensible location. Use your judgement.

1. Session Awareness

Every turn, the memory plugin injects your current session ID: