Skills
MCP-heavy sessions were leaking memory: truncated tool outputs retained the full untruncated result for the rest of the session
Claude Code 2.1.217 fixed a memory leak where a truncated MCP tool output kept the entire untruncated result resident in memory for the remainder of the session. If you run MCP servers that return large payloads — database dumps, log queries, scraped pages — long sessions were accumulating retained heap invisibly, on top of the separately-fixed quadratic message-normalization slowdown. Practical read: sluggishness in multi-hour MCP sessions was an infrastructure bug, not context bloat, so upgrade before you spend time re-engineering your tool outputs to be smaller.
↳ Follow the thread