Oh My Pi is available in Orutta Stable and Beta. Orutta 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; Orutta 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 | sh

Homebrew and Bun installs are also supported:

brew install can1357/tap/omp
bun install -g @oh-my-pi/pi-coding-agent

Verify that the executable is available:

omp --version

If omp is not on PATH, set the Oh My Pi binary path in Orutta provider settings to the full path of the executable.

Authenticate

Start Oh My Pi interactively:

omp

Complete 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 --json

Confirm that omp models --json lists at least one model. This verifies the binary, provider credentials, and model catalog before Orutta is involved.

Connect to Orutta

Enable Oh My Pi

Open provider settings and confirm that Orutta detects omp.

Confirm authentication

Run omp directly first so ~/.omp credentials exist. Orutta 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 Orutta

Oh My Pi sessions can expose:

Models from the omp models --json catalog 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
Orutta's terminal, browser, diff, checkpoint, worktree, and Git delivery surfaces

Orutta 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.

Orutta does not currently classify Oh My Pi as supporting native live-turn steering.

Updating

Use Oh My Pi's supported update path, then restart Orutta. Create a new task after an update that changes ACP configuration, model discovery, authentication, or autonomy modes.

Troubleshooting

OMP is not detected

Run omp --version from a fresh terminal.
Confirm the installer directory is on PATH.
Check Orutta's custom binary path.
Restart Orutta after installation or environment changes.

Oh My Pi