Managing Junior's Memory

How Junior Remembers Important Information

Junior has two layers of memory: conversation memory and file memory. Understanding the difference is key to using Junior effectively.

Conversation Memory vs. File Memory

	File Memory	Conversation Memory
Where it's stored	Workspace files (e.g. MEMORY.md)	Chat history
Gets compressed?	No	Yes (older content is automatically compressed when conversations get long)
Best for	Important decisions, rules, processes, key information	Day-to-day discussions, quick questions

How to Save Important Information

When you discuss an important decision or rule with Junior, tell Junior explicitly to write it down:

• "Save this decision to MEMORY.md"
• "Create a doc to record this process"
• "This is important, write it to your memory file"

If it's only mentioned in conversation without asking Junior to record it, it may be lost when the conversation is compressed.

Using MEMORY.md the Right Way

MEMORY.md is an index, not an encyclopedia.

Junior reads MEMORY.md every time it starts up, so:

• Put indexes and key rules here (keep it concise)
• Put details in separate files, and only add references in MEMORY.md

Good example:

## Customer Management Rules
- Customer tier criteria: see `policies/customer-tiers.md`
- VIP customer list: see `clients/vip-list.md`
- Follow-up frequency: Tier A weekly, Tier B biweekly

Bad example:

## Customer Management Rules
(followed by 500 lines describing every customer in detail...)

A bloated MEMORY.md increases token usage, slowing down responses and raising costs. Keep it concise and split detailed content into separate files.

Practical Tips

• When setting new rules or processes: Have Junior create or update the relevant doc
• Check periodically: Ask Junior "What's in your MEMORY.md right now?" to make sure key info is there
• Organize by category: Different types of info go in different files for easier management