Compare staging with production before a release

Text, layout and console differences page by page, with the ones that look like bugs marked.

  • You start it: When you start it

What it does

The task

Open each of these paths on staging at staging url and on production at production url: paths. Take a full-page screenshot of each, and compare the text, the layout, the images and the links. Read the console errors and failed requests on both. List the differences per page, and mark the ones that look like bugs, for example missing text, broken layout or new console errors. Do not submit forms or change data on production.

  • It works in any website and Google Docs, in the workspace you pick, and signs in with passwords from your Cuiar vault.
  • It runs once, when you start it.

What you give it

BlankWhat to giveExample
staging urlThe address of staginghttps://staging.brightleaf.app
production urlThe address of productionhttps://brightleaf.app
pathsThe paths to compare, separated by commas/, /pricing, /signup, /dashboard, /settings/billing, /help

What you get back

An example run with the example values above. Your run uses your own data.

6 pages compared, staging 2.5.0-rc1 against production 2.4.2

/ : New banner "XLSX export is here". Expected

/pricing : The yearly toggle is missing on staging. Looks like a bug

/signup : No difference

/dashboard : The chart legend covers the chart below 1280 px. Looks like a bug

/settings/billing : New field "Default currency". Expected

/help : 2 new console errors on staging: 404 for /static/help-search.js. Looks like a bug

Screenshots saved in the doc "Staging check 2.5.0-rc1".

Run it in Cuiar

  1. 01

    Open it

    Click Use in Cuiar on this page. The side panel opens with the task in the composer.

  2. 02

    Fill in 3 blanks

    Type staging url, production url and paths. Tab moves to the next blank.

  3. 03

    Run it

    Run sends it to the agent. Follow each step in the panel, and stop it at any time.

From the terminal

cuiar exec "Open each of these paths on staging at https://staging.brightleaf.app and on production at https://brightleaf.app: /, /pricing, /signup, /dashboard, /settings/billing, /help. Take a full-page screenshot of each, and compare the text, the layout, the images and the links. Read the console errors and failed requests on both. List the differences per page, and mark the ones that look like bugs, for example missing text, broken layout or new console errors. Do not submit forms or change data on production."

Run it from your AI agent

Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call run_task yourself.

1. Add Cuiar to Claude Code

claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp

2. Ask your agent

Use the Cuiar tool run_task to run my "Compare staging with production before a release" template with staging url = https://staging.brightleaf.app; production url = https://brightleaf.app; paths = /, /pricing, /signup, /dashboard, /settings/billing, /help.

Setup for other agents: AI agents.

The tool call

{
  "name": "run_task",
  "arguments": {
    "task": "Open each of these paths on staging at https://staging.brightleaf.app and on production at https://brightleaf.app: /, /pricing, /signup, /dashboard, /settings/billing, /help. Take a full-page screenshot of each, and compare the text, the layout, the images and the links. Read the console errors and failed requests on both. List the differences per page, and mark the ones that look like bugs, for example missing text, broken layout or new console errors. Do not submit forms or change data on production."
  }
}
All engineering templates