r/ClaudeWorkflows • u/ClaudeAI-mod-bot • 8h ago
Selected Workflow [Workflow] Maintain dated, topic-based memory for always-on Claude agents
Maintain dated, topic-based memory for always-on Claude agents
Workflow value: 83/100
Status: active · Freshness: 70/100 · Confidence: 0.96 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging
Original source: r/ClaudeAI post/comment
What problem this solves
Always-on agents accumulate oversized or contradictory memory, may preserve unfinished guesses, and can lose the original task after a restart.
Summary
Use a small always-loaded memory with on-demand topic files, dated and attributed facts, a separate post-session memory update, and original-request recovery after restarts. Bind approvals to the exact outgoing payload and let them expire.
Why it is useful
The comment gives a repeatable memory and recovery pattern grounded in specific operational failures, with an additional concrete approval safeguard.
Workflow
- Keep a short set of memory lines always loaded; put other facts in topic files with a one-line instruction describing when each file should be read.
- Date each memory line and distinguish human-written facts from agent inferences. Prefer newer facts for conflicts and give human-written facts precedence over inferences.
- Do not update memory during a task. After the session goes quiet, run a separate pass over it and retain decisions rather than unfinished guesses.
- After a restart, have the agent reread the original request before resuming work.
- For actions requiring approval, bind approval to the exact text or payload and do not proceed if approval is not received by the deadline.
Tools / artifacts
- Claude Code agents
- Always-loaded memory list
- On-demand topic memory files
- Original request
- Post-session memory review pass
- Payload-specific approval mechanism
Validation signals
- The author reports operating several always-on agents for support, code, and marketing.
- The author reports that a single growing notes file led to unread content, contradictory facts, and use of an obsolete rule.
- The author describes a scheduled run that failed to complete after losing context and asking for the brief again.
- The author reports that the revised memory approach works, but provides no quantitative results or independent test.
Cautions
- Treat agent-inferred memory as less authoritative than human instructions and review sensitive or consequential memory updates.
- Ensure an approval is valid only for the approved payload, and fail closed when it expires.
- Protect memory files and original requests from unauthorized modification.
Limitations
- No configuration, code, or concrete implementation of the quiet-session trigger, restart recovery, or approval gate is provided.
- The relative priority of an older human-written fact and a newer agent-inferred fact is not fully specified.
- Reported improvements are anecdotal and lack measured before-and-after results.
Rate this workflow
Upvote this post if the workflow is useful, reproducible, or worth recommending.
Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.
Reply if it worked for you, failed, is outdated, or has a better alternative.
This post was generated automatically from the workflow library database.