thrume.
For developers

Start at the failure.
Get to the next check.

A vague report leaves you rebuilding someone else’s session before you can debug it. Thrume brings the recorded steps, the marked failure and selected logs together, ready to inspect yourself or with your coding agent.

Request beta access Follow the workflow
Context, carried into the code

Begin where
the evidence begins.

Watch a vague report become a focused investigation brief in an authorized assistant.

01 / Understand

See the failure before you form a theory.

Replay what the reporter saw. The steps, the visible error and their explanation give you the shape of the issue before you open a file.

Spend your attention on the problem, not recreating the report.
02 / Retrieve

Bring the evidence to your assistant.

An authorized MCP connection lets your compatible assistant retrieve recording context and captured evidence. Start the conversation with the actual moment.

Less copying screenshots and pasting logs between tools.
03 / Investigate

Turn context into a better next check.

Ask what the evidence proves, what is still missing and where to investigate next. Your assistant can help work on the code in its own environment; you review the reasoning and the change.

A grounded starting point for engineering judgment.
Incoming reportTeam invitation
THE REPORT YOU RECEIVED
“Inviting a teammate
is broken again.”
Failed team invitationScreen recording · marked at 00:24
00:42

“I open Team, enter the email, and click Send invitation. This is where I expect confirmation.”

Seen at 00:24Invitation could not be sent.
Your assistant / Authorized MCPIllustrative retrieval
ASK ABOUT THE ACTUAL MOMENT

“Inspect the failed invitation
around 00:24.”

01
Find the recording

Failed team invitation · 00:42

02
Inspect captured evidence

Screenshot + selected browser events

SOURCE / BROWSER · 00:24POST /api/invitesHTTP 500

The request failed at the visible error.

Your assistant / Investigation briefIllustrative response
EVIDENCE FIRST. THEN A HYPOTHESIS.

The request failed.
Now trace its error path.

Observed

Screen error and HTTP 500 at 00:24.
Source: recording + browser evidence

Still unknown

What caused the server to return 500.

NEXT CHECK

Inspect the invitation handler and its server logs. Reproduce the request, then test any proposed change.

Your environment. Your review. Your decision.
Synthetic example, not a live AI response or a verified fix. MCP retrieves authorized evidence that exists in the recording. External assistants operate in their own environments under their own policies; Thrume does not confirm causes or apply code changes.
The value of a better handoff

Better context.
Better first questions.

Thrume connects what happened on someone’s screen with the evidence your team captured. Keep the investigation in the tools where you already think and build.

Explore MCP & AI toolsConnect your assistant
Put it to work

A workflow
your team can use.

Read the practical guide
Follow the issue across the work on your Mac.

Reproduce the browser action with the relevant local app, log file or wrapped command connected and selected in Debug mode. Keep those timestamped events with the screen recording, so the visible failure and nearby events travel together.

Give your coding agent the evidence to inspect.

Connect your assistant through MCP and ask about the marked failure. Let it retrieve screenshots and selected events, identify observed errors and propose the next diagnostic checks. Keep the source references as you test the explanation against your code.

Leave the next developer a clear way in.

Record a tricky edge case, explain a change or show what you have already checked. Share the recording with the team and keep follow-up questions on its timeline. The next person can pick up the investigation when they are ready.

Public beta · Approval required

Bring your next
handoff into focus.

Start with a recording. Give the next person the context to move forward.

Request beta access