---
title: "v2.5.0 - October 21, 2026"
url: "https://docs.mekodata.ai/changelog/installer/v2.5.0/"
---

# v2.5.0 - October 21, 2026

Release notes for installer and public skills plugin v2.5.0 - browser sign-in, automatic capture repair, and datapack search.

This release covers version 2.5.0 of the `@yugabytedb/meko-mcp` installer and the public Meko agent skills plugin. Installer 2.5.0 is the release after 2.3.0. Installer 2.3.1 and 2.4.0 were not published. The public plugin 2.4.0 was published on October 15, 2026, including Kiro power 1.1.0. The capture fixes prepared for installer 2.3.1 are in this release.

Published skill versions: `meko-mcp-tools` 3.4.0, `meko-mcp-tools-desktop` 2.11.0, `meko-select-datapack` 1.2.1, `meko-select-datapack-desktop` 1.3.1, and Kiro power 1.2.0.

## Install or upgrade

```bash
npx @yugabytedb/meko-mcp@2.5.0
```

In a terminal, with no `--api-key` and no `MEKO_API_KEY`, the installer opens your browser and creates an API key. See [Before you connect](/integrations/connect-to-ai-agent/#before-you-connect).

Claude Desktop can also install the MCP server from [meko-2.5.0.mcpb](/downloads/meko-2.5.0.mcpb). That file installs the MCP server only. It still asks you to paste an API key, and it doesn't install the Desktop skills. See [Claude Desktop](/integrations/connect-to-ai-agent/#desktop-extension).

Claude Code users can also [update the skills plugin directly](/integrations/connect-to-ai-agent/#updating-the-skills-plugin). That update does not install capture repair or the Claude Code status line. Rerun the installer for those.

The public plugin source is in [`yugabyte/meko-skills`](https://github.com/yugabyte/meko-skills).

## Changes

### New features

- **Browser sign-in** - In a terminal, a Cloud install with no `--api-key` and no `MEKO_API_KEY` creates an API key for you. A command that includes `--url` opens the browser. A command with no `--url` asks you to choose **Sign in with browser** or **Paste an API key**. Sign in with the same method you use for the Meko portal. The new key is named `Meko installer (<computer>) <time>`, counts toward your 10 active keys, and expires after one year. Manage it under **Settings > API Keys**. `--no-browser` prints the sign-in URL instead of opening a browser. A run with no terminal attached, such as CI, still requires a key. `--yes` in a terminal still signs in through the browser. The **Connect** dialog still shows a command that includes `--api-key`.
- **Automatic capture repair** - While an agent session is open, its capture timer runs `--capture-cleanup fix` about every 30 minutes, one run at a time. It sends at most 100 exchanges per run and stops early when the server is failing. When one session is rejected for an API key, a plan limit, or datapack access, other sessions with the same cause are left paused for that run. `--capture-cleanup stop` pauses retries and stops a repair that is already running. `--no-autofix` turns repair off for every client. `--autofix` turns it back on. A later install that passes neither flag keeps the saved choice.
- **Claude Code status line** - When the installer sets up Claude Code's status line, it shows what capture needs. Examples: `capture: needs you (API key)`, `capture: paused (5 queued)`, `capture: retrying (12 queued), auto-fix at 14:30`, `capture: sending 7`, and `capture: auto-fixed 3`. Healthy capture shows nothing. `auto-fixed` disappears about an hour after that run. An interactive install asks whether to show the Meko datapack in the status line and defaults to yes. A one-liner that passes `--url` does not add the status line unless you also pass `--statusline` or `--yes`. Updating only the skills plugin shows no capture text. A status line from an older installer keeps `capture:catching_up(N)`, `capture:degraded(N)`, or `capture:blocked(N)` until you rerun the installer.
- **`--capture-cleanup fix`** - One command repairs stuck capture. It clears leftover failure fields, sends a backlog, or moves unsent turns to a new conversation when the old one cannot be served. It does not move a session that is still open. A bad API key, a plan limit, or a datapack problem is reported for you to fix, and that session stays paused until the next `fix`. `npx @yugabytedb/meko-mcp@latest --capture-cleanup status` shows the last repair run.
- **Datapack search in the selector** - `meko-select-datapack` 1.2.1 and `meko-select-datapack-desktop` 1.3.1 show 10 datapacks at a time, newest first. Reply with a number to pin that row, part of a name to search, or `next` / `prev` to change pages. On a server that has no `datapack_search`, they fall back to listing datapacks.

### Improvements

- **Knowledge-base upload in the skills** - `meko-mcp-tools` 3.4.0 and `meko-mcp-tools-desktop` 2.11.0 ask you to confirm the file and the datapack before an upload, because the file goes into the shared knowledge base. An agent that has the file then calls `knowledgebase_upload_document` and checks `knowledgebase_document_status`. An agent that cannot send the file points you at the portal upload.
- **Kiro power 1.2.0** - The public Kiro power tells the agent how to find a datapack and how to add a knowledge-base file.
- **Installer datapack lookup** - When the server lists `datapack_search`, `--migrate --datapack <name>` and the install canary use it. An older server still uses `datapack_list`.

### Fixes

- **A viewer datapack holds capture** - A conversation write on a datapack where you are a viewer returns `read_only_access`. Capture holds that session and reports it at the next session start, instead of retrying every few minutes. `--capture-cleanup fix` reports it as a datapack problem. See [What a viewer can do](/architecture/core-concepts/manage-access/#what-a-viewer-can-do).
- **Failed turns retry when they are due** - A failed send is retried as soon as its retry time arrives, instead of waiting for the next 10-minute checkpoint. This applies to Claude Code, Cursor, Codex, Kiro, and OpenCode.
- **OpenCode picks up a new URL or API key** - After you reinstall or change the key, the next capture attempt uses the new values. You don't have to wait for an old capture process to exit.
- **OpenCode's first install can take longer** - The first OpenCode run after install may spend up to 2 minutes installing its plugin before config resolves. The installer says why it is waiting.

### Known limitations

- OpenCode support covers CLI and TUI 1.18.x. It doesn't cover OpenCode Desktop, V2 preview APIs, headless or remote sessions, or child-session migration.
- OpenCode capture stores visible user text and the first visible assistant message. It doesn't store tool calls, hidden reasoning, files, attachments, or streaming output. It uses your account's default datapack and doesn't read the pin. `--datapack` applies to `--migrate` only.
- Browser sign-in needs a terminal. The Desktop extension (`meko-2.5.0.mcpb`) does not create a key.
- The **Connect** dialog command still includes `--api-key <paste-your-api-key>`.
- Claude Desktop has no session hooks, so automatic capture still depends on the model even with the skills installed.