Skip to main content
Capture streams what happens on a call to your local disk: a transcript of what’s said, recordings of any screen that gets shared, and metadata for apps on shared screens. It runs entirely on your machine; nothing gets sent to an external service.Capturing calls enables two things: it lets agents follow the call in real time, and allows you to reference information from past calls.

​
Starting and stopping capture

The Capture button appears in the popover, the screen share window, and the webcam window:The Capture button in the screen share window toolbar on macOSThe Capture button in the webcam window on macOSThe Capture button in the popover call controls on macOSWhen the popover is focused during a call, C toggles capture. See Using your keyboard to navigate Tuple.You can also have Tuple start capturing as soon as you join any call; see Start capture automatically.

​
What Capture records

A captured call contains three kinds of content:
  • Transcript: everything said on a call, transcribed by a local Whisper model.
  • Screen recordings: recordings of any screen that gets shared on a call (yours or someone else’s).
  • App metadata: window titles and content URLs for the apps visible in shared screens; learn more about what gets shared.

​
Disk usage

Screen recordings use almost all of the disk space that Capture takes up. Transcripts and app metadata are small by comparison.As a rough guide, one minute of screen sharing uses 1–10 MB of disk space. A 30-minute call with a screen shared the whole time uses about 30–300 MB; a typical 30-minute call is usually around 100 MB.The exact amount depends on what’s on the screen:
  • Screen activity: a mostly static screen, like an editor you’re reading, uses less space than scrolling, switching windows, or playing video.
  • Resolution: larger and higher-resolution screens use more space. Tuple records shared screens at their full resolution so that text stays legible.
  • Whose screen it is: recordings of your own screen tend to use more space than recordings of screens that other participants share.
To limit how much video Capture stores, set a maximum cache size.

​
Notifying other participants

When you start capturing, every other participant receives a notification letting them know. The notice stays on screen until the participant acknowledges it or leaves the call. If you join a call that’s already being captured, you’ll receive the same notification.While capture is active, each capturing participant shows a Capturing indicator in the popover participant list and in the screen share window’s participant list.

​
Capturing solo

You can capture a call by yourself, even before any other participants have joined. This is useful for capturing notes, dictation, or working with an agent (see Connecting an agent).

​
The Capture menu

The chevron next to the Capture button opens the Capture menu, which shows what’s being captured right now and how to hand the call to an agent:Capture menuThe top of the menu is a live status block showing what’s being captured (transcript, screen recordings, and app metadata). Each row has a status dot that dims when that kind of content isn’t being collected.Below the status block, Connect a Local Agent allows you to copy commands to hand the live call to an agent:
  • Copy Terminal Command copies a tuple connect command to run in your terminal.
  • Copy Agent Prompt copies a prompt to paste into an agent you already have running.
Copying a command or prompt provides context. Ask the agent explicitly when you want it to follow the call continuously. For existing scripts or skills, use the migration guide.

​
Accessing captured calls

Captured call content is stored in a local database on your machine. You can browse captured calls in the Local History tab, or use the tuple CLI to search, list, and export past calls — see Searching past calls.

​
Automating with triggers

Tuple fires call-capture-started and call-capture-complete triggers when a capture session begins and ends. Use a trigger script to post-process transcripts, summarize the call, or save it into your team’s notes system.Browse the Triggers Directory to see what others have built.