# New Team Member Quickstart (/docs/quickstart/new-team-member)



New Team Member Quickstart [#new-team-member-quickstart]

This guide is for people **joining an existing team** via an invite link.

<Callout>
  Setting up SageOx for your team from scratch? See the [Team Setup Quickstart](/docs/quickstart/team-setup) instead.
</Callout>

Step 1: Accept the invite [#step-1-accept-the-invite]

Click the invite link your teammate shared. This takes you to SageOx where you can create an account (or sign in) and join the team.

Step 2: Choose how you want to start [#step-2-choose-how-you-want-to-start]

The same team can use SageOx in different ways. Pick the mode that matches what you are doing first:

| If you are mostly | Start here                                                                                                         |
| ----------------- | ------------------------------------------------------------------------------------------------------------------ |
| Code-mode         | Install `ox`, then connect each repo you work in                                                                   |
| Assistant-mode    | Connect SageOx over [MCP](/docs/mcp)                                                                               |
| Capture-mode      | Start with [Console Recorder](/docs/context-capture/console) or [Video import](/docs/context-capture/video-import) |

Step 3: If you are building in code, install the CLI [#step-3-if-you-are-building-in-code-install-the-cli]

<Terminal>
  <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>
</Terminal>

Step 4: If you are building in code, authenticate [#step-4-if-you-are-building-in-code-authenticate]

<Terminal>
  <TerminalCommand>
    ox login
  </TerminalCommand>
</Terminal>

This opens your browser to confirm. Your session persists across terminal restarts.

Step 5: If you are building in code, connect your repositories [#step-5-if-you-are-building-in-code-connect-your-repositories]

In each git repo you work on:

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

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

This links the repo to your team. Repeat for each repo you work on.

Step 6: Start using SageOx [#step-6-start-using-sageox]

If you connected a repo, launch your AI coding tool as usual:

<Terminal>
  <TerminalCommand>
    claude
  </TerminalCommand>
</Terminal>

The agent automatically runs `ox agent prime` on startup, injecting your team's shared context — conventions, architectural decisions, and domain knowledge.

If you started with MCP instead, connect your assistant through the [MCP overview](/docs/mcp) and ask it to search SageOx or read team knowledge.

If you started with capture, record a discussion or import a walkthrough and let SageOx distill it into Team Context for the rest of the team.

If the repo-connected setup seems off, run `ox doctor` to diagnose authentication, repo connection, and team membership.

Next steps [#next-steps]

* [CLI Commands Reference](/docs/cli/quickstart)
* [MCP overview](/docs/mcp)
* [Learn about Team Context](/docs/context-capture/discussions)
* [Console Recorder](/docs/context-capture/console) — record team discussions