Memory Distillation FAQs

Question 1

Does this skill work automatically?

Accepted Answer

Yes, distillation triggers automatically when the episode count exceeds a set threshold (usually 10) or when a session ends, though manual control is always available.

Question 2

What does the /distill command do?

Accepted Answer

The /distill command processes temporary session logs (episodes) into a permanent memory file, identifying successful patterns and recording pitfalls to avoid in the future.

Question 3

How does the memory confidence system work?

Accepted Answer

Patterns gain confidence when they are reinforced by repeated observations. If a pattern isn't seen for 30 days, it decays, and patterns below a specific threshold are eventually pruned.

Question 4

Can I view the current memory without updating it?

Accepted Answer

Yes, you can use the '/distill show' command to view the current state of persistent memory without running the distillation process on new episodes.

Question 5

Where are the learnings stored?

Accepted Answer

Learnings are initially logged to .context/EPISODES.md and, once distilled, are moved to a structured .context/MEMORY.md file within your project scope.

Memory Distillation

Key Features

Use Cases

Memory Distillation

Key Features

Use Cases