oh-my-pi

What you will run into

You want one coding agent binary that can talk to any model provider without installing a heavy runtime — oh-my-pi is a single 183MB binary: CLI-first, brings any provider into your coding flow, with profiles and subagents. The two things people trip on: the binary download from GitHub direct is slow on mainland networks (must use the gh-proxy prefix), and it is 183MB — a self-contained binary with no runtime deps, so make sure disk and download stability are fine. When to use it:

• Text-mode single rounds for site docs (--print);
• Full coding sessions with your provider of choice (needs an API key);
• Multi-project isolation with profiles (--profile + --alias).

When not to use it: you do not want a 183MB binary, or you cannot provide any API key (local providers still need some endpoint).

Path: Quick fix (30s, one command) -> Step by step (skimmable) -> How to confirm it works (success criteria). In a hurry? Jump to Quick fix.

Why this happens

Single binary (Linux x86_64, no runtime deps): download + chmod + run. --print is the text-mode single round (needs an API key, e.g. ANTHROPIC_API_KEY, or --provider); agents unpack exports built-in subagents to ~/.omp/agent/agents (project form uses --project → ./.omp/agents); --profile work --alias omp-work creates an isolated alias (auth/sessions/settings/caches separated). Key concepts:

• --print: text-mode single round, script/pipe friendly;
• agents unpack: exports built-in subagents;
• profile isolation: separate auth/sessions/settings/caches per alias.

Where it writes: ~/.omp/ (logs/agents; written on run); project form writes ./.omp/agents.

Step by step

Step 1: Install the binary (why gh-proxy: mainland GitHub direct is slow)

Why: single 183MB binary, download via the gh-proxy prefix (mainland direct is slow). chmod +x and it runs, no runtime deps. Verify with —version after install.

curl -sL -o omp https://gh-proxy.com/https://github.com/can1357/oh-my-pi/releases/download/v18.0.11/omp-linux-x64
chmod +x omp
./omp --version

Expected output: omp/18.0.11 After install, confirm:

• --version prints omp/18.0.11;
• omp --help shows the full flags and tool list.

Stuck? How to recover:

• download slow/failed → confirm the network can reach gh-proxy; switch networks and retry;
• want it globally → put it on PATH (e.g. /usr/local/bin; note the 183MB single file).

Step 2: Non-interactive single round (--print, needs an API key; not verified here — no key)

Why: --print is the text-mode single round, good for site docs Needs an API key (--model specifies the model).

omp --print "explain this repo in one sentence" --model gpt-5.2

Expected output: model reply (text mode) After install, confirm:

• a model reply comes back with no key error.

Stuck? How to recover:

• missing key error → set ANTHROPIC_API_KEY etc., or --provider to a specific vendor;
• multi-project isolation → use --profile work --alias omp-work (auth/sessions/settings/caches separated).

Step 3: Unpack subagents + profile isolation (as needed)

Why: agents unpack exports built-in subagents (commands from —help, not verified); --profile work --alias omp-work creates an isolated alias (auth/sessions/settings/caches separated), good for multi-project/multi-vendor.

omp agents unpack

Expected output: exports built-in subagents to ~/.omp/agent/agents (project form uses --project → ./.omp/agents)

omp --profile work --alias omp-work

Expected output: creates the shell alias omp-work (isolated auth/sessions/settings/caches) After install, confirm:

• subagents appear under ~/.omp/agent/agents;
• the alias works in a new shell (or after sourcing the shell config).

Stuck? How to recover:

• agents unpack errors → commands from —help (not verified here), follow official docs;
• alias not active → confirm the shell config file was loaded (new terminal or source).

How to confirm it works

Step 1: Confirm the command and help surface

Why: omp --version printing omp/18.0.11 and omp --help showing the full flags/tool list mean the binary is complete and executable.

./omp --version
./omp --help

Expected output: omp/18.0.11; full flags and tool list Stuck? How to recover:

• version mismatch → re-download (note the 183MB single-file integrity);
• command not found → confirm the path and chmod +x.

Step 2: Confirm the call path (needs an API key, not verified here)

Why: --print returning a model reply means the binary + provider path both work; a missing-key error means the env vars are not set.

omp --print "explain this repo in one sentence" --model gpt-5.2

Expected output: model reply (text mode; not verified here — no API key) Stuck? How to recover:

• missing key error → set ANTHROPIC_API_KEY etc., or --provider to a specific vendor;
• want multi-project isolation → use --profile work --alias omp-work (auth/sessions/settings/caches separated).

Other environments

• Non-Linux x86_64: official binaries for other platforms (not verified here, same command surface); single binary with no runtime deps.
• Want it globally: put it on PATH (e.g. /usr/local/bin; note the 183MB single file).
• Write surface: writes ~/.omp/ (logs/agents) on run; project form writes ./.omp/ — own directories, no overlap with common tools.
• Runtime: full coding sessions need an API key; --print text mode suits site docs

Daily usage

Startup and entry

Call the CLI directly; entry omp --help.

Common operations

Operation 1: View the command surface (verified here)

omp --help

Expected output: USAGE + FLAGS (--model/--provider/--profile/--mode/--print etc.) + env surface (OMP_PROFILE/PI_CODING_AGENT_DIR) + tool list (read/bash/edit/write/task/browser etc.) Operation 2: Non-interactive single round (--print, needs an API key; not verified here — no key)

omp --print "explain this repo in one sentence" --model gpt-5.2

Expected output: model reply (text mode) Operation 3: Unpack subagents (not verified here — commands from —help)

omp agents unpack

Expected output: exports built-in subagents to ~/.omp/agent/agents (project form uses --project → ./.omp/agents) Operation 4: Profile isolation (multi-project/multi-vendor switching)

omp --profile work --alias omp-work

Expected output: creates the shell alias omp-work (isolated auth/sessions/settings/caches)

Data and directories

• Logs/subagents: ~/.omp/ (logs/agent/agents; written on run);
• Project form: ./.omp/agents (with --project).

Uninstall & cleanup

note: remove the single binary; own ~/.omp directory auto-deleted; project .omp/ cleaned manually as needed

rm -f /usr/local/bin/omp ~/.local/bin/omp
rm -rf ~/.omp
command -v omp >/dev/null 2>&1 && echo '残留: omp 仍存在' || echo 'oh-my-pi removed: OK'

Expected output: oh-my-pi removed: OK

Dependency warnings

• Version: [18.0.11, 18.0.11] locked (2026-08-31 upgrade retested: gh-proxy download 185.5MB + --version reports 18.0.11 + --help command surface complete, evidence）; full session not run (needs provider and account — zero-account discipline, same scope as collection).
• Environment: Linux x86_64; no runtime deps; single 183MB binary.
• Network: GitHub direct slow, must use the gh-proxy prefix (verified path).
• Write surface: ~/.omp/ (logs/agents; written on run); project .omp/.
• Runtime: full coding sessions need an API key (ANTHROPIC_API_KEY etc.).
• Co-install: conflict-matrix pairs on the matrix page (~/.omp own write surface, no overlap with common tools).

FAQ

• Q: Binary too big (183MB)? A: single self-contained binary (no runtime deps); download via the gh-proxy prefix.
• Q: --print reports missing key? A: set ANTHROPIC_API_KEY etc., or --provider to a specific vendor.
• Q: How to isolate multiple projects? A: --profile + --alias (e.g. --profile work --alias omp-work), auth/sessions/settings/caches separated.
• Q: Where to report problems? A: install/uninstall issues on this marketplace go through the entry feedback channel; project issues go to the author's repository.