omp

🔌 Pi Plugin Compatibility

Golden baseline for running legacy Pi-named plugins under the OMP runtime.

Many plugins still say Pi because they target the upstream Pi plugin API. In this workspace, OMP is the runtime; keep the PI_* knobs those plugins actually read.

Golden baseline# 

/home/mc/.env                         = Pi-plugin compatible config
/home/mc/.local/bin/omp-plugin-env    = Pi spawn → OMP bridge
/home/mc/.omp/agent                   = OMP agent state

Required habits#

  1. Keep PI_* environment names unless plugin docs explicitly support OMP_*.
  2. Force spawned child sessions through /home/mc/.local/bin/omp-plugin-env.
  3. Pin session state with PI_CODING_AGENT_DIR=/home/mc/.omp/agent.
  4. Use explicit env-file paths when supported.
  5. Restart OMP after config changes.
  6. Check whether saved plugin config overrides environment config.
  7. Avoid plugin source patches unless the plugin is actually broken.
  8. Keep secrets out of docs, logs, Discord, and commits.

Fast fix matrix#

Symptom Cause Fix
Plugin tries to run pi Default spawn command Use /home/mc/.local/bin/omp-plugin-env.
Launcher says no secret Env missing at process boot Set launcher secret in env, then restart OMP.
/new opens wrong runtime Spawn command wrong Set OMP wrapper as spawn command.
Child session loses config Wrong CWD/env Use --allow-home and explicit env-file path.
Config changes ignored Plugin read config once Restart OMP.

Security minimum#

A private Discord bot and minimal allowlists are mandatory. If external access is required, put it behind HTTPS, auth, and a launcher secret.

Sources: docs/omp-pi-plugin-cheatsheet.md, docs/omp-coms.md.