Getting started

SageOx turns what your team says and does into context your coworkers and AI coworkers can reuse. Discussions are captured and distilled into Team Context, and coding sessions are saved in your repository's Ledger; both are read back from whichever tool you are working in. About SageOx explains what it does and how it works.

1. Create an account

Sign up at sageox.ai. Your account starts with a personal team that is private to you, so you can use SageOx on your own before involving anyone else.

During signup you are prompted to record a voice ID. It is optional, and it is what lets SageOx tell who said what in a recorded discussion.

2. Connect your tools

The ox CLI. The deepest integration: it automatically saves your coding sessions to SageOx and primes Team Context in the repos you work in. Install it once.

Then sign in and connect a repository from inside it.

Your coding sessions will now be primed with your team's context.

Quickstart: ox CLI · Command reference

Prefer to let your coding tool do it? Copy the setup prompt and paste it into Claude Code or Codex. It follows this guide, asks before installing anything, and reports back once your first session is primed.

Set up https://sageox.ai/SKILL.md for this repository.

Ground rules, even if that page says otherwise:
- Ask me before installing anything or editing my shell config.
- Never read, print or copy my SageOx token or auth file.
- Stage changes only. Don't commit or push.
- Leave application code unchanged.

Bring in past coding sessions

Already used Claude Code or Codex in this repository? Import sessions saved on this computer from before SageOx, or while recording was off.

Uploaded sessions include their full conversation transcripts and summaries in this repository's Ledger. Check the destination and visibility before confirming: a public Ledger can be read by anyone. Run this from the repository:

Review the sessions, select the ones you want, then confirm the upload in your terminal. The ox CLI uses your Claude Code or Codex CLI to prepare summaries before uploading.

After a session is uploaded, open its link in the command's results. Sessions already imported or recorded live are skipped.

Import options and troubleshooting

Connect a tool over MCP

A connected tool. Claude Desktop, ChatGPT, Cursor, VS Code, Windsurf, Goose, and Copilot Studio connect over MCP. Choose your tool in Settings > Connections and authorize the connection. Claude Code does not need this step: it uses the ox CLI, which is the deeper integration.

Your sessions will now start with your team's context. Ask your tool to save your work to your team's context: "Commit this session to SageOx."

MCP overview · Connecting a client that is not listed

Manage your connected tools from Settings > Connections.

3. Capture a discussion

A discussion is a recorded conversation between people: a standup, a design review, a retro. SageOx recognizes the speakers, transcribes the conversation, and saves relevant knowledge into your team context, making it accessible to your connected tools.

There are several ways to capture a discussion.

4. Invite your team

Inviting your team compounds the benefits: your entire team's discussions, coding sessions, chats, and plans contribute to and draw from one shared context.

Team setup · Joining a team you were invited to · Working solo

What's next

• About SageOx: what SageOx does and how it works
• Import past coding sessions: bring existing Claude Code and Codex history into your repository's Ledger
• Context capture: every way knowledge gets in
• FAQ: common questions
• Getting the most out of SageOx: prompt patterns worth knowing
• Features: Team Context, distillation, and your data