Giving Claude unlimited memory using external note files

Executive overview

Every AI has a fixed context window. When processing large batches of files — transcripts, emails, tickets — the model forgets earlier work before it finishes. The fix is to externalise memory into files the AI writes and reads itself, so it can resume after each context reset.

Three files do the work: a context file (the goal), a to-dos file (a checklist), and an insights file (accumulated output). Claude Code — or any tool that can read and write local files — runs the cycle autonomously until all items are processed.

The model never loses progress because the notes, not the context window, are the memory.

The three-file memory system

• Context file: stores the original goal so the AI re-reads it after each reset
• To-dos file: a numbered checklist the AI ticks off as it finishes each item
• Insights file: the AI appends findings after processing each file, never overwriting
• All three are markdown — lighter on memory and supports checkboxes

How the processing cycle works

• AI reads the context and to-dos files before starting any work
• Processes each file, updates insights and checks off the to-do entry
• Just before context is compacted, it ensures the to-dos are current
• After the reset, it re-reads context and to-dos, then continues from where it stopped
• The prompt ends with an explicit instruction to keep running until all files are done

Setting up Claude Code (no code required)

• Download the Claude desktop app and switch from Chat to Code mode
• Select the local folder containing your input files
• Change the mode from Ask to Act so Claude acts autonomously
• Set the model to Opus for highest quality; drop to Sonnet or Haiku if usage is limited
• Paste the prompt and press enter — no terminal or coding knowledge needed

Prompt structure

• Top section sets the goal and names the folder Claude should work in
• "Before you start" block instructs Claude to create the three memory files
• "As you work" block reinforces iterative updates and pre-wipe checklist saves
• "After memory wipe" block tells Claude to re-read context and to-dos first
• Bottom section specifies what to extract and adds a constraint to run until complete

Example use cases

• Extract customer language (frustration, fear, confusion) from prospect call transcripts for ad copy
• Generate grounded FAQs from real client questions, including predicted follow-ups
• Identify churn signals from client call recordings before customers leave
• Aggregate feature requests across hundreds of client conversations
• Rank and prioritise unanswered inbox leads by conversion likelihood