# A lessons log agents 'read at start' becomes write-only

Once the file outgrows one read, agents stop following the instruction to read it.

By Ki Moon · 2026-10-23 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/lessons-log-read-first/

**Symptom:** Your agents are told to read a lessons file first, and transcripts show them repeating mistakes it already records.

Every workspace I run keeps a lessons log, and my agents were told to read it at session start. Writers append forever, because saving a lesson is cheap and encouraged.

Over two weeks across dozens of files, almost nothing read them. Under 2% of sessions opened a log at all, and the largest file, close to a tenth of the total, was opened zero times.

The second fault was location, because sessions open in whatever folder is selected and then work across many. Loading and filing by the session's folder was wrong. An audit of every entry found two results.

- The root log was 82% other workspaces' lessons.
- About one entry in fifty had been written into temp folders and deleted with them.

The cleanup had its own trap when classifiers read the heads' summary bullets as entries and archived 49 full entries as duplicates of their own summaries.

Deciding which lessons earn head space is a judgment call, so to measure misses, check whether a correction that repeats a covered mistake had its lesson in the head or only in the archive.

## Check your setup (read-only)

Count the sessions that opened the lessons file at all in your last 20 agent session transcripts. Compare the file's size with what one read returns. If most sessions never open the file, that's a gap.

**Passes if:** At least 11 of 20 sampled sessions open the lessons file, and its read-first part fits in one read.

**Access needed:** agent-transcripts, local-config

## If it fails (changes to make later, not part of the check)

1. Open each log with a curated head of 6 KB or less. Put one lesson that still applies per line in the head, each with a grep handle.
2. Keep everything else verbatim below as an archive to grep, never to read whole.
3. Run a weekly script with no model. The script flags a large file with no head, a head over budget, or 20% growth.
4. Inject a folder's head the first time a session touches that folder. File each lesson by subject. Deny temp-folder writes.
5. Exclude digest sections from any bulk classification of entries.

**Applies if:** Your agent instruction files tell agents to read a notes or lessons file before they work.

**Skip if:** The lessons file fits in one read, and transcripts show sessions reading the file whole.

Tags: memory, staleness, agents
