What supermemoryai/supermemory shipped
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
Week of October 5, 2026
What shipped
- @supermemory/tools 3.0 now calls the v5 API across every integration and retires @supermemory/ai-sdk, with config taking one namespace. Pull request #1773
- The server now runs on the v5 API and supermemory 5.0, with the namespace as the first argument on every tool. Pull request #1783
- Pre-snake_case tool names return as deprecated aliases so cached clients stop failing on the old names. Pull request #1782
- Removal requests now have a separate tool with its own schemas and destructive safety annotations. Pull request #1790
- The agent framework integration is prepared for 2.0.0 on the Python SDK. Pull request #1786
- The memory graph adds opt-in stacked nodes and emphasized connections, so the console no longer carries a patch. Pull request #1792
- Wrapper packages now cap the Python SDK below 5 so existing installs keep calling the 3.x API. Pull request #1774
- The docs add a versioned v5 API reference with legacy and latest versions organized by workflow. Pull request #1690
- A migration guide documents every migrated workflow, request and response change, filter conversion and rollout step. Pull request #1691
- SDK snippets across 50 pages move to the shipped v5 call shape and the namespace rename is finished. Pull request #1772
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
- @supermemory/tools 3.0 calls the v5 API across every integration and retires @supermemory/ai-sdk; config takes one namespace. Pull request #1773
- The MCP server moves to the v5 API and supermemory 5.0 with the namespace as the first argument. Pull request #1783
- Pre-snake_case tool names are kept as deprecated aliases for clients with a cached tool list. Pull request #1782
- Removal requests have a separate tool with its own description, schemas and destructive annotations. Pull request #1790
- The agent framework integration is prepared for 2.0.0 on the Python SDK. Pull request #1786
- Wrapper packages pin the Python SDK below 5 and bump patch versions. Pull request #1774
- The memory graph gains opt-in stacked nodes and emphasized connections. Pull request #1792
- Docs add a versioned v5 API reference with legacy and latest versions. Pull request #1690
- Docs add a V3/V4 to V5 migration guide. Pull request #1691
- SDK snippets across 50 pages move to the shipped v5 call shape. Pull request #1772
- A one-line migrate tip appears on every v5 entry point. Pull request #1779
- Docs cover the paginated v5 namespace list and both delete outcomes. Pull request #1769
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.
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
- Added supermemory-livekit, a Python plugin that gives LiveKit Agents voice sessions persistent memory by loading caller profiles and related memories before each reply. Pull request #1702
- Published documentation disclosing that server-v0.0.8 binds all interfaces with unsafe implicit local authentication and warns operators against exposing it to untrusted networks. Pull request #1711
- Upgraded Better Auth to patched version 1.7.6 and applied root dependency security changes. Pull request #1719
- Patched root workspace security vulnerabilities including Next 16.3.3, Drizzle 0.45.2, Vite 7.3.5 and related packages. Pull request #1724
- Fixed out-of-credits error messaging to direct users to the billing console and prevented these errors from inflating error rates. Pull request #1753
- Refreshed documentation design to use console design tokens including Geist, neutral greys, updated radii and borders in light and dark mode. Pull request #1715
- Added team invitation guide documenting how to invite team members with role and access choices. Pull request #1754
- Instrumented MCP server with PostHog analytics sending only allowlisted metadata with personless user IDs and disabled schema injection. Pull request #1712
- Documented advanced PDF extraction availability on Scale and Enterprise plans including page-by-page OCR and automatic tier selection. Pull request #1728
- Enabled conversation ids in PostHog MCP tool calls to group related calls instead of creating separate sessions for each call. Pull request #1718
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
- Feat(livekit): add persistent memory for LiveKit Agents Pull request #1702
- Docs: disclose current self-hosted security and telemetry behavior Pull request #1711
- Fix(auth): upgrade Better Auth to patched 1.7.6 Pull request #1719
- Fix(deps): patch root workspace security vulnerabilities Pull request #1724
- Fix(mcp): clear out-of-credits error and keep it out of error rate Pull request #1753
- Docs: refresh the documentation design Pull request #1715
- Docs: add team invitation guide with console screenshots Pull request #1754
- Feat(mcp): instrument server with metadata-only PostHog analytics Pull request #1712
- Docs: explain advanced PDF extraction availability Pull request #1728
- Feat(mcp): group PostHog MCP tool calls by conversation id Pull request #1718
- Fix(docs): remove vulnerable ZIP extractor and patch tar via Mintlify Pull request #1727
- Fix: docs icons in dark mode Pull request #1735
Ship day: LiveKit voice agent memory, Better Auth security patch, advanced PDF extraction docs, and dependency security fixes across the stack.
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
- Memory graph 0.2.4 released with fixes for theme rendering, initial node layout, and settling behavior. Pull request #1686
- Public MCP tools now use
snake_casenaming, andsearch_memoryno longer fetches full profile data on every call. Pull request #1665 - Billing and Gmail documentation updated to reflect Max plan ($100/month with $130 in monthly credits) and correct feature availability across plans. Pull request #1685
- Muse Code plugin documentation added, covering marketplace install, file-based auth, lifecycle hooks, and MCP tools. Pull request #1674
- Added 35 documentation redirects for stale URLs identified in Google Search Console Pages report. Pull request #1673
- Graph styling restored with configurable dots, and incoming nodes now automatically settle and fit without manual intervention. Pull request #1684
- Eve integration guide added and integration icons refreshed with updated plugin ordering. Pull request #1671
- CI auto-fix workflow now restricted to same-repository pull requests from human actors. Pull request #1663
- Documentation build process now runs on isolated Node 22 runtime for local development compatibility. Pull request #1692
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
- Memory graph 0.2.4 released with theme fixes, initial node fit, and node settling improvements Pull request #1686
- MCP public tools now use
snake_casenaming;search_memoryreturns memories only, profile data moved toget_profilePull request #1665 - Billing and Gmail documentation updated to reflect Max plan and current feature entitlements Pull request #1685
- Muse Code plugin documentation added with marketplace install, auth, lifecycle hooks, and MCP tools Pull request #1674
- 35 documentation redirects added for stale /docs URLs Pull request #1673
- Graph console theme and dots restored; incoming nodes automatically settle and fit Pull request #1684
- Eve integration guide added; integration icons refreshed and plugin order updated Pull request #1671
- CI auto-fix workflow restricted to same-repository pull requests from human actors Pull request #1663
- Documentation development now runs on isolated Node 22 runtime Pull request #1692
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.
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.