Where do I get the API key?

Settings → Agents & API Access → Create API Key. The same key works for the MCP server and any /api/v1/* call.

Does the extension require an internet connection?

It needs to reach your Lastest instance. If you self-host inside a private network, the extension works as long as VS Code can resolve the Lastest URL.

Can I run a single test?

Yes - right-click any test in the explorer or use the lastest.runTest command palette entry.

Does the extension support multiple projects?

Yes. Connect once per workspace; the extension picks the repository whose remote matches the connected Lastest project.

How do I review a visual diff inside VS Code?

Use lastest.openInBrowser to jump to the diff card in the Lastest UI. Native in-editor diff view ships in a future release.

IDE

Run, watch, and review tests without leaving VS Code

A first-party VS Code extension surfaces your full Lastest instance in the Activity Bar - test tree by functional area, status bar build counts, and live SSE updates. Authenticated with the same Bearer token your MCP server and CI use.

Try Lastest free →Read the docs

What you get

Three things this integration does - and what they mean for your team.

Test Explorer

Tree view of every test grouped by functional area, with status icons (passing, failing, new). Click a test to view details inline; right-click for run, edit, and "open in browser."

Status bar + commands

Live build status and counts in the bottom-right. Five commands: refreshTests, runTest, runAllTests, openInBrowser, connect - bind any of them to a keyboard shortcut.

Real-time SSE

The extension subscribes to /api/v1/events. Build status changes, test completions, and runner status updates push instantly - no polling, no stale view.

How it works

Data flow, configuration, and result routing - visualised.

Diagram 1 · Extension architecture

How the VS Code extension talks to Lastest

The extension uses /api/v1/* over HTTPS for CRUD and /api/v1/events over SSE for live updates. Same Bearer token used for MCP and CI works here - issue from Settings → Agents & API Access.

Diagram 2 · Test explorer + status bar

What you actually see in the editor

Tests grouped by functional area in the Activity Bar. Status bar shows build counts. Inline notifications surface diff approvals and runner failures.

Diagram 3 · SSE event flow

Live updates without polling

Server pushes build status changes, test completion events, and runner status updates over Server-Sent Events. The extension updates icons and counts instantly.

Configure

Drop-in config for VS Code

VS Code keybinding to run all Lastest tests

{
  "key": "ctrl+alt+l",
  "command": "lastest.runAllTests",
  "when": "editorTextFocus"
}

Frequently asked questions about Lastest + VS Code

Where do I get the API key?: Settings → Agents & API Access → Create API Key. The same key works for the MCP server and any /api/v1/* call.
Does the extension require an internet connection?: It needs to reach your Lastest instance. If you self-host inside a private network, the extension works as long as VS Code can resolve the Lastest URL.
Can I run a single test?: Yes - right-click any test in the explorer or use the lastest.runTest command palette entry.
Does the extension support multiple projects?: Yes. Connect once per workspace; the extension picks the repository whose remote matches the connected Lastest project.
How do I review a visual diff inside VS Code?: Use lastest.openInBrowser to jump to the diff card in the Lastest UI. Native in-editor diff view ships in a future release.

Other integrations