FindingcurrentRunning agents

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

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

SymptomYour 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 ifAt least 11 of 20 sampled sessions open the lessons file, and its read-first part fits in one read.

Access needed:agent-transcriptslocal-config

If it fails: changes to make later (not part of the check)
  1. 01Open 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. 02Keep everything else verbatim below as an archive to grep, never to read whole.
  3. 03Run a weekly script with no model. The script flags a large file with no head, a head over budget, or 20% growth.
  4. 04Inject a folder's head the first time a session touches that folder. File each lesson by subject. Deny temp-folder writes.
  5. 05Exclude digest sections from any bulk classification of entries.
Applies ifYour agent instruction files tell agents to read a notes or lessons file before they work.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.