You don't need your whole team

Most tools need buy-in from everyone before anyone gets value. SageOx is different. You can start alone, see results in 5 minutes, and your team benefits later when they join.

This page is for you — the engineer who wants to try something before pitching it.

Setup (2 minutes)

That's it. You now have a team (just you) and a connected repo.

Immediate wins — no teammates required

1. Better Claude Code sessions, instantly

When you run ox init, SageOx sets up context injection for your AI coworkers. Every Claude Code session starts with your team's conventions, architectural decisions, and domain knowledge pre-loaded.

But here's the solo-player unlock: CodeDB.

CodeDB indexes your repo's code and git history into a searchable database that Claude Code can query. Instead of grep-and-hope, your AI coworker gets:

• Semantic code search — find functions, types, and patterns by meaning, not just text
• Git history search — "when did this behavior change?" and "who touched this module?"
• Cross-reference navigation — understand how code connects across your codebase

This alone makes Claude Code dramatically better at navigating large codebases. No coworkers needed — it's you and a smarter AI coworker.

2. Turn screen recordings into searchable knowledge

You already record Loom walkthroughs. You already use Cap to capture quick demos. Right now those recordings live in Slack threads that nobody will ever find again.

Import them into SageOx and they become structured, searchable artifacts:

SageOx transcribes the audio, extracts keyframes, summarizes the content, and commits it all to your Team Context repo. The next time Claude Code starts a session, it can reference what you discussed in that walkthrough.

Use cases that pay off immediately:

3. Voice memos to yourself

Create a habit of recording 60-second voice memos when you have an idea, make a decision, or hit a wall.

Open the web recorder on your phone (add it to your home screen for one-tap access) and just talk:

• "I'm going with Postgres JSONB for the metadata column because we don't know the schema yet and I don't want to run a migration every time we add a field."
• "The auth flow is broken when the refresh token expires during a long-running upload. Need to add retry logic in the upload middleware."
• "Idea: we should expose the keyframe extraction as a public API endpoint so other tools can use it."

These get transcribed and committed automatically. Six months from now, when someone asks "why did we use JSONB here?", the answer is in your Team Context — not lost in your head.

4. Import your back catalog

Got a folder of old Loom videos? A backlog of Cap recordings? Import them all at once:

Every recording gets transcribed, summarized, and indexed. Instant searchable knowledge base from content you already have.

Why this matters even as a solo player

The compounding effect is real. After a week of importing recordings and recording voice memos, you'll have:

• An AI coworker that knows your decisions — not just your code, but why you wrote it that way
• Searchable walkthroughs — no more scrubbing through 20-minute Loom videos to find the one thing you said about the API
• A personal engineering journal — that you barely had to write, because you just talked

And when your coworkers eventually ask "what is this thing you keep importing recordings into?" — you already have the answer. Their onboarding is ox login && ox init. Everything you've built is already there waiting for them.

Next steps

• Video Import — full guide to importing recordings
• Web Recorder — record from your browser or phone
• Team Setup — ready to invite your team?