mem0 2.1.0 tracks the full plugin chain calling it

mem0 released version 2.1.0 with a specific fix to how it identifies callers. mem0's v2.1.0 release notes add three set-once headers that carry surface identity. One of them, X-Mem0-Client, is append-only and lists name/version for every layer in the call chain, outermost first.

That matters if you've built on an SDK that gets wrapped by something else. Before this, a plugin calling into the mem0 SDK reported only itself as the client, not the plugin that invoked it. Now the whole chain shows up, so debugging which layer in a stack made a call gets you the full path rather than the last hop alone.

The header stack has a size limit. When it's full, mem0 drops whole entries instead of slicing characters off the end. Cutting a name mid-string could leave a fragment that looks like a different, real client name. The platform would then read that fragment as a legitimate one.