Also in this release

MemHub + API
Features11
  • Routines can enrich themselves from the web while they run, with multi-query and adaptive depth.
  • Routines produce binary file deliverables and attach them to their email.
  • Artifacts expose a deliverable manifest, and deliverable content is extracted for semantic search.
  • Notion can be opted into per brain at context-session creation.
  • Skill bundles carry binary brand assets.
  • MCP serversearch_brains, search_all_brains, and get_brain_overview.
  • MCP serverdelete_skill and a refresh mode on add_skill_to_brain.
  • MCP server — gated deletes and refresh in chat, bringing it to parity with MCP.
  • APINew 2026-generation tiers, including Scale at $399, with per-org overage charging. Legacy customers are grandfathered.
  • APIProcedural recall is split out of /search into POST /v1/memories/trigger.
  • APIAsync ingest write path via SQS and Lambda.
Improvements6
  • Agent routines default to the chat runtime, and the content that triggered a run is injected as its focus.
  • Team-document originals moved off Vercel Blob to S3.
  • APIQuota and overage meter against the billing period rather than the calendar month.
  • APIBreaking: "recall" is renamed "search" across the customer-facing surface.
  • APIBreaking: X-Org-Id is dropped — the org is derived from the key.
  • APIThe ZeroEntropy reranker is removed from the team path.
Fixes3
  • Notion indexnotion_node.path binds as ltree again, fixing an asyncpg type mismatch.
  • Routines — the enrich deep→quick downgrade applies on edit; document trigger-focus is built from ordered chunks.
  • Artifacts — S3 bytes are garbage-collected on delete.
Security2
  • Developer keys — mem-manager keys validate against the data-plane memory API, and revocation is atomic.
  • APIRate limiting — valid API keys are no longer demoted into the unauthenticated 3/min bucket.