Getting started
SageOx has more than one real front door. Some coworkers start in code-mode while building in a checked-out repo. Some start in assistant-mode through ChatGPT, Claude Cowork, or another MCP-connected assistant. Some start in capture-mode by recording the discussions where product and engineering decisions actually happen.
Start with the mode you are in right now:
- Code-mode — building in code with
ox - Assistant-mode — working through MCP
- Capture-mode — recording or importing team knowledge through Context capture
Choose your path
| What you are doing first | Start here | Why |
|---|---|---|
| Building in Claude Code, Codex, Gemini CLI, Aider, or another repo-based coding tool | Quickstart: ox CLI | Code-mode connects your repo, primes Team Context into coding sessions, and unlocks repo-aware features like indexing and session capture. |
| Working in ChatGPT, Claude Cowork, Claude Desktop, or another MCP-capable assistant | MCP overview | Assistant-mode is the fastest path when you want SageOx search, interactive cards, and access to team knowledge without starting from a checked-out repo. |
| Recording discussions, walkthroughs, or voice notes | Context capture | Capture-mode feeds the same Team Context and Ledger system, even if you have not connected a repo yet. |
You do not need to pick one forever. Most product-shaping coworkers end up using more than one mode over time.
Code-mode
Use this path when your AI coworker is working inside a checked-out repo.
After that, start your coding tool as usual. In many supported tools, Team Context is injected automatically at session start. If setup seems off, run ox doctor.
Assistant-mode
Use this path when the assistant itself is your starting point.
- Open the MCP connect flow
- Pick your assistant
- Authorize SageOx
- Ask the assistant to search SageOx, read team knowledge, or save useful work back
Read MCP overview first, then Getting the most out of SageOx via MCP for the prompt patterns that make it useful quickly.
Capture-mode
Use this path when the first value is getting conversations and walkthroughs into shared memory.
- Console Recorder — record directly in the browser
- Video import — bring in Loom, Cap, Figma, and downloaded recordings
- Mobile guides — mobile capture, casting, and troubleshooting
Every capture path feeds the same distillation pipeline and lands in Team Context.
Team state quickstarts
These pages answer a different question: not how are you working?, but where are you in the team lifecycle?
- Solo Quickstart — try SageOx alone first
- Team Setup Quickstart — create a team and invite coworkers
- New Team Member Quickstart — join an existing team
What happens next
Whatever path you start with, the destination is the same:
- Work or discussions are captured
- SageOx distills them into Team Context and Ledger history
- That context becomes available in assistants, coding sessions, and the web app
Next steps
- MCP overview — connect SageOx to your assistant
- Quickstart: ox CLI — connect a repo for code-first workflows
- Context capture — every way to feed SageOx knowledge
- Features — how Team Context, distillation, and your data fit together