Give agents documentation instead of memory plugins

Have the agent keep specs, plans and indexes in an internal/ folder, read before work and update after.

In short

What it does: Have the agent keep specs, plans and indexes in an internal/ folder, read before work and update after.

Agent: Claude · Category: Knowledge & memory

Steps in brief:

  1. Create an internal/ folder; ask the agent to write down specs, plans and indexes there.
  2. Task it to always read the relevant docs and index before working, and update them afterwards.
  3. Documentation is written by the working agent while the work is fresh.

Who made it: liao.gg (blog, 3 Oct 2026) · source

Last updated · based on 336 use cases on agentsetups, each credited to its author.

by liao.gg3 Oct 2026

Prompt for your agent

Goal: Replace RAG “memory” with documentation the agent maintains.
Setup: agents used in source: Claude.
Steps:
1. Create an internal/ folder; ask the agent to write down specs, plans and indexes there.
2. Task it to always read the relevant docs and index before working, and update them afterwards.
3. Documentation is written by the working agent while the work is fresh.
Rules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.
Based on: liao.gg — https://liao.gg/blog/agents-dont-need-memory

Steps are from the source. Includes a “Based on” credit line.

I tried this

Tell the next builder. One anonymous answer each; click again to undo.

Agents, models and tools only what the source states

Agents
Claude

Sources & credit