Agents
@hwchase17 is right, memory creates lock-in. But not just conversations. Tool registries, hooks, agent conventions -> that's harness memory …
@hwchase17 is right, memory creates lock-in. But not just conversations. Tool registries, hooks, agent conventions -> that's harness memory too. In my setup I define agent tools once in a shared regis
@hwchase17 is right, memory creates lock-in. But not just conversations. Tool registries, hooks, agent conventions -> that's harness memory too. In my setup I define agent tools once in a shared registry and a hook blocks any edit that drifts. Can't do that on closed harness.
Related
- The ‘agent harness’ is essentially the new runtime. It’s like a lightweight OS around an LLM—handling memory, tool calls, retries, and contr…
- memory is just context -> the harness decides what gets remembered, how, and when memory ownership = agent ownership deepagents lets you own…
- a big part of agent harnesses is how they interact with context memory is just context its therefor impossible to separate harness from memo…
- @hwchase17 middleware was the right abstraction for it too. way more adoptable than asking everyone to restructure their agent setup
- here's how we're improving our base harness, you can apply these same lessons to hill-climbing for your application-specific harness!
- deepagents is a harness / planning tool, filesystem backend, subagent spawning, memory management / thats the stack that matters / models ar…
Source: Harrison Chase (X) | 2026-04-12