v0.9.3 — July 16, 2026

Release notes for Meko v0.9.3 — memory promotion, artifacts, retrieval quality, and sign-in improvements.

This page covers the Meko portal, API, and platform. For Installer, MCP server, and agent skills updates, see the Installer release notes.

LinkedIn sign-in and profile completion — Sign in with LinkedIn, then complete or verify the account profile when the identity provider does not supply all required fields. Federated identities also link to an existing account that shares the same verified email.
Knowledge-base upload visibility — Unprocessed S3 uploads appear in the knowledge-base dialog, and in-flight files are counted in the summary instead of showing zero during ingestion.
Google account chooser — Sign-in prompts for the Google account to use instead of silently reusing a prior selection.

Memory promotion — Owners and maintainers can promote selected private memories into the datapack's shared knowledge base via the memory_promote MCP tool.
Artifact storage — Agents can store and retrieve generated artifacts (artifact_put / artifact_get) in the per-datapack schema.
Server-side memory extraction — Posting a substantive conversation turn drives asynchronous memory extraction on the server, so agents no longer need a separate memory_add for every fact the user states.

Retrieval quality — The inference gateway no longer applies a similarity-score filter when a rerank score is present, and the gateway-side memory score filter was removed in favor of the prominence-based retrieval path.

Lifetime datapack cap — The free-tier datapack limit is gated on lifetime creations rather than only currently active datapacks.

Cross-user React Query cache — The client cache is cleared on login and logout so one session cannot retain another user's data.

Cloud MCP capture 403 — Installer-generated transports now send an explicit User-Agent, fixing WAF blocks against Cloud Meko. Cursor capture uses a synchronous SessionStart path.

Patched npm vulnerabilities across meko_ui, meko_admin, and docs, and Go module vulnerabilities in the backends.

Admin console, Token Burn / contextual prominence search, and AMP cluster management shipped behind feature flags in this window; they will not be enabled for all production users until later promotions.