Features/Understand and fix

Triage and Fix with Quanta

From “it’s broken” to a pull request.

Quanta turns a customer’s bug report into a draft pull request. It finds the root cause from the replay and logs, writes the smallest fix it can, and opens it on GitHub for your team to review. Nothing merges without a human.

Hire Rectify freeSee how it works
1 click
to a full triage report
Draft PR
opened on GitHub for review
0
merges without a human
1Bug report
Removing the last mood leaves the counter at 1

Sofia Marchetti · Fieldnote

ReplayConsoleNetworkSteps
2Triage with Quanta
HighP1

Root cause

Selected IDs not cleared on remove.

0%
3Fix with Quanta

› read MoodList.tsx

› edit selection.ts

✓ 1 file, +4 −1, $0.21

4Draft pull request
Draft
Quanta fix: Removing the last mood leaves the counter at 1

Waiting for your review

Review

A bug report comes in. Someone reproduces it, digs through the logs, finds the file, writes the fix and opens the pull request. That’s the afternoon gone.

Quanta does the digging. You do the review.

01

It starts with a real report.

A customer reports a bug from your widget. It arrives with a replay of what they did, console logs, network errors and the exact steps they took, so Quanta works from evidence, not guesses.

A session replay with its event timeline: page loads, clicks and errors
02

Triage with Quanta.

Any teammate, one click. Quanta reads the logs and the action timeline, looks at the screenshots and scans your connected GitHub repo, with progress shown live. Then it hands you a report.

  • Severity, priority and a plain summary
  • A root-cause guess with its confidence and the log lines behind it
  • The suspect files and functions, linked to GitHub
  • Steps to reproduce, and suggested fixes with code sketches
Triage reportReading logsReady

Removing the last mood leaves the counter at 1

Severity: HighPriority: P1Code change needed
Root cause

The row is removed, but the selected IDs are never cleared, so the header still counts one.

Confidence0%
Evidenceselection.size === 1 after onRemove(id)
Suspect files

src/components/MoodList.tsxonRemove()

src/state/selection.tsclearSelection()

Steps to reproduce
  1. Open Mood settings
  2. Add two moods, remove both
  3. The header still says “1 selected”
03

Fix with Quanta.

An admin confirms, and Quanta clones the repo, reads the suspect files and makes the smallest change it can. Every command it runs, the step count and the running cost are shown as it works. If a fix fails, it explains why in plain words and offers to retry.

Fix with Quantastep 1cost 0¢

› clone rectify/app, default branch

› read src/components/MoodList.tsx

› read src/state/selection.ts

› edit src/state/selection.ts +4 −1

- remove(id) { items.delete(id) }+ remove(id) {+ items.delete(id)+ selected.delete(id)+ }

✓ Fix ready. 1 file changed, 7 steps, $0.21

04

A draft PR, ready for review.

Rectify opens a draft pull request titled “Quanta fix:” with the triage summary, the root cause, what changed and a link back to the report, and your team gets a push notification. You review and merge as usual. Prefer your own editor? Pull the triage report into Cursor or Claude Code over MCP and fix it there.

DraftQuanta fix: Removing the last mood leaves the counter at 1

#214 · rectify/app · quanta/fix-mood-counter into main

Summary

Removing a mood now clears it from the selection, so the counter matches the list.

Root cause

remove() deleted the row but left its ID in the selected set.

What changed

src/state/selection.ts +4 −1

Reported by Sofia Marchetti, FieldnoteView the report in Rectify ↗
Waiting for your reviewReview changes
05

Guardrails, built in.

Quanta proposes; your team decides. Fixes stay small and focused, and every job cleans up after itself.

  • Draft pull requests only. Quanta never merges and never pushes to your default branch
  • Small, focused changes, and it never deletes files
  • The GitHub token is removed before Quanta starts, and your AI key stays out of its shell
  • Working files are deleted after every job. Your code is never stored
  • Runs on your own AI key, with the final cost shown on every fix
0

merges without a human

Draft PRs onlySmall changesNo stored codeYour own keyCost on every fix

Ask Quanta

Don’t click through it. Just ask.

Ask in plain English and Quanta does the work. Anything that changes your data waits for a person to approve it.

QuantaOn shift

Triage the Safari PDF bug.

Severity high. Likely cause (82% confidence): the blob URL is revoked before Safari opens it, in lib/invoice.ts, openPdf(). Steps to reproduce and two suggested fixes are attached.

Ask Quanta to do anything

Works well with

One workspace. It all connects.

Hear from usersBug reports and feedbackEvery report with a replay, logs and a diagnosisUnderstand and fixCode ScanBugs and vulnerabilities, before users find themUnderstand and fixQuantaThe AI teammate that knows your whole product
See every feature

Give your SaaS its first hire.

Hire Rectify freeSee pricing

Free for 14 days. Set up in about two minutes.