Oh My Pi
Install, authenticate, verify, and run Oh My Pi through Karmas Coder.
Oh My Pi is available in Karmas Coder Stable and Beta. Karmas Coder connects to Oh My Pi through its omp executable and Agent Client Protocol mode. Oh My Pi owns the account, model routing, credentials, thinking levels, and provider service; Karmas Coder supplies the task, repository environment, transcript, approvals, review surfaces, and Git workflow around the session.
Install
Install Oh My Pi with the official installer on macOS or Linux:
curl -fsSL https://omp.sh/install | shHomebrew and Bun installs are also supported:
brew install can1357/tap/omp
bun install -g @oh-my-pi/pi-coding-agentVerify that the executable is available:
omp --versionIf omp is not on PATH, set the Oh My Pi binary path in Karmas Coder provider settings to the full path of the executable.
Authenticate
Start Oh My Pi interactively:
ompComplete the sign-in flow inside the terminal. Oh My Pi stores its user state under ~/.omp/ by default. Do not commit credentials or paste them into a task transcript.
Verify
From a disposable repository:
omp --version
omp models --jsonConfirm that omp models --json lists at least one model. This verifies the binary, provider credentials, and model catalog before Karmas Coder is involved.
Connect to Karmas Coder
Enable Oh My Pi
Open provider settings and confirm that Karmas Coder detects omp.
Confirm authentication
Run omp directly first so ~/.omp credentials exist. Karmas Coder reads the resulting model availability rather than duplicating the secret.
Refresh models and thinking levels
Oh My Pi publishes its full multi-provider catalog through omp models --json, with each model carrying its own thinking efforts inline. Confirm that the expected models appear before starting the task.
Thinking levels are off, minimal, low, medium, high, xhigh, and max. Availability varies per model.
Start a bounded task
Use a clean repository and conservative permissions. Review the selected autonomy or plan mode before allowing edits and commands.
Capabilities in Karmas Coder
Oh My Pi sessions can expose:
- Models from the
omp models --jsoncatalog and their thinking levels - Tool calls, command output, file changes, and assistant text
- Permission and autonomy controls supplied by the runtime
- Session configuration negotiated at startup
- Karmas Coder's terminal, browser, diff, checkpoint, worktree, and Git delivery surfaces
Karmas Coder applies Oh My Pi's model and thinking choices through ACP session configuration because command-line model flags are not authoritative in every ACP release.
Karmas Coder does not currently classify Oh My Pi as supporting native live-turn steering.
Updating
Use Oh My Pi's supported update path, then restart Karmas Coder. Create a new task after an update that changes ACP configuration, model discovery, authentication, or autonomy modes.
Troubleshooting
OMP is not detected
- Run
omp --versionfrom a fresh terminal. - Confirm the installer directory is on
PATH. - Check Karmas Coder's custom binary path.
- Restart Karmas Coder after installation or environment changes.
No models are available
Run omp directly and complete authentication so ~/.omp credentials exist, then confirm omp models --json returns models before refreshing Karmas Coder.
The model catalog differs between projects
Check the configured agent directory. A custom agent directory selects a different profile directory (auth, sessions, skills, models) for every Karmas Coder invocation through PI_CODING_AGENT_DIR.
Thinking levels are missing for a model
Update Oh My Pi, authenticate directly, and start a new Karmas Coder session. Thinking levels are advertised per model by the runtime; non-reasoning models expose none.
Official documentation
Continue with Your first task or Provider handoffs.