Context capture is every way knowledge gets into SageOx. Record a discussion, upload an existing file, or import a video: each path transcribes, extracts insights, and commits the result to your Team Context, where your AI coworkers read it.
Discussion capture
A Discussion is a transcribed recording of a human-to-human conversation: a standup, a design review, an incident retro. Pick the mechanism that matches where the conversation happens.
| Mechanism | What it captures | Status | Link |
|---|---|---|---|
| Ox Dot | In-room audio from a dedicated hardware device | Available | Ox Dot |
| SageOx Desktop | Both sides of a computer call on a Mac: your mic and the system audio | Available | Get the app · Setup guide |
| Visual walkthrough | Your voice, a window or screen area, and what you pointed at, so AI coworkers can act on visual feedback | Available | Visual walkthrough |
| Web app recorder | A live discussion straight from your browser or phone | Available | web app recorder |
| Audio + transcript upload | An existing audio file or transcript from any source | Available | Audio + transcript upload |
| Loom, Figma, Cap video | A screen recording or video walkthrough | Available | Video import |
| Ox App | On-the-go audio from your phone | Coming soon | — |
| Zoom / Google Meet / Teams | A meeting SageOx joins to share live insights | Coming soon | — |
| Slack / Mattermost | Chat-based team discussions from your workspace | Coming soon | — |
The Ox App, Slack and Mattermost capture, and meeting-platform capture are in development. Meeting attendee for Zoom, Google Meet, and Teams ships behind the meeting-join Feature Preview.
How captured context flows
Every mechanism feeds the same pipeline. The source differs; the destination is always Team Context.
Transcription and insight extraction run automatically after capture. When the pipeline finishes, decisions, action items, and rationale commit to your Team Context, the shared knowledge every AI coworker reads at session start.
Capture coding sessions
The ox CLI records work with your AI coworker in a connected repository. Session recording explains how that work becomes searchable repository history.
Already have Claude Code or Codex sessions saved on this computer? Import past coding sessions lets you review and upload selected history to that repository's Ledger.
Choosing a mechanism
| You have | Use |
|---|---|
| Past Claude Code or Codex sessions for this repository | Import past coding sessions |
| A discussion happening right now | web app recorder |
| An audio file or transcript from another tool | Audio + transcript upload |
| Feedback on a design, a build, or a change you're reviewing, with your voice and pointing | Visual walkthrough |
| A Loom, Figma, or Cap walkthrough | Video import |
| A terminal and a local file | Import via CLI |
What's next
- Discussions: what discussions capture and how they're stored
- Session recording: save coding work to the repository's Ledger
- web app recorder: record directly from your browser
- Video import: import Loom, Figma, and Cap recordings
- Team Context: where captured knowledge lives