A verification queue for coding agents.

Writing code scales to dozens of agents. Verifying it on one laptop doesn't.

Run fifteen sessions and they all finish around the same time. Each one starts a stack to check its work, and they collide over ports, databases and memory. Worktrees separate your files, not any of that.

Moving to the cloud gives up the fast feedback of working locally. verifique keeps verification on your laptop, and runs only what your laptop can carry.

One short file

Your agent writes it.

Run verifique init and give the guide to your coding agent. It works out what two copies of your app would fight over and writes this file.

Then verifique doctor proves it: two copies side by side, each using its own data. Your framework doesn't matter. Your database servers just need to be running already.

services:
  postgres: {}
  redis: {}

stacks:
  web:
    prepare: [pnpm install, pnpm build]
    seed: pnpm db:seed
    env:
      DATABASE_URL: "{postgres.url}"
      REDIS_URL: "{redis.url}"
    apps:
      web:
        run: pnpm start
        port: 3500
        ready: /
        env: { PORT: "{port}" }

checks:
  e2e: { stack: web, slots: 2, run: pnpm test:e2e }
  manual: { stack: web, type: agent, agent: claude }

Proof

An agent shouldn't mark its own homework.

• Judged against your words. The checker gets your request and the diff, not just the author's summary.
• No proof, no pass. A pass needs its steps, what it saw and an evidence file.
• Crashes never pass. A check that dies can't read as success.
• Tied to the content. Commit the same files later and the verdict still holds.
• Clean every time. Databases are created, seeded and dropped for each check.
• It knows when to stop. Three failures in a row and the branch comes to you.

job 6: failed on storefront
check   manual
content afa3d3034  commit 511d73986

Google Fonts fetching was correctly removed, but only
weights 300, 400 and 900 are wired into the bundled font.

steps
  - Read the diff
  - Signed in as the setup step instructed
  - Inspected all network requests
  - Parsed the served CSS for @font-face rules
  - Queried document.fonts in the live page
  - Saved a screenshot of the dashboard

saw: exactly three @font-face rules for roboto, at 300,
400 and 900. The 500 and 700 files exist but are never
referenced.

not checked: a pixel comparison against a build from
before the change.

files   ~/.verifique/jobs/6