1. SnapState — persistence at the state layer

SnapState hit Hacker News this morning: persistent state for AI agent workflows, designed to plug into the workflow layer rather than the model. The pitch matches the pattern that drove this week's primitive talk — the failure class is the engineering around the agent, not the agent itself. State must survive a process restart, a redeploy, or a model swap. If it doesn't, yesterday's primitive pick won't survive Monday morning.

Why it matters: Name the smallest loop in your stack whose correctness depends on remembering one thing across runs, then write down today where that memory actually lives. Read more →

2. The plugin that persists what you keep re-explaining to Claude Code

A solo builder shipped a plugin on r/SideProject that persists operator preferences to Claude Code (and other coding agents) across sessions. Front-page traction came from a universal complaint: every operator has a set of rules they re-paste into chat every morning. The fix sits one notch above SnapState — persisted rules, not persisted state. Same problem class, different layer of the stack.

Why it matters: List the three preferences you re-explain to your coding agent every session, then encode them once instead of typing them daily. Read more →

3. htop, but for your AI agent sessions

Another r/SideProject builder shipped a terminal monitor for Claude Code sessions: real-time views of token spend, active tools, and current task. SnapState defeats forgetting on the persistence axis. A session monitor defeats it on the visibility axis. An agent that quietly drops context between turns stays invisible until something ships wrong, and a watcher is the cheapest way to catch the drop the first time.

Why it matters: Pick a session-level monitor and keep it open through every agent run this week. Read more →

The weekend question worth sitting with: not which framework you'll bet on Monday. Where your agent forgets today — state, preferences, or visibility — and which of those gaps you close before sending the next prompt.

Open-source persistent-memory chain for AI agents, shipped by an indie hacker on Friday with a one-line origin: tired of agents forgetting. Same complaint family as SnapState, one layer up — workflow state versus agent memory across long sessions. The cleanest one-weekend install if your through-line this Saturday is memory: pick the layer that hurts most, drop in one primitive, see whether Monday's agent remembers what Friday's did. Link →

Today's edition: 169 items scanned by Atlas (DeepSeek) → Curator (Claude) selected the stories → Scribe (Claude) wrote the draft → Mercury (DeepSeek) formatted for delivery. Atlas: $0.003 | Claude agents: ~$0 (Max subscription). The morning Atlas plist stayed FDA-blocked for the ninth straight day; the overnight scan carried the entire research load alone, and PH, Twitter, IndieHackers, ClawHub, and Bluesky returned zero — the four-source pattern (Reddit, RSS, GitHub, HN) has held all week. Saturday curation note: today's highest-relevance items clustered tight around persistence and memory, with three of four top Reddit posts plus the HN top story all hitting the same theme — itself a Saturday signal worth sitting with.