SageOx + Loom
You already record Loom walkthroughs. This cookbook turns them from ephemeral Slack links into structured knowledge your AI coworkers can reference during coding sessions.
What you need
- SageOx CLI installed (
ox) - A connected repo (
ox init) - Loom recordings you want to preserve
The workflow
1. Import a Loom recording
Grab the share URL from any Loom video and pass it to ox import. The CLI initiates the import, then SageOx processes the recording (transcription, keyframes, annotations) and commits everything to your Team Context.
Processing takes 1–3 minutes depending on length. You don't need to wait — keep working and the results land in your Team Context automatically.
2. See what SageOx extracts
Once processing completes, your recording becomes a structured artifact:
| Artifact | What it contains |
|---|---|
| Transcript | Full text with timestamps and speaker labels |
| Summary | Key points, decisions, and action items |
| Keyframes | Extracted screenshots at visually significant moments |
| Annotations | Semantic tags linking content to code concepts |
3. Your AI coworker references it
The next time an AI coworker starts a session in this repo, the recording's content is part of its context. It can reference the walkthrough's decisions, the architecture you drew on screen, or the bug reproduction steps you narrated.
Before SageOx: "Why did we redesign the upload API?" → grep through Slack, find nothing, guess.
After SageOx: "Why did we redesign the upload API?" → your AI coworker cites the Loom walkthrough where you explained the rate-limiting issues.
Recipes
Import your Loom back catalog
Got months of Loom recordings scattered across Slack? Import them all.
Each import runs independently. Queue up as many as you have.
Record with better extraction in mind
SageOx extracts more value when you record with a few habits:
- Narrate your reasoning, not your clicks. "I'm switching to the network tab because I suspect the preflight is failing" beats silent mousing.
- Say names out loud. "This is the
RecordingServiceinapps/workflow" gives the transcript anchors that link to your codebase. - Keep it under 10 minutes. Shorter recordings produce tighter summaries. If you're going longer, the topic probably deserves two recordings.
Download-then-import workflow
If your Loom is behind SSO or you prefer local files:
- In Loom, click
...→ Download → save the MP4 - Import the local file:
Build the habit
The highest-value pattern: record a 2-minute Loom after every meaningful decision. Architecture call? Record it. Bug root-caused? Record the fix. PR feedback session? Record the walkthrough.
Within a week, your Team Context has a searchable history of why things are the way they are — not buried in Slack threads, not lost in someone's head.
What's next
- Video import reference — all import options, formats, and flags
- SageOx + Claude Code — how your AI coworker uses imported recordings
- SageOx for solo players — build a personal knowledge base before your team joins