Shipped · Databases

What supermemoryai/supermemory shipped

The public repository of Supermemory · github.com/supermemoryai/supermemory

Written by FoxPlug from the repository's own releases; not affiliated with Supermemory. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/supermemoryai/supermemory; Supermemory did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for supermemory, free

Week of November 2, 2026

What shipped

Why it matters

This week production deploy failures were addressed, and the security patch for the Next.js remote code execution advisory is now able to go live. The MCP graph tools also moved off the last legacy call to the v5 namespace graph feed, with paging by cursor. Developers get a more reliable build and deploy path and docs that match the v5 list endpoint's cursor pagination.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: patched the Next.js RCE advisory and MCP SDK advisories, fixed production deploys with OpenNext's static-assets cache, dropped DM Sans to unblock builds, moved the MCP graph tools to the v5 namespace graph feed, and synced docs with v5 cursor pagination.

Post for LinkedIn

This week: the web app's Next.js pin moved to 16.4.1 to patch an unauthenticated RCE advisory, a Server Actions denial of service advisory and MCP SDK advisories. Production deploys were unblocked by switching the web app to OpenNext's static-assets cache and bumping OpenNext so next 16.4.1 stops returning 500 on every page. DM Sans was dropped so builds stop fetching Google Fonts URLs that next/font/google cannot parse. The MCP graph tools now read the v5 namespace graph feed with cursor paging instead of the legacy v3 documents route. The docs were synced with cursor pagination for the v5 list endpoint, shipping in the TypeScript SDK from 5.1.1.

Week of October 26, 2026

What shipped

Why it matters

This week fixed a misleading confirmation message: adding a memory now reports that the document was accepted and extraction continues in the background, and the tools expose the existing dreaming status. The hosted worker also got a patch bump to stay consistent with the earlier API-key validation change, while dependency updates closed two alerts. Docs work covered a full drift audit and small fixes, and a new AGENTS.md gives coding agents correct project instructions in one place.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: tool responses now say when a document is accepted and memories are extracted in the background, and document tools expose dreaming status. The hosted worker moved to 1.0.1, two dependency alerts closed, and docs went through a full drift audit.

Post for LinkedIn

This week's changes to the project: the add memory tool now reports what actually happened, that the document was accepted and memories are extracted in the background, and the document listing and single document tools expose the existing dreaming status. The hosted worker was bumped to 1.0.1 to stay in sync with the earlier API-key validation change, and dependency updates moved happy-dom to 21.0.4 and the zod 4 copies to 4.6.7. On the docs side, a full drift audit compared the live code against the live docs across API and specs, concepts and guides, SDKs, coding-agent plugins, framework tools and pricing. An AGENTS.md file was added at the repo root with instructions for coding agents, and the Mem0 migration guide now names that dashboard without linking it.

Week of October 12, 2026

What shipped

Why it matters

This week fixed several MCP and tools problems that made ordinary calls fail or time out, and tightened scope handling in the 2.x tools line. It also added Docker-based installation for Supermemory Local with upgrade guidance, and brought the v5 docs in line with what the API actually accepts. Users on both the server and the Python wrappers get fixes that previously required workarounds.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Supermemory this week: forget_memory by exact ID runs in about 0.5s instead of the 30s timeout, Local 0.0.9 ships prebuilt Docker images for amd64 and arm64, and tools 2.3.1 keeps containerTag inside the configured scope.

Post for LinkedIn

This week in Supermemory: forget_memory now forgets memories by exact ID taken from search_memory, running in about half a second on production instead of hitting the 30s timeout. Supermemory Local 0.0.9 is out with prebuilt Docker images for Linux amd64 and arm64, improved uploads, namespace operations and API v5 support. On the tools side, 2.3.1 backports a fix that keeps model-supplied containerTag inside the configured scope, 3.1.2 bundles 8 community fixes adapted to v5, and 3.1.0 makes ai an optional peer so apps on newer SDK releases avoid a duplicate copy. Docker installation and safe upgrade instructions are now in the docs, and the v5 docs were aligned with the API across ingestion, search, connectors and self-hosting.

Week of October 5, 2026

What shipped

Why it matters

This week the project moved onto the v5 API and supermemory 5.0, and the tools package went to 3.0 with no aliases, so call shapes and config change for integrations. The migration guide, versioned API reference and rewritten snippets exist so you can upgrade deterministically, and the wrapper cap keeps older installs working while they catch up.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Tools 3.0 and the server now run on v5, with the namespace as the first argument and a separate tool for removals. Old tool names come back as deprecated aliases so cached clients stop failing. Migration guide and versioned API reference are out.

Post for LinkedIn

This week the MCP server moved to the v5 API and supermemory 5.0, with the namespace as the first argument on every tool, and @supermemory/tools 3.0 brings every integration onto v5 while retiring @supermemory/ai-sdk. Removals now have a separate tool with its own schemas and destructive annotations, and the pre-snake_case tool names return as deprecated aliases so cached clients stop failing. The wrapper packages pin the Python SDK below 5 so existing installs keep working. On the docs side, a versioned v5 API reference, a migration guide and rewritten snippets across 50 pages support the upgrade.

Week of September 28, 2026

What shipped

Why it matters

This week brings security patches across the entire dependency stack, a new LiveKit integration for voice sessions, and significant documentation improvements. The disclosure of self-hosted security behavior and telemetry practices reflects commitment to transparency for operators deploying Supermemory.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Ship day: LiveKit voice agent memory, Better Auth security patch, advanced PDF extraction docs, and dependency security fixes across the stack.

Post for LinkedIn

This week we shipped persistent memory for LiveKit Agents voice sessions, security patches across the dependency stack including Better Auth 1.7.6, refreshed documentation design, improved team invitation workflow, and PostHog analytics instrumentation for better MCP observability. We also published transparency disclosures about self-hosted security behavior and documented advanced PDF extraction capabilities on Scale and Enterprise plans.

Week of September 14, 2026

What shipped

Why it matters

The memory graph got visual and performance improvements while the plugin ecosystem expanded with Muse Code documentation. Documentation accuracy received significant attention through billing updates and SEO fixes, and internal CI workflows were refined to prevent unintended automated actions.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: memory graph 0.2.4 with theme and layout fixes, MCP tools now using snake_case, and 35 doc redirects for stale URLs. Billing docs updated with Max plan details.

Post for LinkedIn

Weekly update: memory graph 0.2.4 shipped with theme restoration, automatic node settling, and improved initial layout. MCP tools refactored to snake_case naming and search_memory optimized to reduce unnecessary data fetching. Documentation expanded with Muse Code plugin guide, updated billing information for Max plan, and 35 redirects addressing stale URLs from GSC audit.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-09.

Is this your repo? Ask us to remove this page.