Record the bug.
Start closer
to the fix.
Give your team more than a screen recording. Bring the selected logs, screenshots and context their AI tools need to help investigate.
Native Mac recorder · Browser-based review · MCP connectedBetter, together.
Your people. One place.
POST /api/invites312 msInvitation service unavailableFrom “look at this”
to “let’s investigate.”
One recording. Layers of useful context.
Better, together.
Your people. One place.
POST /api/invites312 msInvitation service unavailableWhy did the invitation fail?
The invite reached the server, then failed. At 00:24, POST /api/invites returned 500: “Invitation service unavailable.”
Next check: match this request to the invitation service logs. The underlying cause is still unconfirmed.
Illustrative response · synthetic evidenceIllustrative workflow. Debug sources need setup and selection. Your assistant proposes next steps; you decide what to investigate.
You saw the problem.
Help them see it too.
The clicks. The unexpected result. The error right beside it. Keep the useful pieces together, so your report gives the next person somewhere to start.
Explore debugging“The invitation should send.
Here’s what happened instead.”
POST /api/invites312 msInvitation service unavailableGive your agent
something to go on.
Connect a compatible assistant through MCP. Let it find the recording, inspect selected evidence, and help you reason about the next step—right where you work.
Explore the MCP workflowSet up your AI connection Read the connection guide
Why did the invitation fail?
The invite reached the server, then failed. At 00:24, POST /api/invites returned 500: “Invitation service unavailable.”
Next check: match this request to the invitation service logs. The underlying cause is still unconfirmed.
Illustrative response · synthetic evidenceGood context travels.
Reports developers
can work from.
Show the reproduction. Share selected evidence. Make the retest easy to review.
02 / EngineeringGet to the interesting
part sooner.
Inspect the failure with your team—or bring the evidence into your coding assistant.
03 / Support & clientsTurn “it’s broken”
into a useful handoff.
Let people show the issue. Give engineering a clear starting point.
Screen recording,
built for developers.
Thrume is a developer-focused screen recorder. Make Normal recordings for walkthroughs, or Debug recordings that keep selected logs and screenshots beside the video. Teammates watch in the browser, and authorized AI tools retrieve the evidence through MCP.
Normal recordings
Normal recordings capture your screen, microphone and an optional camera for walkthroughs, demos and updates.
Debug recordings
Debug recordings add the sources you connect and select: browser console and supported request metadata through the extension, logs from the Mac apps you choose, and log files and wrapped command output through the local bridge.
MCP access
MCP access lets authorized AI tools such as Cursor, VS Code, Codex, Claude Code and Claude retrieve recordings, screenshots, selected logs and available transcripts.
Plans from $9.99 a month billed yearly, per workspace. Every plan starts with a 30-day free trial.
Your voice.
Less of the room.
On-device voice enhancement helps clean up microphone noise after recording. Keep your explanation front and center, with optional Voice+ when you need it.
Meet audio enhancementNot every recording
starts with a bug.
Walk through a design. Explain a change. Share an update. Keep your private drafts, team projects and timestamped conversations in one place.
See how teams shareInvite flow · QA reviewTeam projectBetter, together.
Your people. One place.
Theo 00:24I’ll start with the captured request.
Choose what you capture.
Control what you share.
Selected sources
Choose the screen, microphone and debugging sources that belong in this recording.
Deliberate sharing
Review your draft. Choose your audience. Decide whether guest links include logs.
Authorized AI access
Approve the assistant you connect. Its access follows your permissions.
Before you
press record.
What is Thrume?
Thrume is a developer-focused screen recorder. Make Normal recordings for walkthroughs, or Debug recordings that keep selected logs and screenshots beside the video. Teammates watch in the browser, and authorized AI tools retrieve the evidence through MCP.
Who is Thrume for?
Thrume is for software teams: developers investigating bugs, QA testers who need reports developers can work from, and support or client teams escalating issues to engineering. Product and design teams use it for walkthroughs and reviews.
How much does Thrume cost?
Team is $12.99 a month, or $9.99 a month billed yearly ($119.88 a year), with 25 GB of shared storage. Team Plus is $29.99 a month, or $19.99 a month billed yearly ($239.88 a year), with 100 GB of shared storage. Debug Pro is $74.99 a month, or $49.99 a month billed yearly ($599.88 a year), with 500 GB of shared storage. Prices are per workspace, not per person, in US dollars, and exclude any applicable taxes. Every plan includes Normal and Debug recordings and MCP access, and starts with a 30-day free trial. See pricing.
How is Thrume different from other screen recorders?
Most screen recorders stop at the video. Thrume can keep the selected logs and screenshots with the recording, and lets your AI tools retrieve that evidence through MCP. Read how Thrume compares.
Who can use Thrume?
Anyone. Sign up free with your email address; once you confirm it, your workspace is ready with 25 GB of storage. To join an existing workspace, ask its owner for an invitation.
Which computers can record?
Thrume records on a Mac with macOS 15 or later. Authorized teammates and guests can watch in a browser without installing the recorder.
Does every recording capture logs?
No. Use Debug mode and explicitly connect and select the relevant sources before recording. Normal mode is for straightforward screen recordings.
Do I need AI to use Thrume?
No. Recording, sharing and inspecting captured evidence work without an external assistant. MCP gives compatible AI tools an additional way to retrieve evidence you authorize.
Can an agent fix the bug from a recording?
It can use available evidence to help investigate and propose changes in its own environment. A recording is a starting point, not proof of a root cause or a guarantee of a correct fix.
How do I connect my assistant?
Add the remote MCP server in a compatible client, sign in and approve workspace access. Start with the MCP connection guide.
Make your next recording
the start of a solution.
For the people who find the issue.
And the people who work out what to do next.
Maya 00:24Expected the invite to send. This is where it fails.