Report on the affected screen
The tester explains what they expected, what actually happened and any useful reproduction detail.
The closed repair loop
How Remedy turns a real software defect into a verified fix.
Six connected stages preserve the evidence, boundaries and decisions that ordinary AI code generation leaves behind.
Capture and sanitise context
Permitted diagnostic events, route and device context are attached. Sensitive keys and credentials are rejected.
Diagnose the likely cause
Remedy correlates the user report with technical context and identifies a focused failure hypothesis.
Prepare a bounded code repair
The connected coding agent receives only the relevant task, evidence and project repair rules.
Check, review and approve
Relevant tests and regression checks support human review before the team allows deployment.
Verify after deployment
Remedy rechecks the original reproduction path and closes the issue only when the result is verified.
A status trail everyone can understand
Reported. Diagnosing. Repair prepared. Awaiting approval. Deployed. Verified. Product, QA and engineering share one view of what has happened and what must happen next.
reported → context captured
diagnosing → cause isolated
repair_ready → checks passed
approved → deploy permitted
deployed → live version observed
verified → original defect resolved
diagnosing → cause isolated
repair_ready → checks passed
approved → deploy permitted
deployed → live version observed
verified → original defect resolved