ox
Scannednpx machina-cli add skill sageox/ox/ox --openclawSageOx (ox) - Team Context for AI Coworkers
ox is a CLI that gives AI coworkers shared team context: conventions, architectural decisions, session recording, and collaborative knowledge that persists across sessions and teammates.
When to Use
- Starting work: Run
ox agent primeto load team context (conventions, norms, decisions) - Recording sessions:
ox agent session start/ox agent session stopto capture work to the project ledger - Checking health:
ox statusfor auth/sync/daemon state,ox doctorfor diagnostics - Initializing:
ox initto set up SageOx in a new repository
Key Concepts
- Team Context - shared conventions, norms, and architectural decisions (versioned)
- Ledger - historical record of sessions, decisions, and discussions
- Session - a recorded human-to-AI coworker conversation
- AI Coworker - an AI participant on a team (not "agent" in user-facing output)
Essential Commands
| Command | Purpose |
|---|---|
ox agent prime | Load team context for this session |
ox agent session start | Begin recording a session |
ox agent session stop | Stop recording and push to ledger |
ox status | Check auth, sync, daemon health |
ox doctor | Run diagnostic checks |
ox init | Initialize SageOx in a repository |
ox conventions | Get verified team coding standards |
ox session list | List recent sessions from ledger |
Requirements
Install the ox CLI: brew install sageox/tap/ox or visit https://sageox.ai/install
Source
git clone https://github.com/sageox/ox/blob/main/claude-plugin/skills/ox/SKILL.mdView on GitHub Overview
ox provides a CLI to load and share team conventions, architectural decisions, and a persistent session ledger among AI coworkers. It ensures consistent context across sessions and teammates so AI coworkers can reference the same standards when collaborating.
How This Skill Works
Use ox agent prime to load the team context (conventions, norms, decisions). Start a session with ox agent session start and stop with ox agent session stop to push recordings to the ledger, while ox conventions and ox status/doctor help maintain health and standards. The ledger stores historical sessions, decisions, and discussions for future reuse.
When to Use It
- Starting work in a repository with .sageox initialized
- Recording coding sessions to the project ledger
- Checking auth, sync, and daemon health with ox status and ox doctor
- Initializing SageOx in a new repository
- Reviewing and applying verified team conventions via ox conventions
Quick Start
- Step 1: Run ox agent prime to load team context in a repo with .sageox
- Step 2: Start recording a session with ox agent session start
- Step 3: Stop recording and push to the ledger with ox agent session stop
Best Practices
- Run ox agent prime at the start of a session to load team context
- Use ox agent session start and ox agent session stop to capture work to the ledger
- Regularly check health with ox status and ox doctor to ensure sync and daemon stability
- Refer to ox conventions to apply verified team coding standards
- Initialize or re-initialize SageOx in new repositories with ox init
Example Use Cases
- Loading team context in a feature branch development
- Recording a design discussion to the project ledger
- Auditing past decisions via the ledger for a refactor
- Verifying coding standards before a merge using ox conventions
- Setting up SageOx in a new repository with ox init
