██████╗ ███████╗ ███████╗ ██████╗ ██╗ ██╗ ██╗ ███████╗ ██╔══██╗ ██╔════╝ ██╔════╝ ██╔═══██╗ ██║ ██║ ██║ ██╔════╝ ██████╔╝ █████╗ ███████╗ ██║ ██║ ██║ ██║ ██║ █████╗ ██╔══██╗ ██╔══╝ ╚════██║ ██║ ██║ ██║ ██║ ██║ ██╔══╝ ██║ ██║ ███████╗ ███████║ ╚██████╔╝ ███████╗╚██████╔╝ ███████╗ ╚═╝ ╚═╝ ╚══════╝ ╚══════╝ ╚═════╝ ╚══════╝ ╚═════╝ ╚══════╝

Detect. Reproduce. Fix. Ship.
From CI to production.

Resolue autonomously detects software issues — from failing tests to production errors — reproduces them, generates a fix, and opens a PR with proof.

Get Early Access ↓ Learn how it works →

⇅ fix-checkout-timing ⎇ /fix/checkout-await Open ▾

PR #248 ↗ Ready to merge ⇄ Merge

⌂Home

CI FailuresCI

⇅ checkout-timing

+12-3

fix/checkout-await · Ready to merge ⌘1

⇅ nav-redirect

+6-1

Reproducing... ⌘2

Production ErrorsSentry

▲ TypeError #4821

+4-1

342 users affected ⌘3

▲ Null ref #4819

Fix verified ⌘4

AlertsDatadog

◆ API latency spike

Investigating... ⌘5

TicketsLinear

◈ ENG-1204

Form submit broken ⌘6

☰◫⚙

⊕ All issues

Fixing CheckoutError

TypeError #4821

⟳

▸ 8 tool calls, 4 messages

📋 🔍 📎 📤

I've reproduced the failure and identified the root cause. The router.push() call in cart.tsx is missing an await, causing a race condition where the checkout page renders before navigation completes. Let me apply the fix and verify:

▸ 1 file changed src/pages/cart.tsx

+4-1

Verification complete. All 3 originally failing tests now pass. Full suite: 147/147 tests pass. Production error rate on this route: 0 new occurrences since deploy.

▸ 15 tool calls, 13 messages

📋 🔍 📎 📤

Resolution Summary

Issue resolved across CI and production. Regression test generated.

What Changed:

Added await to router.push() — Navigation was firing async, causing checkout to mount before route transition completed.
Generated regression test — New test in checkout.spec.ts verifies the async navigation flow to prevent recurrence.
Sentry issue #4821 auto-linked — Same root cause. Marked as resolved with fix commit reference.

GPT-4o-mini

Ask Resolue to investigate further...⌘L to focus

📎 ↑

Changes5

All files

Review🔍

src/pages/cart.tsx

+4-1

☐

src/components/CheckoutRedirect.tsx

+22-0

☐

src/utils/navigation.ts

+8-3

☐

tests/checkout.spec.ts

+18-0

☐

tests/regression/nav-async.spec.ts

+34-0

☐

⌄ Run

Terminal

▶ Run ⌘R

→ fix/checkout-await git:(fix-checkout-timing) █

Resolution sources

One engine. Every signal.
From test failure to production incident.

⚡

CI Pipeline

Playwright, Cypress, or any integration test failure triggers automatic reproduction and fix generation.

v1.0

▲

Sentry

Production exceptions are ingested, reproduced locally using breadcrumbs, and fixed with auto-generated regression tests.

v1.0

◆

Datadog

APM traces, error rate spikes, and synthetic test failures trigger investigation and patching.

v1.0

◈

Linear / Jira

Bug tickets with reproduction steps are picked up, verified, and fixed automatically. Engineers review the PR.

v1.5

⊙

GitHub Issues

Community-reported bugs with error logs or screenshots are triaged, reproduced, and resolved.

v1.5

⬡

Manual Trigger

Paste an error URL, stack trace, or test name. Resolue investigates on demand.

v1.0

How it works

Connect your stack. GitHub, Sentry, Datadog, Linear — Resolue listens to all your error sources.

Issue detected. Resolue wakes up. CI failure, production exception, or bug ticket — each gets an isolated Docker worker.

Reproduce. Investigate. Patch. Browser agent explores your app. LLM diagnoses root cause. Minimal diff generated.

Review the PR. Fix, root cause, regression test, evidence screenshots, and preview URL — all in one PR.

Detect. Reproduce. Fix. Ship.From CI to production.

Every bug. Every source. Resolved.

Detect. Reproduce. Fix. Ship.
From CI to production.