Project memory

Project memory stores durable facts that should survive beyond one conversation. It is useful for architecture decisions, project vocabulary, recurring constraints, and discoveries that future tasks should not have to reconstruct.

Memory is local to the project and disabled until you enable it.

Enable memory

1. Open BIGGI → Settings → Context.
2. Find Project memory.
3. Enable memory for the current project.
4. Optionally enable automatic saving from completed turns.

BIGGI creates a local memory index for the project. The settings screen shows the stored index size and the approximate startup context added to the current session.

What to remember

Good memory entries are stable and specific:

• “Runtime save data uses schema version 3 and migrates through src/save/migrate.ts.”
• “The authoritative player speed is in MovementConfig; scene overrides are not allowed.”
• “Browser playtests use the gameplay fixture and require port 4173.”

Avoid:

• Temporary task status
• Secrets or credentials
• Large copies of source files
• Facts that can be discovered cheaply from one obvious file
• Guesses that have not been verified

Manage memory from chat

Use the memory control in the chat header to inspect status, remember a fact, forget a fact, rebuild the index, or disable memory. When memory contributes to a turn, the conversation can show injected or recalled memory badges.

Automatic saving

Automatic saving extracts durable project facts from completed turns. Review the memory index periodically; an agent can mistake a temporary condition for a stable rule.

Disable automatic saving when the repository contains sensitive information that should not be summarized into a separate local index.

Memory, instructions, and indexing

Use instructions for policy and memory for verified project knowledge.