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
To upload Loom recordings (anyone on the team — no CLI needed):
- A SageOx team account
- Loom recordings you want to preserve
To implement with recording context (developers):
- SageOx CLI installed (
ox) with a connected repo (ox init) - A coding agent (Claude Code, Codex, etc.)
The workflow
1. Upload or import a Loom recording
- Copy the share URL from any Loom video
- Go to your team's Media section at sageox.ai
- Click Import
- Paste the Loom URL and add a descriptive title
SageOx downloads the video and processes it automatically. Processing takes 1–3 minutes depending on length.
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 | Screenshots at visually significant moments with AI descriptions |
| Metadata | Title, duration, import date |
3. Your AI coworker references it
The next time an AI coworker starts a session, 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 one at a time through the web UI. Each import runs independently — queue up as many as you have.
For large backlogs, consider prioritizing:
- Architecture and design decision recordings
- Onboarding walkthroughs
- Bug investigation recordings
- Feature demos with design rationale
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 RecordingService in apps/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 deserves two recordings.
Download-then-upload workflow
If your Loom is behind SSO or you prefer local files:
- In Loom, click ... → Download → save the MP4
- Go to your team's Media section
- Click Upload and drag in the file
- Add a descriptive title
Both methods produce the same result — URL import is faster when available.
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.
Anyone on your team can upload recordings through the web — no CLI, no setup. 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
- Upload via web — drag-and-drop upload from the SageOx web interface
- Video Import — all import options and supported formats
- Loom Import — detailed Loom import guide
- SageOx + Claude Code — how your AI coworker uses imported recordings
- SageOx for solo players — build a personal knowledge base before your team joins
Cookbooks | SageOx Workflow Recipes and Integration Guides
Step-by-step workflow recipes for SageOx. Integrate with Loom, Figma, Cap, Claude Code, Codex, and OpenClaw. Build team knowledge that compounds over time.
SageOx + Figma | Turn Design Walkthroughs into AI-Accessible Knowledge
Import Figma design walkthroughs into SageOx. Automatic transcription and keyframe extraction turn your design rationale into context AI coworkers reference when implementing UI.