API changes.

API, server, and developer platform updates from Supermemory.

Agents can discover the API spec at /openapi.json#

The OpenAPI spec is now served from the conventional root path on both the API host and supermemory.ai, so an agent or crawler can find it without knowing the versioned URL.

Fixes

  • Unknown routes and thrown errors now return JSON error bodies instead of plain text, matching every other API response.

Both of these serve the live spec:

https://api.supermemory.ai/openapi.json
https://supermemory.ai/openapi.json

The versioned paths still work and are unchanged:

https://api.supermemory.ai/v3/openapi
https://api.supermemory.ai/v4/openapi

Automatic memory recall and a live statusline in Claude Code#

Supermemory now pulls relevant memories into every substantive prompt on its own, and the Claude Code status bar tells you what it did: how many memories it loaded, captured, and recalled this session, and how long ago it last saved.

Improvements

  • Connect to the hosted MCP server with an existing Supermemory API key instead of going through OAuth.

Fixes

  • Documents that have a usable summary no longer save with the title Untitled Document.

The status bar rotates through these, roughly every four seconds:

6 loaded · 6 captured · 2 recalls
saved 12s ago
recalled 3m ago

Backfill historical documents with documentDate on ingest#

Set documentDate on each document so historical content lands on the date it actually happened instead of the date you uploaded it, which is what makes time-based search work on backfilled data.

Improvements

  • A new guide walks through backfilling dated documents through the batch ingestion API, with TypeScript and Python examples.

Fixes

  • Fixed an issue where SDK responses dropped fields the API returned, across 15 endpoints.

Send up to 600 documents per request to POST /v3/documents/batch, sorted oldest to newest:

{
  "documents": [
    {
      "id": "msg-2019-04-02-118",
      "content": "Decided to move the billing cutover to Q3.",
      "documentDate": "2019-04-02T09:15:00Z"
    }
  ]
}

Without documentDate a backfilled document is dated the day you uploaded it, so a question like "what did we decide in 2019" will not find it.

Build custom tools on top of Company Brain#

Use an API key from the Supermemory app to build custom tools and workflows on top of your Company Brain.

Improvements

Fixes

  • Large API document lists no longer fail while loading memory relations.

Existing scoped API keys work with v4 conversations#

Scoped API keys that can add memories can now call the v4 conversations endpoint with the same container-tag and write-access protections as memory ingestion.

Improvement

  • Scoped API keys that can add memories now work with POST /v4/conversations, so conversation ingestion can be limited to approved container tags without requiring a full-access key.
  • Existing scoped keys with memory-ingestion access inherit the conversations endpoint automatically because conversations follow the same access rules as add.

Codex plugin routes memories into project Spaces#

Codex can organize captured work into custom memory containers and keep project Spaces named from the context it sees.

Improvements

  • Memories now show a temporary title while they are still being processed.

Fixes

  • Fixed conversations ingested from plugins being attributed to the API instead of their actual source.

Memory generation improvements and playground fixes#

Improvements

  • Memory generation now uses timestamps and recent history, so new information connects to related memories more accurately.

Fixes

  • Document processing now completes even when memory generation fails for part of a batch.

Usage-based API billing#

API billing now follows metered usage instead of relying only on fixed quotas.

Improvements

  • The file upload endpoint now accepts customId and entityContext, matching the memory add endpoint.
  • Usage analytics now report token usage per API key for tracking against plan limits.

Fixes

  • Fixed an issue where document metadata updates didn't appear in search results.

Mount memory as a local folder with SMFS#

SMFS mounts a Supermemory container as a local folder that shells, editors, and agents can use through ordinary file operations.

SMFS turns a Supermemory container into a folder tools already understand.

Fixes

  • Fixed PATCH document updates returning a 409 conflict against the document's own filepath.

Persistent memory plugin for OpenAI Codex#

Install the Codex plugin to recall project and user memory, capture completed sessions, and explicitly search or save context.

