Files beat settings: Claude's memory is just markdown
Two memory UIs shipped this year. One is a settings panel. One is a folder. The folder is winning on every design axis that matters.
→ MEMORYField Notes
Everything here was chosen and explained by a person: essays when there's an argument to make, notes when an observation is worth keeping. Every note says why it was clipped and attaches to the pattern it evidences.
Two memory UIs shipped this year. One is a settings panel. One is a folder. The folder is winning on every design axis that matters.
→ MEMORYWhen the shopper is an agent, ranking incentives invert — position bias weakens and structured data wins. Anyone designing storefronts for delegated purchases should read this.
watching → emerging → established
A stable convention across independent vendors. Safe to standardize on — deviating from it now carries cost.
3 documented sightings since May 2026 — every one traces to a dated source.
See the evidence →113 people wrote their own permission policies and the agents overreached anyway — user-authored scope is not a control surface. Strong boundary evidence for visible, editable trust scopes.
watching → emerging → established
A stable convention across independent vendors. Safe to standardize on — deviating from it now carries cost.
5 documented sightings since Jun 2026 — every one traces to a dated source.
See the evidence →Google planting an open-source agent in the terminal confirms the CLI as the contested surface for coding agents — and open-sources the control loop others keep proprietary.
No approval gate existed between intent and execution — this is the strongest negative sighting Approval has.
watching → emerging → established
A stable convention across independent vendors. Safe to standardize on — deviating from it now carries cost.
5 documented sightings since Jun 2026 — every one traces to a dated source.
See the evidence →Auto mode trades the gate for speed, and prompt injection walks straight through — a gate only protects when it can't be talked out of. The approval pattern's boundary condition, demonstrated.
watching → emerging → established
A stable convention across independent vendors. Safe to standardize on — deviating from it now carries cost.
5 documented sightings since Jun 2026 — every one traces to a dated source.
See the evidence →The bottleneck in the two-dozen-agent future isn't model quality, it's legibility — knowing who is doing what. Exactly the roster and ambient-status behaviors on our watching list.
watching → emerging → established
A candidate behavior, not yet a published pattern. Early signal — worth tracking, not yet worth standardizing on.
1 documented sighting since Aug 2026 — every one traces to a dated source.
See the evidence →The reverse of delegation was always the weaker half of the loop. It just cleared the promotion bar.
→ HUMAN HANDOFFMulti-file edits raise the stakes of every gate: approve and undo now span a changeset, not a file. Recovery patterns are about to matter more than approval ones.
watching → emerging → established
Seen across products but the shape is still settling. Adopt with an exit: expect the anatomy to shift.
3 documented sightings since Feb 2026 — every one traces to a dated source.
See the evidence →Background agents are multiplying, and every product is inventing a peripheral signal for "what is my agent doing" — menu bars, badges, toasts. Three sightings and counting.
→ AMBIENT STATUSThe same transparency artifact — a step list — plays two different roles depending on whether execution waits for you.
→ PLANNINGClaude Code's plan approval moves the gate from every action to the shape of the work — and that changes what approval means.
→ APPROVALAgentic experience design, coding agents, MCP, and the signals that matter — weekly, free, in about five minutes.
Free. No spam. Unsubscribe anytime.