Hover/changelog← HomeDocs中文
Changelog

What’s new in Hover.

Everything user-visible we’ve shipped across Cloud, the VS Code extension, the MCP, and the engine. The per-commit detail lives in the repo changelogs.

  1. · @hover-dev 0.48 · hover-dev 0.44MCPVS Code

    Four test types, one suite — all deterministic

    • Hover now crystallizes not just end-to-end flows and API contracts, but Visual regression (screenshot baselines) and Accessibility (axe-core WCAG scans) too. Every type is a plain Playwright spec that runs in your CI with no AI at run time — pixel diffs and rule engines, not a model second-guessing your UI.
    • Specs are organized under __vibe_tests__/{e2e,visual,api,a11y}/, and the Business Map marks each type at a glance. Add the two new types from your agent with crystallize_visual_spec / crystallize_a11y_spec.
  2. · @hover-dev/mcp 0.46 · CloudCloudMCP

    Every failed CI test gets a reasoned verdict — drift vs bug

    • When a spec goes red, Hover Cloud now weighs real evidence — the code diff since the last green run, the failing page, and your business rules — to call it drift (the UI changed, heal the test) or a bug (fix the app, the test caught it). It cites what it found, so the verdict is checkable, not a vibe.
    • Failures that share one broken control are grouped into a single verdict — five specs dying on the same renamed button become one call, not five guesses. Deterministic evidence (the diff, the page) decides for free where it can; a model only fills the gaps, and abstains when it truly can’t tell.
    • Declaring a guard now auto-records its acceptance criteria as your app’s rules, so the verdict always has your stated intent to score against — no extra step.
  3. · @hover-dev/mcp 0.43 · hover-dev 0.40 · CloudMCPVS CodeCloud

    Test accounts follow you to any machine

    • Opt in to sync a test account to Hover Cloud when you set its password (or push them all with one command). Values are encrypted at rest; syncing is always a choice, never a default.
    • The MCP resolves credentials through a chain: local env → .hover/.env → your project’s Cloud-synced accounts. A fresh machine or a teammate just signs in and the agent can log in — no manual export, and the secret still never enters the model’s context.
  4. · @hover-dev/mcp 0.42MCP

    Test-account logins without the agent ever seeing the password

    • fill_control now takes valueFromEnv: the agent names the credential variable (HOVER_USER_PASS), the Hover server types the real value from your exported .hover/.env. The secret never enters the model’s context, and nothing sensitive echoes back.
    • If an agent types a variable name or a process.env expression as the literal value (a real failure we hit), Hover resolves it instead of typing it; if the variable isn’t set, it refuses to type anything and says how to fix it.
  5. · @hover-dev/mcp 0.41MCP

    The Hover command menu speaks your language

    • Install in Chinese and the /mcp__hover__* commands (ask, heal, lint, guard, build, and the rest) now show their titles and descriptions in Chinese right in the slash-command menu — not just the agent’s replies. Set via HOVER_LANG; more languages to follow.
  6. · @hover-dev 0.40 · hover-dev 0.39MCPVS Code

    The business map gains an API layer

    • When the agent locks an API contract (status, shape, authz per endpoint), it now lands on the business map under an API section — so the map shows both what users do and what the app promises over the wire, each colored by its latest run.
    • API lines wear a shield in the map graph and render as hexagons in the Mermaid export. One glance answers: which endpoints are contract-locked, and which routes still run bare.
  7. · hover-dev 0.38VS Code

    Share the business map anywhere — Copy as Mermaid

    • One button copies your business map as a Mermaid flowchart. Paste it into a README, a PR description, or a doc — GitHub renders it natively, so teammates without Hover see the app’s flows and their test coverage: green passing, red failing, dashed not covered.
    • Export-only: the map file in your repo stays the source of truth, kept honest by your CI.
  8. · @hover-dev/mcp 0.37–0.39MCP

    Verify moves into the loop — seconds per turn, and a "no green, no done" gate

    • New verify_specs tool: after your agent edits code, it replays the affected flows against the live app in seconds (fast mode), and runs the real spec files with the same engine CI uses before a push (faithful mode). Structured pass/fail per flow, with the exact broken step.
    • The /build workflow now climbs that ladder every round: fast check each edit, faithful check before the push, CI as the authority. Local green means "worth pushing" — CI still owns the verdict.
    • hover-hook install --gate turns the Stop hook into a finish gate: when the agent tries to say "done", Hover replays your crystallized flows first — any red blocks the finish with the exact list. Fail-open on setup gaps, so it never wedges a session.
    • Setup mistakes now stop with the fix instead of silently going wrong: an unreachable app, missing login credentials, or a missing CI ingest token each get a one-line diagnosis. And a replay bug that typed a literal env expression into login fields is fixed.
  9. · hover-dev 0.37 · @hover-dev/mcp 0.36 · CloudVS CodeMCPCloud

    Connect a repo to Cloud from the editor — and map big apps in parallel

    • Signed in, the VS Code panel now knows whether the current repo is actually a Cloud project. If it isn’t, a Create project button opens Cloud pre-selected to that repo — connecting a repo no longer means hunting for it in a list.
    • Mapping a large app is faster: the map-the-business-lines phase is pure code-reading, so your agent can now split the codebase by area and map it in parallel with its own sub-agents (recording specs stays sequential — one real browser, exact replay).
    • Cloud: org-owned repos now appear in the new-project picker (via GitHub App installations), and team invites are link-only — copy a link, no dependency on email delivery.
  10. · @hover-dev/mcp 0.35MCP

    Hover in the agent loop — Claude Code hooks

    • New `hover-hook install` wires Hover into Claude Code’s hooks: your agent starts each session oriented (which Cloud project + environment, and any specs that drifted in CI), gets nudged toward /mcp__hover__guard when a prompt looks like new behavior, and sees a .hover health check at the end of a turn.
    • The hooks run Hover’s deterministic checks (no AI) — tightening the inner dev loop while keeping the green path AI-free.
  11. · @hover-dev 0.34 · CloudMCPCloud

    Your agent knows its Hover Cloud — who, which project, which environment

    • New cloud_context MCP tool: signed in, your agent can orient in one call — who it’s connected as, whether this repo is a Cloud project (with its environments + URLs + test accounts), and which environment is active in the editor (what a test/heal targets).
    • The heal queue and run verdicts now carry each environment’s URL, so the agent heals or builds against the right deployment (staging vs prod) — no guessing, no extra lookup.
  12. · Cloud · @hover-dev/mcp 0.33CloudMCP

    Guard-first development: define the behavior, ship the code, keep the regression

    • /mcp__hover__guard turns a feature intent into a declared contract before any code exists: business rules anchored to a business line, plus a pending line on the map with acceptance criteria. No fabricated tests — the spec is still recorded from the real flow.
    • /mcp__hover__build drives it to green: implement, verify each criterion in the live app, crystallize, push, then read Hover Cloud’s per-failure verdicts (bug → fix the code; drift → heal the outdated test; unclear → ask you) and iterate. Merging stays yours.
    • A judge now scores ambiguous failures against your stated rules (advisory, auditable), and the new /api/v1/runs endpoint gives agents the verdicts programmatically.
  13. · hover-dev 0.36 · @hover-dev 0.32VS CodeMCPCloud

    One environment-aware panel — sign in, pick an environment, test

    • The VS Code extension is now a single panel with tabs — Overview, Heal, Environments, Map — instead of three separate views. It works signed out (local-first); signing in (approve in the browser) unlocks Cloud CI runs and the heal queue.
    • A first-run wizard walks you from optional sign-in to choosing your test environment (Local, a deployed URL, or import from Cloud). The run target, the Remote view, the heal queue, and the agent’s test/heal drive are all scoped to that active environment.
    • The Hover MCP now follows the environment you activated in the editor — it targets that URL and logs in with its credentials during test and heal, instead of a fixed localhost.
    • Accidentally removing an environment or account now offers Undo — restored with its saved passwords.
  14. · Cloud · @hover-dev/mcp 0.31CloudMCP

    Your business rules, on the map — a living, tested spec

    • The Business Map now shows the rules Hover learned about your app (from .hover/memory/ in your repo), grouped under the business line each one governs, with an app-wide section. Structure (what’s covered) and meaning (how it behaves) in one view.
    • Each rule shows when it was learned and the commit that recorded it — the git history is the knowledge history. And when a failing spec’s line had a recent rule change, the heal queue flags it: likely an intentional change, not a bug.
    • The agent (MCP 0.30) now anchors each rule to its business line as it records it, and asks about the invisible rules up front on a first run.
    • A new Knowledge timeline shows how that knowledge evolved — every rule added, changed, or removed, straight from your repo’s git history.
    • Hover now keeps your repo’s .gitignore set up to commit the knowledge base and ignore working files — no hand-editing (opt out with HOVER_NO_GITIGNORE).
  15. · CloudCloud

    Failure screenshots + a bilingual dashboard

    • Failed specs on the run page now show their Playwright screenshot inline — pulled on demand from your CI run’s artifact on GitHub; Cloud stores no image bytes.
    • The dashboard speaks 中文: switch the display language under Settings → Language.
  16. · CloudCloud

    Drift or bug? The queue now knows — and asks when it doesn’t

    • Every CI failure is triaged by its shape: drift (an action lost its target — heal the test), bug (the app itself failed — fix the app), or a middle state awaiting your verdict when an assertion failure could be either. Healing away a real bug is the one thing a self-heal system must never do.
    • Drift entries copy a one-click heal command for your agent; bug entries copy a paste-ready regression report — failed flow, error, environment, commit, cross-run history as evidence, and a deterministic repro command (the spec itself).
  17. · CloudCloud

    PR verdicts in business language

    • Merge confidence on every failed PR run: each failure is classified pre-existing / flaky / regression from its cross-run history, with the reason shown per spec — so you know whether the red is yours before you dig. Deterministic, never a model’s guess.
    • A business-coverage section on PR comments: which business lines went red in this run, and which uncovered lines this PR looks related to — each with a ready authoring command for your agent.
  18. · @hover-dev/mcp 0.29MCP

    The agent now interviews you about your business

    • On a first test_app run, Hover presents the business map it drafted and asks — in one message — for priorities, invisible rules (which features need login? paywalls? is this a safe test environment?), and corrections. Confirmed rules land in your repo’s knowledge base.
    • Rules the app itself demonstrates (a /login redirect, a quota message) are recorded without asking — the knowledge base compounds every run instead of staying empty.
  19. · Cloud · hover-dev 0.32CloudVS Code

    GitHub App + one-click editor sign-in

    • Connect your repos through a GitHub App — access is scoped per-repo, approvable by an org admin, and the token never expires (no more re-signing-in when a session lapses).
    • Connect your editor to Hover Cloud by approving a short code in the browser — nothing to copy or paste.
    • Every CI run now writes a hover/e2e status back onto your pull request, deep-linked to the run in Cloud.
  20. · Cloud (beta)Cloud

    Hover Cloud, in free early-access beta

    • Connect a GitHub repo and Cloud writes the CI workflow, wires the reporting secrets, and gives you a Run now button — your specs execute on your own Actions minutes, Cloud runs no browsers.
    • Dashboards for pass / fail / flaky, trends, a heal queue, and a business-coverage flow graph — all computed from your ingested CI runs.
    • Multiple environments (staging, production): the same specs pointed at deployed URLs, with test logins wired in without leaking secrets. Scheduled monitoring and regression alerts by email + Slack.
    • Self-heal orchestration: Cloud detects a drifted spec and routes a heal to your editor — the fix stays local and human-reviewed, and closes only when CI sees the spec pass again.
  21. · hover-dev 0.26–0.28VS CodeMCP

    Self-heal in CI + the Hover Cloud pull channel

    • Your editor and MCP poll the Cloud heal queue and notify you when a spec drifts in CI — nothing in the cloud drives your machine; it hands `/mcp__hover__heal` to your own agent.
    • The generated CI can dispatch a drift-heal back to the editor, and — opt-in — open a Claude auto-heal PR.
    • Stronger generated workflows: sharding, scheduled monitoring, concurrency, and a run summary. Plus optimize-all, one-command promote, and HOVER_LANG (converse in your language).
  22. Site

    Cloud-first site relaunch + bilingual docs

    • A light, green editorial rebrand and a Cloud-first funnel, with English + 中文 across the landing page and the docs.
    • A full Hover Cloud onboarding section in the docs — connect a repo, environments, runs, self-heal, connect your editor, team & lifecycle.
  23. · hover-dev 0.24MCP

    A test wiki that compounds

    • Hover keeps a living map of your app’s business lines and the relationships between them, plus a run-history log — so the agent recalls what it already learned instead of re-discovering it each run.
    • Ask the wiki with a `/ask` prompt; a state-aware test_app knows whether it’s bootstrapping a suite or extending one.
  24. · hover-dev 0.21–0.23EngineMCP

    Page Objects + agent-driven optimize

    • Hover detects flows shared across specs and lifts them into Page Objects, folding the specs onto them — cleaner, DRY test code you own.
    • An agent-driven `/optimize` refines a spec against your project’s conventions; the deterministic spec stays the source of truth and you review the diff.
  25. · hover-dev 0.24VS Code

    Self-heal a broken spec in chat

    • When a saved spec breaks because the app changed, click 🏥 Heal — Hover re-runs the flow against your live app, re-locates the broken step with grounded selectors, and offers a fixed candidate to review. It never silently rewrites a spec.
    • The Dashboard flags each spec that’s flaky across runs and puts a Heal action on its row.
  26. · hover-dev 0.22VS Code

    QA Testing mode — autonomous exploration

    • Point QA at a page (or just say “test the app”) and the agent systematically exercises controls, tries negative / boundary inputs, and writes a findings report. Intensity presets bound a run by step count so “explore everything” can’t run away on cost.
    • API-testing and penetration-testing toggles layer real-traffic checks and an origin-locked, own-app security pass onto a QA run.
  27. · hover-dev 0.19VS CodeEngine

    Bring your own model (BYOK)

    • Model settings are a Local CLI ↔ BYOK switch: run on a detected coding-agent CLI, or supply your own key + base URL for Anthropic / OpenAI / Azure / Gemini or an OpenAI-compatible gateway. Keys live in VS Code SecretStorage.