What's new

Highlights from recent releases on each of Meko's two tracks. For the full history, see the Changelog.

Meko portal and platform — v0.9.5–v0.9.6

• Track usage against your plan — a dedicated Usage page shows live consumed versus plan limits for datapacks, conversations, workbench tokens, knowledge-base storage, and MCP memory and search activity.
• Find generated files and follow indexing progress — each datapack now has an Artifacts page, while knowledge-base files show their progress from queued through ready.
• See what Meko saves you — contextual prominence search is live in production. The Datapacks overview and each datapack detail page show the context reduction from unified retrieval across conversation, memory, and knowledge base, with a per-model estimate of the resulting cost savings.
• Conversation-embedding quotas — conversation search and embedding usage is governed by plan-tier quotas as the conversation-search rollout continues.
• Claude Desktop recall works on plain questions — the Meko skill now activates for simple recall prompts, and adding messages to a conversation from Claude Desktop no longer errors.
• AMP cluster tools, opt-in — cluster, branch, and compute management tools are available behind an early-access flag, prefixed with amp_.

Installer, MCP server, and skills — v2.1.0

• Cross-agent reads work as expected — memory_search, memory_get_all, and conversation_list span all of your agent namespaces within a datapack, so agents no longer fan out one search per agent.
• Production is the default for fresh installs — with no existing Meko configuration and no --url, the installer points at https://mcp.mekodata.ai/mcp.
• A tighter 23-tool surface — experimental conversation-search tools stay hidden unless you enable them, and the remaining tool contracts are more precise.
• A self-contained skills plugin — behavioral skills, hooks, and connector metadata ship as a complete Claude Code plugin from yugabyte/meko-skills.
• Memory promotion asks first — promoting to team memory previews the exact memories, explains visibility, and requires explicit confirmation.
• Capture failures stay visible — quota and HTTP 402/403 failures no longer advance the capture watermark, so the next session reports the problem instead of silently skipping turns.

Keep up