Hover/docs
EN中文
← HomeGitHub

Connect your editor

Cloud can route heal requests and CI results back into your editor — but nothing in the cloud can reach into your machine, so the connection is a pull: your VS Code extension and MCP agent authenticate to Cloud and poll. One sign-in covers both.

Connect from VS Code

In VS Code with the Hover extension installed, run Hover: Connect Hover Cloud. This uses a device-link flow — no token to copy:

  1. The extension opens your browser at the Cloud approval page with a short code.
  2. You're already signed in, so you check the code matches and click Approve.
  3. Cloud mints a personal access token and hands it back to the extension exactly once.

The token is saved to ~/.hover/credentials.json (mode 0600), not VS Code's private secret storage — because the Hover MCP server reads the same file, so approving in the editor signs in your MCP agent too.

Prefer to paste a token?

If the browser approval doesn't complete (air-gapped browser, self-hosted Cloud without the approval page), the flow falls back to pasting a token you mint at Settings → API tokens.

What the editor does with it

Once connected, the extension polls the heal queue every few minutes. When a spec drifts in CI, it notifies you and offers Copy heal command — that puts /mcp__hover__heal <spec> on your clipboard for your coding agent. You review the diff; the queue entry closes when CI sees the spec pass again.

The extension's Dashboard panel can also read your project's Cloud dashboard directly (the same pass/fail/flaky data the web app shows), so CI results land in the cockpit without touching a file.

Connect the MCP directly

The MCP server resolves credentials in a fixed chain, so any agent using @hover-dev/mcp picks up the same sign-in:

  1. HOVER_CLOUD_TOKEN (and optional HOVER_CLOUD_URL) environment variables — explicit, good for CI or headless agents.
  2. ~/.hover/credentials.json — written by the VS Code connect flow above, or by hand.

With credentials present, the cloud_failures MCP tool pulls the open heal queue so your agent can work drift straight from the failure hint Cloud extracted.

Minting a token by hand

Under Settings → API tokens on Cloud you can mint a personal access token (hover_pat_…), shown once. Put it in HOVER_CLOUD_TOKEN or the credentials file. Revoke it any time from the same page.

What's next