Workflow

Test every preview deployment with AI agents

Every pull request already gets a live preview. Almost nobody uses it before merging. Here is how to have agents use it for you, and leave what they hit on the pull request.

5 agents try to .

First test freeRun it from your coding agent

How do I test preview deployments automatically?

Trigger a check when the preview is ready (GitHub sends a deployment_status event for Vercel, Netlify and Cloudflare Pages), run it against the preview URL, and post the result on the pull request. The Mimiq preview check GitHub Action does exactly that: AI agents use the preview like users and one comment on the pull request says what broke, what the browser recorded, and where they got stuck.

The preview nobody opens

Reviewers read the diff, glance at the preview link, and merge. The preview is the only place the change runs with real hosting and real configuration before users see it, and it goes unused because using it properly takes time nobody has on every pull request.

Runs on deployment_status, when the preview is live.
Works with Vercel, Netlify and Cloudflare Pages previews.
One pull request comment, updated on every push.
Protected previews: a Vercel bypass secret or basic auth.
Optional: fail the check when agents give up.

How it works

01
Create a key
Free account, then Settings, "Create a key". Add it to the repository as the secret MIMIQ_API_KEY.
02
Add the workflow
One file, shown below. Set the goal to the task a user would try on most changes.
03
Open a pull request
When the preview is live, the agents run and the comment appears. Pushes update the same comment.

The workflow

The Action is open source at github.com/victorgulchenko/mimiq-preview-check. This is the whole setup:

on: deployment_status
permissions:
  pull-requests: write
jobs:
  mimiq:
    if: github.event.deployment_status.state == 'success'
    runs-on: ubuntu-latest
    steps:
      - uses: victorgulchenko/mimiq-preview-check@v1
        with:
          api-key: ${{ secrets.MIMIQ_API_KEY }}
          goal: Sign up and reach the dashboard
          people: 3

Protected previews

Vercel Deployment Protection blocks outside browsers. Pass your "Protection Bypass for Automation" secret as vercel-bypass-secret, or basic-auth-username and basic-auth-password for a password prompt, or login-email and login-password for a test account. They are sent for that run only and never appear in results.

Other CI

Anything that can send an HTTP request can run it: the MCP endpoint takes plain JSON-RPC.

curl -s https://mcp.mimiqai.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer $MIMIQ_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"mimiq.test_flow","arguments":{"url":"'"$PREVIEW_URL"'","goal":"Sign up and start using it","count":3}}}'

40steps at most for each agent, each in its own real browser. Every step comes with a screenshot and what the agent was thinking at the time.

20agents at once, each acting as a different one of your users. The browser also records every error, failed request and request slower than 3 seconds on your site, on the step it happened. Agents find problems; they do not forecast how many people will convert.

$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 agents. After that an agent uses 5 credits, and packs start at $9 for 120 credits.

See a sample report

Questions

Will it block merges?

Only if you want it to. fail-on defaults to never; set it to gave-up or stuck to fail the check.

How long does it add?

About 5 minutes for 3 agents, running in parallel with your other checks.

What does it cost per pull request?

5 credits an agent: 3 agents use 15. The Builder plan's 500 credits a month cover about 33 runs of 3.

Keep reading

Let the agents find what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-10-22.