Connect AIWG to Oh My Pi

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

Status: Experimental. AIWG currently qualifies Oh My Pi 18.1.10 on

Linux x64. OMP is a separate provider from the Pi Coding Agent harness at pi.dev.

For the complete first-time journey, start with Install, Connect, and Verify.

Install OMP from its upstream instructions, install AIWG, then open a terminal at the project root:

Use AIWG to complete this documented outcome: Install OMP from its upstream instructions, install AIWG, then open a terminal at the project root
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Start or reopen OMP from that project. Ask it to verify the project root, `.omp/AGENTS.md`, `.omp/agents/`, `.omp/prompts/`, `.omp/rules/`, and the one-level Agent Skills under `.agents/skills/`. It should confirm that `WORKSPACE.md` and `AIWG.md` are loaded through the native OMP bootstrap before claiming the session is fully connected.

Provider names have different meanings

• `aiwg ... the provider option omp` selects AIWG's OMP deployment adapter.
• `omp the model option <backend>/<provider>/<model>` selects an OMP model.
• `oh-my-pi` is an AIWG alias for `omp`.

For example, an OMP process may use an OpenRouter model while AIWG still uses the `omp` provider selector. Keep `OPENROUTER_API_KEY` in the process environment or provider credential store; do not write it to project files, receipts, transcripts, or command history.

Profiles and complete skill copies

The default project deployment keeps the startup surface small: kernel skills are copied to `.agents/skills/`, while the standard corpus remains available through the agent’s capability search and the agent’s stable-asset loader.

Use AIWG to complete this documented outcome: The default project deployment keeps the startup surface small: kernel skills are copied to .agents/skills/, while the standard corpus remains available through the agent capability search and the agent stable-asset loader.
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

`OMP_PROFILE` takes precedence over `PI_PROFILE`. OMP and Pi can coexist; AIWG keeps their provider identities and native directories separate and preserves operator-owned resources in their shared `.agents/skills/` surface.

Verify and maintain

Use AIWG to complete this documented outcome: Verify and maintain
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Set `AIWG_OMP_BIN` if `omp` is outside `PATH`. A missing model catalog is an error rather than an empty successful result; check the selected profile, backend credentials, and OMP version.

See the full OMP provider guide for native agents, MCP, profiles, runtime execution, teams, sessions, ownership-safe removal, troubleshooting, support limits, and the verification baseline.