API keys can no longer create organizations
Creating an organization now requires a signed-in user. Requests made with an API key get a 403 error.
What shipped in Memsy — new capabilities, improvements, fixes and security updates, newest first.
Subscribe via RSSCreating an organization now requires a signed-in user. Requests made with an API key get a 403 error.
AI agents with an AgentMail inbox can sign in to the Memsy console with AgentID. Each agent gets its own account, and its owner is recorded.
When Memsy grouped related memories, some details on the group could be lost. New groups now keep every field.
Some users saw an "Application error" page right after signing in to the console. That's fixed.
The console now opens on a Home dashboard with widgets for your memory insights and a Studio drop-in.
Every event and memory now records where it came from, such as a connector, Studio or the API. Filter by source on the Memories, Events and Search pages, or pass a source filter in search requests.
Free tiers now include one member seat. Admins can invite a teammate and try working together before upgrading
Ready-to-run recipes for a Next.js chat app, a FastAPI support agent, a Slack bot, and memory as an agent tool.
The Claude Code plugin can limit a search to the current conversation or skip it, and files each turn under the right conversation, including after /clear.
Type or paste text, drop in a documents, and watch it become memory. No SDK and no API key.
Cancelling at the provider's sign-in page returns you to the console instead of an error, and retrying Connect no longer ends in "Connector not found". The API also stays available during large document syncs.
Connectors set up with an API key or the SDK showed as active but never ingested anything. They now sync like ones created in the console.
Closest matches now rank first. A scoring bug had pushed exact matches down, and broad sub-queries could outrank your actual question.
Memories extracted from non-English content are now stored in the original language instead of being translated. Mixed-language content is handled as written.
The S3 connector now supports AWS SSO sign-in along with the pre-existing access keys login.
Events from Slack, GitHub, Google Drive, OneDrive, Notion, and S3 buckets connected with SSO now record the author's email in their metadata, so you can trace a memory back to the person whose content produced it.
Search can now be limited to a single conversation, or told to skip one, including documents from your connectors. Send neither and search covers everything, as before. Available in the Python and Node SDKs (0.3.5).
A background job had cleared the search data for some memories, so search could miss them. This is fixed, affected memories are restored, and new memories keep their search data from the moment they're saved.
Replies like "Thanks." or "Got it." are no longer saved as memories, and memories keep their links to the events they came from.
Relevance scores now stay between 0 and 1, so the threshold option filters results as documented.
New Actors tab on the Hierarchy page lists every actor in your organization with their events and memories. Also available in the Python and Node SDKs (0.3.5) and the MCP server.
Memory and stats queries in the console are now paginated, so organizations with large memory counts load instead of timing out.
Reads and idempotent writes to the vector store now retry on transient faults, so a brief backend blip no longer surfaces as a failed request.
Context-window lookups now require a session id. Previously a request without one could return results drawn from other sessions in the same organization.
The promotion graph, which shows how individual memories were consolidated, is now available on the Free tier rather than Pro and above.
Reranking has a latency cap, so a slow provider can no longer stall a search, and is enabled for Pro, Growth and Enterprise plans.
Content security policy now allows the authentication scripts served from our own domain, fixing a blank sign-in screen for some users.
The connectors section is now shown unless explicitly disabled. Previously a deployment that did not set the flag hid it behind a "coming soon" badge with no indication anything was wrong.
An admin without an assigned seat was refused access to their own organization. Seat assignment is no longer required to administer it.
The bot-protection challenge on sign-up was blocked by content security policy, which could prevent account creation entirely.
Connect a GitHub organization and sync repository content into memory.
Connect OneDrive and pick specific folders or files to sync, rather than syncing an entire drive.
Connect a Notion workspace and sync pages into memory.
Connect an S3 bucket, scoped to your organization, and sync its documents into memory.
Connect Google Drive and sync documents into memory.
See how memories were clustered and promoted for your organization, with per-cluster detail.
Connect one Slack workspace per organization. Connection status is visible to members, not just admins.