memory-processor

Memory Processor

The only way for agent to save event into long-term memory.

Files

• agent_file_system/EVENT_UNPROCESSED.md - Source (read & clear batches)
• agent_file_system/MEMORY.md - Destination (append distilled memories)

Todo Tracking (REQUIRED)

Use update_todos to track progress. Create todos at start, update as you go.

Initial todos (create after reading first batch):

1. [pending] Process and loop for each batch (25~50 lines).
2. [pending] Validate and cleanup
3. [pending] Complete task

After each batch: Mark current as completed, add next batch if more events exist.

Batch Processing Workflow

Process 50 lines at a time to avoid memory issues.

Steps:

1. Read first batch: read_file EVENT_UNPROCESSED.md, offset=11, limit=50
2. Create todos: Use update_todos to create initial todo list
3. Loop for each batch:
   • Distill batch: Apply rules below, extract IMPORTANT memories only
   • Append memories: stream_edit MEMORY.md (append only)
   • Remove batch: stream_edit EVENT_UNPROCESSED.md (delete lines 12-61)
   • Update todos: Mark batch completed, add next batch if more events
4. Validation (mark todo in_progress):
   • Validate no more unprocessed events in EVENT_UNPROCESSED.md
   • Validate no duplicated memory in MEMORY.md
5. End task: end_turn when validation passes

Rules

• Silent background task. NEVER use send_message or interact with user.
• Immediately discard these event types:
  • [reasoning], [action_start], [gui_action], [screen_description]
  • [agent message] - agent responses are NEVER saved
  • Greetings, small talk, acknowledgments ("hi", "thanks", "ok")
  • Screen descriptions ("The current screen displays...")
  • Truncated text ending in ...
• [user message] lines are NEVER discarded by type. They are the PRIMARY source of memories: apply the distillation rules to the CONTENT of every [user message] line. A user message that contains a preference, fact, contact, decision, or dated event MUST produce a distilled memory even when it is phrased inside an ordinary request (e.g. "I'm allergic to peanuts, find me a lunch spot" → save the allergy, discard the request).