Frequently asked questions

Start here for short answers about SageOx. Follow the links when you need more detail.

SageOx turns discussions and work into context that human and AI coworkers can reuse. It captures what matters, distills it into Team Context and Ledger history, and makes that context available in connected AI coworkers, coding sessions, and the web app.

Read How SageOx works for the full data flow.

Where should I start?

Choose the mode that matches what you're doing now:

Assistant-mode: Connect SageOx to an MCP-compatible AI coworker. Start with the MCP overview.
Code-mode: Connect a checked-out repository and work with Claude Code or Codex. Start with the ox CLI quickstart.
Capture-mode: Record or import a discussion. Start with context capture.

The getting started guide compares all three paths.

Do I need to connect a repository first?

No. Assistant-mode and capture-mode work without a connected repository. Connect one when you want code-mode features such as repo-aware context, local code indexing, and coding-session capture.

Which AI coworkers work with SageOx?

Code-mode supports repo-based AI coworkers such as Claude Code and Codex. Support depth varies by tool. Assistant-mode works with MCP-capable clients such as ChatGPT, Claude Cowork, and Claude Desktop.

See the coding tools overview and MCP setup guides for current integration details.

Understand shared context

What is Team Context?

Team Context is the shared record of your team's conventions, decisions, discussion transcripts, and distilled memory. It is team-wide, so human and AI coworkers can build on the same knowledge.

Read Team Context for its structure and editing workflow.

What is the Ledger?

The Ledger is the per-repository history of code work, commits, sessions, and project-specific decisions. Team Context travels across the team; each Ledger stays scoped to one repository.

Read Session recording to see how coding work reaches the Ledger.

What can SageOx capture?

SageOx can capture discussions from desktop or mobile browsers, in-room discussions through Ox Dot, and imported audio or video. Those discussion paths feed Team Context.

Coding sessions follow a separate path: the ox CLI captures them into the repository's Ledger. See context capture and session recording for both flows.

Know where context lives

Does SageOx send my source code to Anthropic or OpenAI?

No. SageOx does not send your source code to an AI model provider. CodeDB indexes code locally on your machine, while AI coworker sessions continue to use your own provider account.

How do I get all my SageOx data?

All customer content lives in git. Team Context and Ledgers are git repositories, and audio recordings are checked into git too. A git checkout gives you all your data in open formats that you can inspect and keep, without locking you into SageOx.

Only rebuildable caches and operational state such as permissions and settings live outside those repositories. We will keep improving the checkout and portability experience over time. Read Your data for the repository layout and storage details.

Get help

What should I do when setup isn't working?

For code-mode, follow the ox doctor diagnostic guide, then run the diagnostic and apply the reported fixes:

terminal

# Check your SageOx setup

For mobile issues, use the mobile troubleshooting guide. For anything else, visit SageOx support.

What's next

Getting started: choose your first SageOx workflow
Your data: inspect and keep your SageOx data
Support: contact the SageOx team