ox prime

ox prime (or ox agent prime) injects Team Context into AI coding agents, providing them with domain-specific guidance, architectural decisions, and coding conventions.

How It Works

When an agent runs ox prime:

1. Fetches Team Context - Retrieves your team's shared knowledge base from SageOx
2. Injects Context - Provides it to the agent in a format it can use
3. Confirms with Agent ID - Returns a unique identifier confirming context is active

The agent then has access to:

• Team norms and conventions
• Architectural decisions
• Distilled learnings from past work
• Domain-specific guidance

Setup

Context injection is automatically configured when you run ox init in a repository. The agent needs:

1. Repository initialized with SageOx (ox init)
2. Valid authentication (ox login)
3. Shell access to run the command

Agents like Claude Code can be configured to run ox prime automatically via CLAUDE.md instructions.

Supported agents

Because SageOx injects context through the repo itself — not through a vendor-specific API — a discovery made by a Claude Code session is available to a Codex agent in the next session. No vendor lock-in on your team's accumulated knowledge.

Checking if it's working

Agent Has Context

Ask the agent: "Are you using SageOx?"

A primed agent responds with its agent_id:

Command Output

Successful prime returns:

Doctor Check

Run ox doctor to verify context injection is configured:

When Context Is Lost

Agents lose injected context when:

The agent should re-run ox prime after these events.

Troubleshooting

No agent_id returned - Check ox doctor for configuration issues

Context not reflected in responses - Verify the agent actually ran the command (check for agent_id)

Stale context - Context version shows when it was last updated; re-prime to get latest

Related Commands

• ox init - Initialize repository (required first)
• ox doctor - Diagnose configuration issues
• ox login - Authentication