Context that attaches itself
Viewers open the Figma file, Linear issue, or GitHub path you had on screen.
The context follows the video
Shoyu attaches the app, page, file, and command behind each moment. Jump to a layer.
Where the work happened
Shoyu notes the window title of every app you bring forward while you record. For apps it recognises, it also adds a link to the same file or page, so viewers can follow along.
- A moment for every switchEach app you bring forward lands on the timeline at the second you switched to it.
- Direct links for Figma, Linear, and NotionRead from their local app data on your Mac. Never the document itself.
- Your team decidesApp Identity is a Policy switch for owners and admins, on by default.
What the page did
The browser extension follows the active tab’s navigation and titles by default. Deep Context adds console error markers and network request metadata. It runs only when you switch it on for that recording, and only while the tab shows “Shoyu Capturing”.
- Page titles and addressesShoyu drops the query string and #fragment unless your organization keeps full addresses.
- Deep Context for one tabConsole error markers and network request metadata, for one recording. Only four basic headers are kept.
- A network log to downloadYour team can download a Deep Context recording’s network log as a HAR file, with no bodies or cookies.
- BrowserNavigationCheckout — step 2 of 3Title
- BrowserConsoleConsole error recorded · message not capturedError
- BrowserNetworkPOST /api/checkout500
- checkout-debug.har, metadata only
What source explains it
The IDE extension records the repo, file, branch, and line range that were open while you spoke. Viewers see the file, branch, and line range, with a link that opens those exact lines on GitHub, GitLab, or Bitbucket.
- VS Code, Cursor, and Devin DesktopThe IDE extension works in VS Code-family editors.
- Paths start at the repoViewers see the repo, file, branch, and lines, never your local folders.
- Search by fileMoment search finds every recording where a file was open, at the second it was.
What the command line showed
The shoyu command records the terminal as a replay, synced to the recording. Capture is output-only by default. Raw input needs a separate, explicit flag.
- Any shellRun
shoyu terminal recordin a shell while you record. The replay keeps each command and what it prints. - Secrets maskedShoyu masks likely secrets such as tokens and keys, but it can miss one.
- Search and downloadMoment search finds the second a command ran, and the session downloads as a replay.
Context in your control
Shoyu captures where the work happened, not what it contained.
- Transcription runs on your Mac. Nothing is sent to a third party to make it.
- A hosted AI service suggests titles from the transcript and context, unless your organization turns that off.
- Code context never uploads code. It points to the repo, file, and lines.
- Deep Context is off by default. When it is on, the tab says so.
- Your team decides which context layers are allowed.
The full list of what is and is not captured is on the Security and privacy page. Need to know which services we use? Get in touch.
Your apps are understood
Shoyu recognises desktop apps by their window title and their own data on your Mac, and pages by their URL. Anything it does not recognise still gets its app name and title, without a link.
Stop explaining where to look
Every recording your team makes arrives with its context attached. Try for free and we will set you up together.