SageOx + Claude Code

Every Claude Code session starts with context from your team's decisions, conventions, and past discussions — and every session's discoveries flow back for future use. This cookbook walks through the full loop: setup, daily usage, and the patterns that compound over time.

Setup

ox init configures Claude Code to run ox agent prime at session start. That's the entire setup.

Recipe 1: Context-aware coding sessions

Start Claude Code as normal. SageOx injects your Team Context automatically.

Your AI coworker receives:

The difference: Without SageOx, your AI coworker reads your code and guesses at conventions. With SageOx, it knows your team chose Postgres JSONB for metadata because the schema isn't stable, that parcel means a geographic unit not a shipping package, and that you use snake_case for API fields.

Recipe 2: Capture session knowledge

Coding sessions produce valuable insights — architecture discoveries, debugging breakthroughs, refactoring rationale. Capture them so future sessions benefit.

Inside Claude Code, use the session commands:

/ox-session-start
... work on your feature, debug an issue, refactor a module ...
/ox-session-stop

The session transcript — your questions, the AI coworker's reasoning, decisions made — gets committed to your repo's Ledger. Future sessions can reference it.

High-value moments to capture:

• Debugging sessions where you root-cause a tricky bug
• Architecture decisions made mid-implementation
• Refactoring rationale ("we're splitting this service because...")
• Onboarding exploration of unfamiliar code

Recipe 3: Reference recorded discussions

Import your Loom walkthroughs, Figma design sessions, and team recordings. Your AI coworker can reference them during implementation.

"Look at the UX walkthrough 'Checkout Flow Redesign' and implement the action bar"

Claude Code finds the recording, reads the transcript and keyframe descriptions, and implements based on the designer's explanation — not just a static screenshot.

See Using Recordings in Coding Sessions for more examples.

Recipe 4: Multiplayer — shared context across AI coworkers

When multiple people work on the same repo, they all receive the same Team Context. Decisions made in one session become available to all future sessions.

This works with any orchestration layer — terminal sessions, IDE integrations, or custom agent factories. The integration point is always ox agent prime via CLAUDE.md.

Agent factory setup

If you're running an agent factory that spawns Claude Code sessions:

1. The factory starts Claude Code in your repo
2. Claude Code reads CLAUDE.md and runs ox agent prime
3. Team Context flows in — no factory-specific configuration needed
4. Session artifacts get captured via /ox-session-start

The CLAUDE.md hook is the universal integration point. Any tool that starts Claude Code in your repo gets SageOx context automatically.

The compounding loop

The real value isn't any single session. It's the loop:

1. You record a decision — Loom walkthrough, voice memo, team discussion
2. SageOx processes it into structured Team Context
3. Your AI coworker references it in the next coding session
4. That session produces new insights captured to the Ledger
5. Future sessions start smarter because of steps 1–4

After a week, your AI coworker knows not only your code but why it's structured the way it is. After a month, it has context that would take a new hire weeks to absorb.

Best practices

Record decisions, not just code The highest-value context is why things are the way they are. Record a 2-minute Loom after architecture calls, bug fixes, and design decisions.

Use descriptive session names When you run /ox-session-start, the session gets a name. "Auth refactor investigation" is more findable than "Session 47".

Review your Team Context Periodically browse .sageox/teams/primary/ to see what your AI coworkers are reading. Edit AGENTS.md to add conventions they should follow.

Capture onboarding sessions When a new team member explores the codebase with Claude Code, capture that session. Their questions and the AI's explanations become documentation for the next person.

What's next

• Team Context — what's in it and how to edit it
• SageOx + Loom — feed Loom walkthroughs into the context loop
• SageOx + Figma — turn design walkthroughs into implementation context
• SageOx for solo players — start the loop before your team joins