Tejus connects to Oh My Pi through its omp executable, running omp acp and talking to it over the Agent Client Protocol (ACP). Oh My Pi owns the account, model routing, credentials, thinking levels, and provider service; Tejus supplies the task, repository environment, transcript, approvals, review surfaces, and Git workflow around the session.

Install

Follow the Oh My Pi quickstart. With Bun installed, you can install it from PowerShell:

bun install -g @oh-my-pi/pi-coding-agent

Verify that the executable is available from a new PowerShell window:

omp --version

If omp is not on PATH, set Oh My Pi binary path in Oh My Pi's Runtime section under Settings → Agent providers → Provider tools to the full path of the executable.

Authenticate

In Tejus, open Settings → Agent providers, expand Oh My Pi under Provider tools, and click Sign in. Tejus starts omp in a terminal window; complete any startup prompts, then click Sign-in options (which sends /login) to choose a model provider and authenticate. You can also start it yourself:

omp

and type /login. Oh My Pi stores its credentials, sessions, skills, and models in its agent directory, %USERPROFILE%\.omp\agent 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 Tejus is involved.

Connect to Tejus

Enable Oh My Pi

Open Settings → Agent providers, keep Oh My Pi enabled under Provider activity, and click Refresh status. Tejus does not read Oh My Pi's sign-in state, so a ready status means the CLI was found.

Confirm authentication

Sign in to omp first so its credentials exist. Tejus reads the resulting model availability rather than duplicating the secret.

Check models and thinking levels

Tejus reads Oh My Pi's multi-provider catalog from omp models --json; each model carries its own thinking levels. Confirm that the expected models appear before starting the task.

Thinking levels are off, minimal, low, medium, high, xhigh, and max, and availability varies per model. Model roles you pin in Oh My Pi's configuration can also use auto.

Start a bounded task

Use a clean repository and conservative permissions. Review the selected permission mode or Plan mode before allowing edits and commands.

Capabilities in Tejus

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
Slash commands advertised by the runtime
Plan mode, when the installed Oh My Pi advertises it
Permission controls supplied by the runtime
Tejus's terminal, browser, diff, checkpoint, worktree, and Git delivery surfaces

Tejus applies Oh My Pi's model and thinking choices through ACP session configuration rather than command-line flags.

Context compaction, usage limits, and live steering of a running Oh My Pi turn are not supported.

Updating

Use Oh My Pi's supported update path, then restart Tejus. Tejus does not run Oh My Pi updates for you. Create a new task after an update that changes ACP configuration, model discovery, authentication, or modes.

Troubleshooting

Oh My Pi is not detected

Tejus shows “OMP CLI (omp) is not on PATH. Install it to use the OMP provider.”

Run omp --version from a new PowerShell window.
Confirm the install folder (for Bun, %USERPROFILE%\.bun\bin) is on PATH.
Check the Oh My Pi binary path in Tejus.
Restart Tejus after installation or environment changes.

Oh My Pi