Oh My Pi

Install and launch

Install Oh My Pi and put omp on PATH. Complete Install and connect, using tokamak-stag for staging. Choose a Responses-compatible model. Oh My Pi and Pi are separate clients with different configuration contracts.

tokamak launch oh-my-pi --model YOUR_MODEL_ID --check
tokamak launch oh-my-pi --model YOUR_MODEL_ID

Use tokamak launch oh-my-pi --model for the picker. Native resume, RPC, thinking and profile options belong after --:

tokamak launch oh-my-pi --model YOUR_MODEL_ID -- --profile work

Configuration and model roles

Tokamak merges a tokamak Responses provider into the active agent registry, preferring models.yml, then models.yaml, then legacy models.json. The key is an environment-variable reference. Unrelated providers and model tuning remain in place.

A temporary settings overlay selects the Tokamak model for primary and background roles, including planning, titles and compaction helpers. Existing plugins, permissions and sessions stay in their native home. Plugins, remote compaction or explicitly independent providers can still use other routes. The same overlay turns off Oh My Pi's startup update check and hides the local and keyless providers it would otherwise probe on every start (Ollama, llama.cpp, LM Studio, the keyless discovery providers, and the built-in anthropic, opencode-go and opencode-zen) in Tokamak-launched sessions only; a provider you configured in the model registry stays enabled, and your own settings file is not changed. For 24-hour prompt-cache retention, set "omp_cache_retention_long": true in ~/.tokamak/config.json (off by default); use it only with models whose upstream accepts prompt_cache_retention, and check how that upstream prices retained caches.

Profiles and paths

The adapter respects OMP_PROFILE, OMP_CONFIG_DIR and the default profile's OMP_CODING_AGENT_DIR, with native PI_* aliases. If you also run Pi, explicitly select separate Oh My Pi paths using the OMP_* names.

Config directory names must be relative to your user home. For an absolute default-profile path, use the coding-agent directory setting. Export concrete directory variables explicitly when your project or mode-specific dotenv configuration could otherwise change them. The launcher refuses ambiguous interpolation or project-only redirects before registry writes.

Recovery and verification

The first original registry is kept beside the file with .tokamak-backup appended. Close Oh My Pi before restoring it manually. Invalid YAML or schema containers are rejected. The temporary overlay is removed after normal exit; forced termination may leave its private directory behind.

Tokamak meters server inference. With a resolved Tokamak identity the launcher also exports Oh My Pi's OTLP logs (runs, LLM requests and tool calls, grouped per launch in Insights); that activity is supplemental and never an extra charge. The recorded Windows check reached Tokamak with Oh My Pi 18.1.14 but received a 402 reservation refusal. That establishes routing, not successful inference. See troubleshooting.