Agents
This post completely misses the point of @sarahwooders 's original article. The whole point is that memory == context engineering, so it can…
This post completely misses the point of @sarahwooders 's original article. The whole point is that memory == context engineering, so it can't be a 'thin conductor'. Saying 'memory is just markdown' t
This post completely misses the point of @sarahwooders 's original article. The whole point is that memory == context engineering, so it can't be a "thin conductor". Saying "memory is just markdown" then embedding the files is just reinventing RAG from first principles. If your memory dies when your harness dies, you built the harness too thick. Memory is markdown. Skills are markdown. Brain is a git repo. The harness is a thin conductor — it reads the files, it doesn't own them.
Related
- a big part of agent harnesses is how they interact with context memory is just context its therefor impossible to separate harness from memo…
- ended up writing similar style post: your harness, your memory https://x.com/hwchase17/status/2042978500567609738 cited @sarahwooders post a…
- 100% this. Memory is just a form of context. Context is all you need, and context is everything when making a great agent.
- memory is just context -> the harness decides what gets remembered, how, and when memory ownership = agent ownership deepagents lets you own…
- Very good article from @hwchase17 about the agent harness and memory achitecture.
- lots that i agree with in here, especially about the importance of not locking in
Source: Harrison Chase (X) | 2026-04-13