AI summary

Know what went wrong without watching the recording

Birdie reads each recording and writes up what went wrong, so an agent knows whether they can answer it, and an engineer gets a reproduction they can act on.

A summary tells you:

• What went wrong, in one line.

• How to reproduce it, step by step, with a timestamp on each step. Click one to jump to that moment in the video.

• Why it happened, when a console error or failed request can be tied to what happened on screen.

• The evidence behind all of it: the console errors, network requests, user steps, frames and speech Birdie used, each with its timestamp.

Every claim is grounded in something Birdie captured. If nothing in the recording explains the failure, the summary says so rather than guessing.

Your own AI provider

AI Summary runs on your workspace's own AI provider account, not on Birdie's.

Your recording data goes to the provider you already use, under your own agreement with them. That means your existing DPA and enterprise terms apply, your zero-retention settings apply, and your security team reviews no new subprocessor. You choose the vendor, the region and the model.

Supported providers: OpenAI, Anthropic, Google, Azure OpenAI, AWS Bedrock, Mistral and OpenAI-compatible endpoints.

Admins can switch off every AI feature for the whole workspace, including MCP and CLI access, under Settings → Security & access.

Turning it on

Go to Settings → Recordings and open Manage on the AI Summary row.

1. Choose your provider and paste an API key.

2. Pick a model. Birdie shows the models available on your key with their relative cost, from the most thorough to the cheapest. It does not pick for you.

3. Choose when summaries run.

Connecting a provider requires admin access. Once it's connected, anyone with access to a recording can see its summary.

When summaries run

Set separately for customer recordings and team recordings:

• Automatic — every new recording is summarized as soon as it finishes processing, and the summary is included in the webhook payload.

• Manual — a Generate button appears on each recording.

• Off — no summaries for that kind of recording.

Good to know

• Summaries are written in English.

• Audio is optional. Birdie works from console logs, network requests, user steps and the screen itself, so silent recordings are summarized too. See Transcript & Captions.

• A summary reflects what the recording captured. A recording that ends before the problem occurs won't contain it.

• Summaries are included in Slack notifications, ZIP exports, the API and the webhook payload, and the reproduction steps can be copied straight into Linear or Jira.