# Getting Started (/docs/getting-started)



Getting started [#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.

<Callout>
  **Start with the mode you are in right now:**

  * **Code-mode** — building in code with [`ox`](/docs/cli/quickstart)
  * **Assistant-mode** — working through [MCP](/docs/mcp)
  * **Capture-mode** — recording or importing team knowledge through [Context capture](/docs/context-capture)
</Callout>

<ScreenFrame caption="Three valid ways to start: assistant-mode over MCP, code-mode in a local repo with ox, or capture-mode through recording and import surfaces." />

Choose your path [#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](/docs/cli/quickstart) | **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](/docs/mcp)                  | **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](/docs/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 [#code-mode]

Use this path when your AI coworker is working inside a checked-out repo.

<Terminal>
  <TerminalComment>
    Install, sign in, and connect your repo
  </TerminalComment>

  <TerminalCommand>
    curl -sSL 

    [https://raw.githubusercontent.com/sageox/ox/main/scripts/install.sh](https://raw.githubusercontent.com/sageox/ox/main/scripts/install.sh)

     \| bash
  </TerminalCommand>

  <TerminalCommand>
    ox login
  </TerminalCommand>

  <TerminalCommand>
    cd ~/code/my-project
  </TerminalCommand>

  <TerminalCommand>
    ox init
  </TerminalCommand>
</Terminal>

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 [#assistant-mode]

Use this path when the assistant itself is your starting point.

1. Open the [MCP connect flow](/connect/mcp)
2. Pick your assistant
3. Authorize SageOx
4. Ask the assistant to search SageOx, read team knowledge, or save useful work back

Read [MCP overview](/docs/mcp) first, then [Getting the most out of SageOx via MCP](/docs/mcp/getting-the-most) for the prompt patterns that make it useful quickly.

Capture-mode [#capture-mode]

Use this path when the first value is getting conversations and walkthroughs into shared memory.

* [Console Recorder](/docs/context-capture/console) — record directly in the browser
* [Video import](/docs/context-capture/video-import) — bring in Loom, Cap, Figma, and downloaded recordings
* [Mobile guides](/docs/mobile) — mobile capture, casting, and troubleshooting

Every capture path feeds the same distillation pipeline and lands in Team Context.

Team state quickstarts [#team-state-quickstarts]

These pages answer a different question: not **how are you working?**, but **where are you in the team lifecycle?**

* [Solo Quickstart](/docs/quickstart/solo) — try SageOx alone first
* [Team Setup Quickstart](/docs/quickstart/team-setup) — create a team and invite coworkers
* [New Team Member Quickstart](/docs/quickstart/new-team-member) — join an existing team

What happens next [#what-happens-next]

Whatever path you start with, the destination is the same:

1. Work or discussions are captured
2. SageOx distills them into Team Context and Ledger history
3. That context becomes available in assistants, coding sessions, and the web app

Next steps [#next-steps]

* [MCP overview](/docs/mcp) — connect SageOx to your assistant
* [Quickstart: ox CLI](/docs/cli/quickstart) — connect a repo for code-first workflows
* [Context capture](/docs/context-capture) — every way to feed SageOx knowledge
* [Features](/docs/features) — how Team Context, distillation, and your data fit together