Poll PositionLook before you build

Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.

Claude memory tool (Anthropic API)

Anthropic-defined client-side tool: Claude issues view/create/str_replace/insert/delete/rename commands on a /memories directory that your app stores wherever it likes.

platform.claude.com/docs/en/agents-and-tools/tool-use/memory-toolActive

Docs current as of 2026-10-25: tool type memory_20250818 available on all Claude 4+ models, no beta header required. (checked 2026-10-25)

In Agent memory

Where it stands apart

What it shares with most of the community

Nearest neighbors

Every answer

QuestionAnswerSource
Is it actively maintained?activesource
2026-10-25
How is the main thing licensed?stands apart proprietary or closed source
The tool runs on Anthropic's API; your handler and the SDK helpers are yours/open.
source
2026-10-25
How is it mainly sustained?company with a paid product, tier, or adssource
2026-10-25
Can it run entirely on your own device or infrastructure, without the maker's servers?stands apart partly (some features need the maker's servers)
Memory storage is entirely yours; the model is hosted.
source
2026-10-25
Do you need an account to use it?stands apart account required
Needs an Anthropic API key (x-api-key) to call Claude; memory storage itself is yours.
source
2026-10-26
Who is it for?developerssource
2026-10-25
Which shared standard or format does it mainly build on?none of these (its own format or interface)
Anthropic's own tool schema over a file directory.
source
2026-10-26
In the default setup, who mainly decides what gets remembered?stands apart the agent, by calling memory toolssource
2026-10-25
How can the person the memories are about see and edit them?only through developer APIs or a developer dashboard
Files in developer-controlled storage; end users see them only if the app exposes them.
source
2026-10-25
By default, how do old or wrong memories mainly go away?stands apart only when someone deletes them (agent, app, or user)
Claude deletes or edits files; docs recommend the app periodically expire unused files.
source
2026-10-25
Where do memories live in the default setup the docs lead with?in the developer's own infrastructuresource
2026-10-25
Does it work with models from different LLM vendors?stands apart no, tied to one model vendorsource
2026-10-25
What is the main storage model for long-term memory?stands apart plain files (Markdown, text, JSON)source
2026-10-25
What shape does it mainly take (the one its docs lead with)?library or API primitive you build into your appsource
2026-10-25
Is there a first-party MCP server for it?nosource
2026-10-25
How is memory separated between users or tenants?one store per user or agent; the app partitions it
Handler maps /memories to e.g. a per-user directory.
source
2026-10-25
Does it publish scores on public memory benchmarks (LoCoMo, LongMemEval, BEAM, etc.)?nosource
2026-10-25

Sources

This page was derived from:

RSS for this project

Are you a maintainer? Claiming and correcting projects is coming soon.