SageOx + Cap

Cap gives you full control over recording quality and export settings — something Loom doesn't offer. This cookbook shows how to configure Cap for optimal SageOx extraction and build a recording habit that compounds into searchable team knowledge.

Why Cap over Loom

For quick, one-off recordings, Loom works. For regular walkthroughs where you want consistent quality and smaller file sizes, Cap is better.

What you need

• Cap installed (free)
• A SageOx account with a connected repo (ox init)

The workflow

1. Record your screen

Open Cap and start a screen recording. Narrate as you go — the transcript quality drives extraction quality.

Good recordings have:

• Clear narration explaining why, not just what
• Focused scope (5-10 minutes max)
• Minimal desktop clutter

2. Export with optimal settings

After recording, open Cap's export dialog and configure:

These settings produce ~8 MB per minute — fast to upload, fast to process.

3. Upload to SageOx

1. Go to your team's Media section at sageox.ai
2. Click Upload
3. Drag in your exported MP4
4. Add a descriptive title

Processing starts automatically. Transcription, keyframe extraction, and summarization run in the background.

4. Your AI coworker references it

The next time Claude Code starts a session, your recording is in context. Your AI coworker can reference the decisions you explained, the UI you walked through, or the bug you reproduced.

Recipes

Bug reproduction recordings

When you find a bug, record the reproduction steps:

1. Show the starting state
2. Narrate the steps: "I'm clicking the submit button with an empty form..."
3. Show the unexpected behavior
4. Explain what you expected instead

Export and upload with a title like "Bug: Cart total shows $0 after removing items". Your AI coworker can analyze the recording to help find the root cause.

Architecture walkthrough recordings

Before diving into a refactor, record a walkthrough of the current state:

1. Open the relevant code files
2. Explain how data flows through the system
3. Point out the pain points you want to address
4. Sketch the target architecture (whiteboard or drawing tool)

This gives your AI coworker the full context when you ask it to help with the refactor.

Code review walkthrough recordings

Instead of writing long PR comments, record a 3-minute walkthrough:

1. Open the PR diff
2. Walk through the changes
3. Explain your feedback verbally
4. Highlight specific lines that need attention

The recording captures nuance that's hard to convey in text. Upload it and link in the PR.

Onboarding recordings

Record walkthroughs for common onboarding topics:

• "How our auth system works"
• "The request lifecycle from API to database"
• "How to set up the local dev environment"

New team members get these recordings in their AI coworker context from day one.

Tips for better recordings

Narrate your reasoning "I'm checking the network tab because I suspect the preflight is failing" beats silent clicking.

Say code names out loud "This is the RecordingService in apps/workflow" creates transcript anchors that link to your codebase.

Keep it under 10 minutes Shorter recordings produce tighter summaries. Split longer sessions by topic.

Clean your desktop Close Slack, hide bookmarks, full-screen the app you're demoing. Fewer distractions means better keyframe extraction.

Use descriptive titles "Sprint 12 Checkout Flow Redesign" beats "Recording 47". AI coworkers search by title.

Build the habit

The highest-value pattern: record a 2-minute Cap walkthrough after every meaningful decision.

• Chose an architecture approach? Record why.
• Fixed a tricky bug? Record the root cause.
• Designed a new component? Record the rationale.

Within a week, your Team Context has a searchable history of why things are the way they are.

What's next

• Cap Setup — detailed export settings guide
• Video Import — all import options and formats
• SageOx + Loom — alternative recording workflow
• Using Recordings in Coding Sessions — how AI coworkers use your recordings