API changes.

Faster memory search during embedding provider slowdowns #

Memory search now avoids long retry chains, so queries stay under 600 ms even when an upstream embedding provider slows down.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.