Verify a Fix Without Redeploying

Scenario

You just changed some code to fix a bug that showed up as a failing request. Before committing, you want proof it's actually fixed — without manually re-triggering the original client action (submitting a form, calling the mobile app, waiting for a webhook) and without redeploying anywhere.

Steps

Find the original failing request and note its ID:

laurel-proxy requests --failed --format table
  METHOD  STATUS  HOST                          PATH                          TIME      SIZE
  ──────────────────────────────────────────────────────────────────────────────────────────────
  POST    422     api.example.com               /v1/orders                   84ms      212B

  1 total (showing 1, offset 0)

Look up the full request to get its ID:

laurel-proxy requests --failed --format json

Apply your fix locally, then replay the exact same captured request against your fixed server with --diff:

laurel-proxy replay req_8f3a2c1b --diff

replay <id> re-sends the captured request — same method, headers, and body — to the same URL. The --diff flag compares the new response against the response that was originally captured and reports whether the request is now improved, regressed,changed, or unchanged.

Example output:

  DIFF: POST https://api.example.com/v1/orders
  status:  422 -> 201 [CHANGED]
  body:    [CHANGED]

  result: improved

If you need to test a variation — a different header, body, or URL — override just that piece without needing the full original request:

laurel-proxy replay req_8f3a2c1b --body '{"quantity": 2}' --diff

Exit codes make this scriptable: replay --diff exits 0 when the replayed response is 2xx, and 1 when it's 4xx/5xx — so you can wire it into a pre-commit check or CI step.

With Your AI Agent

With the AI Agent Plugin, let your agent close the loop after making a fix:

You: "I think I fixed the 422 on /v1/orders. Verify it."

Your agent runs: laurel-proxy replay req_8f3a2c1b --diff
The agent reads the result field, confirms status changed from 422 to
201, and reports back that the fix is verified.

Your agent can chain this straight after applying a fix it made itself — find the failing request, patch the code, replay with --diff, and confirm before telling you it's done.

← Find Slow EndpointsShare as cURL →