New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →

Get Started

omx-copilot

Package Overview

Dependencies

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

Package was removed

Sorry, it seems this package was removed from the registry

omx-copilot

Multi-agent orchestration layer for CoPilot CLI

latest

Source

npm

Version: 0.1.0

Version published: 6 months ago

Maintainers: 1

Created: 6 months ago

Source

oh-my-codex (OMX)

oh-my-codex character
Start Copilot CLI stronger, then let OMX add better prompts, workflows, and runtime help when the work grows.

Community: Discord — shared OMX/community server for oh-my-codex and related tooling.

OMX is a workflow layer for GitHub Copilot CLI.

It keeps Copilot CLI as the execution engine and makes it easier to:

start stronger sessions by default
run one consistent flow from clarification to completion
invoke canonical workflows with $deep-interview, $ralplan, $team, and $ralph
keep project guidance, plans, logs, and state in .omx/

Reference And Attribution

This README's product framing and usage model are authored for OMX, and are informed by these sources:

OMX runtime contract and orchestration policy in AGENTS.md
OMX command surfaces and behavior in src/cli/index.ts
Existing OMX docs set in docs/getting-started.html and docs/skills.html
Legacy website/docs sources (historical reference, may be outdated/unavailable):
- https://yeachan-heo.github.io/oh-my-codex-website/
- https://yeachan-heo.github.io/oh-my-codex-website/docs.html

The implementation remains the oh-my-codex project and keeps compatibility paths such as .codex/ and CODEX_HOME where required by runtime behavior.

Legacy Team Listings (Historical Reference)

These listings are preserved as historical reference only.

Core Maintainers

Role	Name	GitHub
Creator & Lead	Yeachan Heo	@Yeachan-Heo
Maintainer	HaD0Yun	@HaD0Yun

Ambassadors

Name	GitHub
Sigrid Jin	@sigridjineth

Top Collaborators

Name	GitHub
HaD0Yun	@HaD0Yun
Junho Yeo	@junhoyeo
JiHongKim98	@JiHongKim98
Lor	—
HyunjunJeon	@HyunjunJeon

New Usage Guide

1) Clone And Install Dependencies (Source Only)

git clone https://github.com/Yeachan-Heo/oh-my-codex.git
cd oh-my-codex
npm install
npm run build

What this does:

installs local dependencies
builds dist/ outputs from this source tree
prepares runnable local CLI entrypoint at dist/cli/omx.js

2) Initialize Runtime Assets From Source Build

npm run setup
npm run doctor

Equivalent direct commands:

node dist/cli/omx.js setup
node dist/cli/omx.js doctor

3) Start A Session (From This Source Tree)

Default interactive session:

node dist/cli/omx.js

High reasoning + permissive approvals (trusted environments only):

node dist/cli/omx.js --high --madmax

Detached tmux leader session:

node dist/cli/omx.js --tmux --high --madmax

4) Use The Core Flow In Session

Use this sequence for most complex work:

$deep-interview "clarify requirements and boundaries"
$ralplan "approve architecture, risks, and tests"
$ralph "execute end-to-end with verification"

When execution is parallelizable, switch to team mode:

$team 3:executor "implement approved plan in parallel lanes"

5) Daily Command Patterns (Source Build)

Repository exploration:

node dist/cli/omx.js explore --prompt "find where worker launch args are normalized"

Bounded shell verification:

node dist/cli/omx.js sparkshell git status
node dist/cli/omx.js sparkshell --tmux-pane %12 --tail-lines 300

Team runtime operations:

node dist/cli/omx.js team 4:executor "fix build and failing tests"
node dist/cli/omx.js team status <team-name>
node dist/cli/omx.js team resume <team-name>
node dist/cli/omx.js team shutdown <team-name>

6) Runtime Model

Think of OMX in three layers:

Copilot CLI runs the core agent execution
OMX adds orchestration workflows and guardrails
.omx/ persists plans, state, logs, and runtime metadata

7) Environment Requirements

Node.js 20+
Copilot CLI installed and authenticated in your environment (@openai/codex)
tmux on macOS/Linux for team mode
psmux on Windows for native team mode

8) Operational Tips

Use npm run setup after upgrades to refresh managed assets
Use npm run doctor first when something looks inconsistent
Keep AGENTS.md in repo root for project-specific orchestration policy
Prefer $ralplan before $team/$ralph for large or risky changes

9) Known Startup Issue (Intel Mac)

If startup causes high syspolicyd / trustd CPU on Intel Macs:

run xattr -dr com.apple.quarantine $(which omxc) (if you also use a global install)
add your terminal to Developer Tools in macOS security settings
reduce launch aggressiveness (for example, skip --madmax --high)