Memsy Studio — playground for memory creation
Type or paste text, drop in a documents, and watch it become memory. No SDK and no API key.
What shipped in Memsy — new capabilities, improvements, fixes and security updates, newest first.
Subscribe via RSSType or paste text, drop in a documents, and watch it become memory. No SDK and no API key.
Memsy now extracts and stores memories in 25 languages. 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 ingested through the connectors 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. Send neither and search covers everything, exactly as before.
New Actors tab in the Hierarchy page to view all actors along with their associated events and memories.
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.