reviewed: Claude OpusTo engineering in one action
A conversation becomes a ticket without retyping it, evidence and all.
pasting a chat transcript into a ticketSolutions · Bug fixes
From a vague reportto a reviewable fix.
The report arrives with the replay, console and network trail. Tore reads your code, finds the cause, writes the fix with tests and waits for your engineer's approval. Then it tells everyone who reported it.
Tore opens soon. Join the waitlist and we'll email you the day you can start.
app.tore.ai/beacon-data/TCK-519
Example data Example: Priya reports "Checkout is broken" from the chat widget. The report arrives with the pinned element, a screenshot, the last 30 seconds replayed, and console and network attached. Tore investigates: it reads the stack frame and the commit that last touched the code, merges four matching reports into one ticket, and the report becomes "Coupon field clears the cart total on Safari 17", traced to coupon.ts line 212. Tore writes a fix with 112 of 112 tests passing, including one new test, and prepares pull request 519. It waits for Alex, the engineer, who approves it. After the deploy, Priya and three others who reported it are told, and the linked Linear issue closes.
You stop beingthe reproduction step.
The slow parts of every bug, the back-and-forth, the copying between tabs and the follow-up email, happen without anyone doing them by hand.
Forty reports, one piece of work
Repeating reports of the same bug merge into one ticket.
closing duplicates one by oneSupport and engineering, same work
Linked Linear and Jira issues stay in sync, so nothing is tracked twice.
"is this the same as the Jira one?"Reporters hear back
Everyone who reported it is told when the fix is live, without anyone remembering to.
a customer who thinks you ignored themFollow one bug,from report to "it's fixed".
The report
It arrives with the evidence attached.
Your customers report bugs from the chat widget inside your product, with tools that capture what happened. Nobody asks which browser they were on.
- Pin the broken element, or screenshot it and circle the problem
- One-click screen recording, or replay the last 30 seconds
- Console, network, browser and OS attached automatically
- Secrets stripped before upload, and the customer is told
widget · report a bug
Example dataReport a bugin Beacon App
Pin element Screenshot Record Last 30s Console
pinnedbutton "Apply coupon"
browserSafari 17.4 · macOS 14
consoleTypeError: total is undefined
networkPOST /api/cart/coupon · 200
secrets2 tokens stripped · Priya told
The investigation
It reads your code, not just the ticket.
Tore follows the evidence into the repository you connect: the stack frame, the commit that last touched those lines, the files around them. It shows what it looked at, so you can check its reasoning.
- Reads your live repository, not a stale snapshot
- Root cause down to the file and line
- Repeating reports merged into one ticket
- Matches the customer's report to the error event
investigation · TCK-519
Example dataread TypeError at coupon.ts:212
matched Sentry event BEACON-4F2 · 31 events
last change: commit a3f9c1e "cart: async totals"
read 6 files · applyCoupon has 2 call sites
Safari resolves the promise after render
4 reports merged into TCK-519Root cause: the total is read before it is awaited, coupon.ts:212.
The fix
A tested change your engineer can steer.
Tore writes the fix, runs your tests and adds one for this bug. A second model reviews it before your engineer is asked. Your engineer can approve it, request changes in plain words, or take it over.
- Fix, tests and a new regression test
- A second model reviews the fix first
- Request changes and Tore revises it and re-runs the tests
- By default it waits for your engineer's approval
PR #519 · review
Example datacheckout/coupon.ts+3 −1
212- const total = cart.total;
212+ const total = await cart.getTotal();
213+ if (total == null) return keepTotal();
112/112 tests · 1 newreviewed by a second model
Alex requested changesGood catch. Use the existing keepTotal helper in cart.ts instead of a new one.
revised · tests re-run 112/112
ApproveRequest changesTake it over
After it ships
Everyone who reported it hears back.
The ticket stays linked to your Linear or Jira issue the whole way. When the fix is live, Tore tells every customer who reported the bug, in the conversation they started.
- Linked Linear and Jira issues kept in sync
- Reporters told automatically when their fix is live
- Everyone who reported the same bug hears back, not just the first
TCK-519 · activity
Example data
BEA-88 · Coupon clears cart totallinked to TCK-519 · Beacon Web
syncedAlex approved PR #519
deployed v2.4.3 · BEA-88 Done
Tore to Priyain her original conversation · 10:53
Fixed. Coupons now keep your cart total on Safari. Thanks for the recording, it showed us exactly where it broke.
Also told: 3 others who reported itTune it
What to fix high severity and upAutonomy beacon/web: draft the pull requestTell reporters after deploy
5capture tools in the widget: pin, screenshot, recording, replay, console
1ticket for every report of the same bug
2models on every fix: one writes, one reviews
6risk classes always sent to a person
Keep exploring.
Stop chasing reports.Start approving fixes.
Add the widget and connect a repository. The next bug arrives with its evidence, and leaves as a tested change.