For the complete documentation index, see llms.txt. This page is also available as Markdown.

Roadmap & changelog

Where the API is headed, and what changed when.

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

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.

Additive changes (new fields, new routes) land inside v1 without notice — write clients that ignore unknown fields. Breaking changes get a new version path.

Changelog

2026-07-17 — npm publish

  • The CLI/MCP package is live on the public npm registry as testvibenpm install -g testvibe (unscoped; @testvibe/cli was never published). The server-hosted curl | sh / iwr | iex installers remain as the npm-free path.

2026-07-06 — telemetry read surface

  • Telemetry: get_live_servers, list_error_groups, list_server_metrics — read the app's live server vitals (CPU/memory/sessions), fingerprinted application-error groups, and a load run's persisted server samples from CI or an agent; testvibe telemetry live|errors|metrics. The ingest side stays the drop-in telemetry agent / TestVibe.Telemetry package.

  • 3 new operations across the API, CLI, and MCP server.

2026-07-06 — load test authoring

  • Load testing: create_load_test, update_load_test, delete_load_test — author load tests from CI or an agent (simple mode replays functional journeys, advanced drives k6 against paths), edit their configuration, and delete them; testvibe load create|update|delete …. Listing and dispatching (list_load_tests / run_load_test) already shipped.

  • 3 new operations across the API, CLI, and MCP server.

2026-07-06 — plugin management, variables & secrets

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

  • run_suite (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 (GET /runs/{id}/diagnosis): a failed run's failing tests, Gherkin, executed spec sources, artifact links, and log tail in one call.

  • get_project (GET /projects/{id}): project detail incl. test site URLs; testvibe project.

  • delete_file (DELETE /files/content?path=): remove stored files under the write allowlist; testvibe files delete.

  • status filters on list_features and list_runs.

  • 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.

Last updated

Was this helpful?