omp-muse-bridge

An Oh My Pi plugin that registers an authenticated
Muse Code installation as the OMP model provider muse-code.

Muse owns tool execution. OMP displays its replies, reasoning, short activity summaries, and committed todo snapshots.
A persistent muse serve host keeps backend context between matching turns. The bundled muse-spark agent lets
OMP's built-in task tool delegate to Muse; no separate subagent extension or modified host is required.

Screenshots

Tool activity in OMP:

Muse's plan display:

These screenshots show the earlier panel layout. Plans now use a live widget and a saved per-turn transcript snapshot.

Requirements

• OMP 18.1.10 or later, including its @oh-my-pi/pi-ai, pi-catalog, pi-coding-agent, and pi-utils packages
• Muse on PATH, authenticated with muse login, with a populated local model catalog
• Bun 1.3.14 or later for development and the test runner

The bridge reads Muse's cache at $XDG_DATA_HOME/muse/model-catalog, or ~/.local/share/muse/model-catalog when
XDG_DATA_HOME is unset. It does not download or rebuild the catalog. Authentication alone does not prove the cache
is available: if it is missing, open Muse normally and verify its model picker and a normal turn before retrying OMP.
There is no catalog-refresh subcommand in the inspected Muse CLI help.

PI_MUSE_BINARY=/path/to/muse selects the executable for both the persistent host and exec fallback.

Install

omp plugin marketplace add LimpingNinja/omp-muse-bridge
omp plugin install omp-muse-bridge@omp-muse-bridge

Restart OMP afterwards. Extensions load at startup; /reload-plugins reloads skills, commands, and MCP, not this provider.

For delegation, run:

/muse-setup

This copies the bundled definition to <agentDir>/agents/muse-spark.md. The default is
~/.omp/agent/agents/muse-spark.md; OMP profiles and PI_CODING_AGENT_DIR change that location.

Rerun /muse-setup after plugin u