Improvements

  • OAuth clients can now discover Supermemory through /.well-known/openid-configuration.

Usage metering and Console onboarding fixes#

Fixes

  • Organizations with overages off now stop at their included allowance instead of recording billable usage.
  • Updating a document now counts only newly added content instead of re-counting unchanged text.

Test and tune memory search in the Console#

Run v3 or v4 searches, tune retrieval settings, and inspect scored results, timing, or raw JSON before integrating the API.

Improvements

  • Markdown documents now keep headings, tables, and fenced code together when split for indexing.

Fixes

  • New API keys now appear immediately in Console, and deleted scoped keys are removed completely.
  • Document processing now recovers from blocked generated output instead of failing memory generation.

Polish

  • API key previews now preserve the recognizable prefix and use a consistent masked length.

Organization reset and Console permission fixes#

Improvements

  • Owners and admins can reset an organization, clearing its data and connections while keeping members, billing, and the default project.

Fixes

  • Starting User Insights twice no longer creates competing runs or clears the active report.

User Insights: reports on user segments and content patterns#

Generate Console reports about user segments, knowledge domains, and content patterns, with an optional prompt to focus the analysis.

Fixes

  • You can now forget memories from a Console profile without getting a 404 error.
  • Usage emails no longer send the 80% warning after an organization has already reached its limit.

Video ingestion, Notion imports, and document processing fixes#

Fixes

  • API video ingestion no longer fails while extracting transcripts and descriptions.
  • Documents that produce large memory batches now finish processing instead of failing during memory generation.
  • Documents no longer fail when a generated memory references another memory that was filtered out.

Document ingestion reliability fixes and Nova improvements#

Improvements

  • During document ingestion, Supermemory can now generate up to three targeted searches to retrieve related existing memories as context.

Fixes

  • Documents no longer remain permanently stuck in processing after a workflow stops; Supermemory retries them once and marks a second failure clearly.
  • When scheduling a batch document upload fails, only the affected batch is marked failed instead of every queued document.
  • API and MCP quota errors now name the limit reached and explain how to continue with overage.
  • Truncated model output during ingestion no longer discards every generated memory when only relation data is incomplete.
  • Updating a document with the same custom ID no longer creates duplicate memories from facts already extracted.
  • Web links that return an authentication, paywall, or rate-limit response during metadata lookup no longer fail the entire import.
  • Search requests with an empty query or an out-of-range limit now return a clear client error instead of a server error.

Memory expiration fields, plus Nova, MCP, and plugin fixes#

Improvements

Fixes

  • Sign-up attempts with an unsupported email domain now return a clear rejection instead of a generic server error.
  • Usage limits now account for the full size of each request and allow continued processing when organization overage is enabled.
  • Nova no longer intermittently shows an Upgrade to Pro prompt on plugin and connection pages for users with an active paid plan.
  • MCP connections authenticated with an API key no longer fail with a missing-organization error.

Console documents page, scoped API keys, and connector fixes#

Improvements

Fixes

  • Console's API key list no longer crashes when an existing key has no metadata.
  • Deleting or merging container tags no longer reports a failure after the operation has already succeeded.
  • Google and Microsoft connections now keep syncing when new sign-in credentials replace the old ones.
  • Updating only a document's metadata no longer reprocesses unchanged content.

Plugin sign-in approval, Console and Nova fixes#

Improvements

  • Plugin sign-in now shows an approval page before returning an API key to the requesting app.

Fixes

  • Container tags containing URL-sensitive characters can now be viewed, updated, and deleted correctly in Console.
  • Console now shows clear not-found states for missing documents and container tags.

OpenClaw custom memory containers, plus API and Nova fixes#

Fixes

  • Document listing now returns documents matching any selected container tag instead of requiring every tag.
  • The API now returns a rate-limit error for throttled keys instead of reporting them as unauthorized.
  • v4 profile searches and search requests now record search-query usage correctly.
  • Large documents now finish processing instead of failing midway or timing out during summarization.