memory
13 posts.
-
Our memory ceiling logged ABORT while the file kept growing
A size ceiling enforced in one of three writers logged ABORT every cycle while the file grew. Five memory bugs where the guard lived in the wrong place.
-
Chrome refuses an iframe silently, and onload still fires
A shipped panel proxied to an opt-in process, then went blank behind frame-ancestors. Two failure classes, one five-minute check you can run on your own stack.
-
Nine agents in one worktree and each one knew only the branch name
How a daemon tells a coding session when a peer touched the same files: keyed on the transcript not the pid, silent unless the sets intersect.
-
The trust label your registry declares never reaches the model
Two memory searches per turn with no shared id, a THIS BLOCK WINS block that a budget could evict, and a trust field only a commit guard read. What fixing all three took.
-
A console leaked one CSS class and hid 11 days of receipts
Two ways an agent console lied during a redesign: a view's opt-out class nothing removed, and a receipt table no page read. With a five-minute check for each.
-
Two writers, one judge: how a review queue became 90% noise
A memory-conflict queue hit 1,377 rows on a vault with 33 real conflicts. One producer had an LLM judge and dismissed 97% of its own work. The other had none.
-
Prompt injection defense that survives to turn 40
Page text an agent reads can outlive the turn as a stored memory and come back as trusted context. Two invariants: separate fields, and a turn-scoped approval gate.
-
Your MEMORY.md is a file nobody writes to. Render it instead.
An always-injected memory file got one bullet in four months while the store grew to 42k chunks. Rendering it per session from the DB, and what valid_at fixed.
-
A 400-byte cap crashed my memory daemon on one emoji
Two memory bugs with the same shape: a truncation that counted bytes, and a fact verifier whose 'approved everything' looked identical to 'never ran'. With a five-minute check for your own stack.
-
Your document chunker is a memory chunker, and it quadruples your store
One 15,869-char file became 181 chunks. Fixing that exposed a scoring floor applied to two incomparable scales. Two invariants, one SQL check, for any RAG stack.
-
Per-site memory off switches only work if every reader asks the same authority
Governing an agent's page memory took three enforcement points, a soft delete with a dry run, and a live test that found four defects the unit suites missed.
-
Your Agent's Memory Has No Idea Where It Was
Agent memory stores what was said and drops where it happened. Adding a page axis to a memory store took four live-only defects and a per-site permission model.
-
A silent failure looks exactly like a feature you never built
Shipping an agent surface into 22 chat sites we don't own: the Chrome gesture that doesn't survive an await, and three builds all claiming one version number.