Skip to content

support for omp/pi harness #165

Closed
Closed

Description

@bchap1n

My team is 100% omp or pi harness on Windows 11. I am trying to push adoption of wmux but the feedback is that it is "only for Claude". It would be awesome if the user could select omp as the harness or wmux could auto-detect the harness and have total feature parity with Claude.

Activity

  1. amirlehmam commented on Aug 14, 2026

    @amirlehmam
    Owner

    Shipped in 1.0.0. omp is supported.

    "Only for Claude" was a fair reading and I'd rather fix the substance than argue with it. wmux has supported OpenCode since 0.8.0 and Kiro since 0.47.0, but Claude Code is the one with hooks, so it's the one where the sidebar lights up — and that's the visible difference your team would notice.

    What works now

    The wmux block is written to ~/.omp/agent/AGENTS.md — omp's user-scope file for the native discovery provider, which has the highest discovery priority of any provider, loaded for every session. So an omp session gets the same instructions Claude Code and OpenCode do:

    • wmux browser open/snapshot/click/type/… — drive the browser panel your team can actually watch, instead of a headless window
    • wmux markdown <file> — put a plan or a spec in a pane instead of dumping it into the terminal
    • wmux split / new-workspace / send — layout control from inside the agent
    • wmux report-agent — sidebar status (more on this below)

    It's spliced between markers, so anything you've written in that file yourself survives, and switching the integration off in Settings → General removes wmux's block and nothing else.

    The orchestrator can also launch omp workers now: WMUX_AGENT_CMD=omp and /wmux:orchestrate spawns omp in each pane.

    A deliberate choice worth knowing about: omp ships claude and agents-md discovery providers, so on a machine that also has Claude Code installed it would already have picked up wmux's CLAUDE.md block and appeared to work with no code from me at all. I didn't rely on that. It holds only while Claude Code is installed and claude isn't in your disabledProviders, and it would make wmux's behaviour on an omp-only machine depend on a competing tool being present. Your team is 100% omp; that shortcut would have broken for exactly you.

    The honest gap: sidebar status

    This is where parity is not yet total, and I'd rather say so than let you find it.

    omp has a genuinely good hook surface — session_start, turn_start/turn_end, agent_start/agent_end, and pre/post tool events map onto wmux's declared-state protocol almost one for one. Better than Kiro's, and arguably cleaner than Claude Code's.

    The problem is discovery: omp finds hooks in .omp/hooks/ inside a project, walking up from cwd. There's no global hook directory. Wiring the sidebar that way would mean wmux writing into every repository you open — which is precisely what issue #132 was filed about, and I'm not doing it again for a status indicator.

    So today omp panes report status the way any agent can without a plugin: the instruction block documents wmux report-agent, and an omp session that follows it will show Running / Needs you / Idle in the sidebar and can be answered from another pane with wmux answer-agent. That's declarative rather than automatic — it works when the agent cooperates, where Claude Code's hooks work whether it cooperates or not.

    The right fix is an omp extension, and omp's extension loading can be configured globally (~/.omp/agent/config.yml), which is the piece Kiro lacks. That would give omp full automatic parity — arguably better than Claude Code's, since turn_start is a first-class event rather than something I had to reconstruct from four terminal hooks (see #151). It's a separate piece of work from teaching omp that wmux exists, so it isn't in 1.0.0.

    If your team would use it, say so here and I'll prioritise it — and if anyone there wants to write it, an omp extension calling wmux report-agent on those five events is maybe 40 lines and I'll ship it in resources/.

    Trying it

    Install 1.0.0, launch it once (it rewrites the context files on startup), then start omp in a pane. wmux ping from inside the pane should answer pong; if omp says the command isn't found, that's #158 and 1.0.0 also fixes the guidance around it.

    Thanks for pushing on this rather than quietly writing wmux off. "My team says it's only for Claude" is more useful feedback than a feature request.

  2. bchap1n commented on Aug 15, 2026

    @bchap1n
    ContributorAuthor

    https://github.com/bchap1n/omp-wmux-extension
    working well for me, feel free to ship it in resources/
    thanks for the high quality response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions