Catch the bug.
Keep the
context.
The “wait, did you see that?” recorder.
Capture what happened, choose what leaves your Mac, and give people—and agents—the whole story.
An interactive walkthrough. No download needed.
Human-approved context.
The save fails, but the board still says Done.
Error · task update failedYour Mac. Your call.
Try changing the evidence included in this example.
2 evidence types selected.
This is a demo. Nothing is recorded or uploaded.
A useful place to start.
Your review choices shape this illustrative handoff.
Investigate why moving this task to Done doesn’t persist. Start with the approved evidence.
LESS “CAN YOU REPRODUCE IT?”
A bug report.
With its story attached.
A recording shows the symptom. The right context makes it worth investigating.
- 01
Catch the moment.
A window, a region, or the whole display. Narrate the strange bit while it’s still in front of you.
Native macOS capture - 02
Choose the context.
Review the recording and optional evidence. Keep what helps. Leave the rest on your Mac.
Review before upload - 03
Pass the story on.
Share a replayable report with a person, or approved evidence with a read-only coding agent.
One clear starting point
Useful evidence.
Your permission.
CONTEXT WITHOUT THE OVERREACH
Your screen isn’t
an open book.
Neither is the rest of your Mac. Jammy puts a review step between capturing a bug and sharing its evidence.
Connected on purpose.
Diagnostics only from the browser tab, Electron app, or custom logger you explicitly connect and include.
Shared on your terms.
Choose the evidence before upload. Share with a revocable link, not a public media bucket.
Give your agent
a lead.
Not a hunch.
A vague prompt is a rough place to start. Let a coding agent inspect the finalized evidence you approved: context, events, transcripts, and reviewed frame samples when included.
Read the evidence. Respect the boundary.
No management access. No automatic fixes. Credentials expire and can be revoked.
Good context.
Meet your next investigator.
For existing Jammy owners connecting an MCP-compatible coding agent.
Copy the address, then configure your MCP client.
The endpoint alone doesn’t grant access. Create an expiring, read-only credential in the Mac app under Settings → Agent access. Keep the credential private; never use your owner token.
THE SMALL PRINT, HUMAN-SIZED
Good questions.
Here’s where things stand.
Can I download Jammy today?
Jammy is in private preview. There isn’t a public signed download or open signup yet. The interactive walkthrough on this page is available to everyone; it doesn’t record your screen or send any data.
What do I need to run it?
The native app requires macOS 15 or later and a configured Jammy backend. It can capture a display, window, or region, with optional microphone, system audio, and camera bubble. Screen and audio capture require the relevant macOS permissions.
What leaves my Mac?
Only the material you approve for upload. Review the recording, narration, device fields, diagnostics, and optional still-frame samples first. Diagnostics come from sources you explicitly connect and include, not every tab or app on your Mac.
Who can see a shared report?
A share link grants access to its report, so treat it like a key: anyone who has it can view the shared material. You can revoke the share. The report includes replay links that point to a specific moment, so you can send someone straight to the evidence.
Can an agent change or fix anything through Jammy?
No. Jammy’s MCP endpoint is read-only: it exposes finalized, reviewer-approved evidence for investigation. Create a separate, expiring agent credential in the Mac app and revoke it when you’re done. Jammy does not automatically fix a bug or prove that a fix works.
NEXT TIME SOMETHING GETS WEIRD
Make it a Jammy.
Private preview · macOS 15+