> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/testvibe-api/resources/roadmap-and-changelog.md).

# Roadmap & changelog

This handbook documents **current reality**. A few adjacent capabilities are planned but not built — listed here so you don't go looking for them in the reference.

## Roadmap

| Planned                                                           | Status                                                                                                                                   |
| ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **npm publish** of the `testvibe` package                         | Not yet — install from the repo (`npm i -g <repo>/cli`).                                                                                 |
| **Remote MCP with OAuth** (hosted MCP endpoint, no local install) | Planned. Today the MCP server runs locally over stdio with an API key.                                                                   |
| **Billing gate on dispatch**                                      | Usage is metered on every generation/run; hard credit enforcement at the API layer is coming. Don't build around the absence of a limit. |
| **Browser/exploration tools over the API**                        | The in-app assistant's sandboxed browser tools stay app-only for now.                                                                    |

{% hint style="info" %}
Additive changes (new fields, new routes) land inside `v1` without notice — write clients that ignore unknown fields. Breaking changes get a new version path.
{% endhint %}

## Changelog

### 2026-06-11 — suite runs, run diagnosis, project detail

* [`run_suite`](/testvibe-api/api-reference/runs/run_suite.md) (`POST /projects/{id}/runs`): dispatch several features — or every `generated` feature — in one call; `testvibe run --all --wait` is now the one-line CI gate.
* [`diagnose_run`](/testvibe-api/api-reference/runs/diagnose_run.md) (`GET /runs/{id}/diagnosis`): a failed run's failing tests, Gherkin, executed spec sources, artifact links, and log tail in one call.
* [`get_project`](/testvibe-api/api-reference/projects/get_project.md) (`GET /projects/{id}`): project detail incl. test site URLs; `testvibe project`.
* [`delete_file`](/testvibe-api/api-reference/files/delete_file.md) (`DELETE /files/content?path=`): remove stored files under the write allowlist; `testvibe files delete`.
* `status` filters on [`list_features`](/testvibe-api/api-reference/features/list_features.md) and [`list_runs`](/testvibe-api/api-reference/runs/list_runs.md).
* MCP tools now carry `readOnlyHint`/`destructiveHint` annotations; `run --wait` (single and `--all`) exits non-zero on failure.

### 2026-06-10 — v1 initial release

* `/api/v1/ops` API: projects, features CRUD, generation (dispatch/status/log/cancel), runs (dispatch/list/digest/artifacts), files, configs.
* API keys (`tvb_…`) in Settings → CLI & API keys, replacing the old CLI pairing flow.
* `testvibe` CLI and MCP stdio server (19 tools), sharing one manifest with the API.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/testvibe-api/resources/roadmap-and-changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.