Skip to content

Hand each fix to your coding agent, with the screens attached.

Variantly doesn’t change your code. Every issue you act on becomes a fix brief: what to change, where, and what the recheck will look for. Your agent, or a person with a pull request, makes the change; the recheck shows whether it landed.

Fix brief · issue 1Redrawn example
Where: /app/team, #invite-flash (removed after 3000 ms; no role="status")
Change: render the message in <div role="status">;
         remove the 3000 ms timeout; keep a Dismiss button.
Recheck: message present at step 6; transcript includes
         "Invitation sent to sam@demo-target.test."

What leaves Variantly.

A fix brief hands your coding agent what the live product showed, not only the code: the task, the attempt, and a link to each screen it cites. It is plain text, so any tool that reads text can use it.

Copy a fix brief

Each issue you act on gets one block: what to change, where, what the recheck looks for, and the evidence. Paste it into your agent’s prompt.

See a fix brief

Connect the MCP server

List a product’s issues and read each with its evidence.

Import recordings, download reports

Import recordings from Chrome Recorder or Playwright. Download the conformance report as DOCX (the ITI template), OpenACR, PDF, or HTML.

How to import

Run it from your coding agent.

Connected through your account, your agent can describe a task, start a review and ask for a recheck without leaving the editor. A person still decides each issue.

Set up Claude Code, Cursor or Codex

Claude Code

claude mcp add --transport http variantly https://mcp.variantly.app/api/mcp

Where your agent fits in the loop.

A recheck says what it saw on the deployed product, not that a commit landed.

  1. Decide

    A person decides to act on the issue.

  2. Change

    Your agent reads the fix brief and the capture, and opens a pull request.

  3. Deploy

    The change reaches staging or production.

  4. Recheck

    The same task runs again from the same perspective and looks for what you intended. It records what it saw.

Start with what you meant.

Start with a public URL. Arrange signed-in or private access separately. No static design files.

We use these details to reply about the review.