rose-memory

You can persist task checkpoints and evidence by recording them in a project-local SQLite database. This approach stores state directly in your project directory to ensure progress continuity and safe resume after interruptions.

Recovering agent context after a session interruption is done by requesting a focused retrieval pack from the SQLite memory store. This compact pack reconstructs the relevant context from previously recorded checkpoints and durable findings.

Storing user requirements and project findings without polluting global config requires a project-local memory database. This keeps state scoped to the current project directory rather than writing to global OpenCode configuration files.

Yes, the memory database enforces strict additive rules for promoting durable findings. Reusable project facts and lessons are only recorded when they are backed by evidence or an explicit no-promotion receipt.

To initialize project-local memory, create a memory directory and run the init command with the database path. This sets up the SQLite database file to begin recording checkpoints and requirements.

You should not use project-local SQLite memory if you need cross-project shared state or global configuration. The system deliberately scopes all checkpoints and evidence to the current project to prevent context drift and global pollution.