OMP CLI still appears as unknown/plain shell instead of an agent

[riccardo-algorime]

Is this a reproducible bug?

• I confirm this is a reproducible bug, not a feature request, idea, question, contribution proposal, or direction check.

Current behavior

Running omp inside a Herdr pane can still appear as an unrecognized/plain shell process instead of an OMP agent row in the sidebar.

This looks unresolved from the public tracker: #80 (Feature Request: Add agent detection support for omp CLI) is closed, but a new comment on 2026-06-03 reports that omp still is not detected as an agent. I also checked open issues for omp, oh-my-pi, and Oh My Pi; I did not find an open issue tracking this.

There is also user-facing ambiguity because the current docs describe OMP integration support (herdr integration install omp), while the supported-agent detection path still appears to treat omp differently from agents that are detected automatically.

Expected behavior

A pane whose foreground agent is Oh My Pi / OMP should be visible to Herdr as an agent, not as ordinary shell activity.

At minimum, one of these should be true and clearly documented:

1. omp is recognized by process detection, so users get baseline sidebar state out of the box, similar to other supported agent CLIs; or
2. OMP is explicitly integration-only, and Herdr guides users to install/check herdr integration install omp when an omp process is running but no OMP authority events are arriving.

The ideal behavior is first-class OMP support:

• omp foreground process is labeled as omp in the agent panel.
• Screen heuristics provide a safe fallback when the native integration is not installed or not loaded.
• The native OMP integration remains the authority when installed and reports semantic state through the socket API.
• herdr integration status makes it obvious whether the OMP integration is installed in the path that OMP actually loads.

Reproduction

1. Start Herdr.
2. Open a pane.
3. Run omp in that pane.
4. Observe the agent/sidebar state.

Observed by users: the pane is not detected/displayed as an OMP agent. This is also consistent with the still-open user report in the comments on closed issue #80.

Useful checks while reproducing:

herdr integration status
herdr integration install omp
herdr integration status
which omp

If OMP is intended to work only after integration installation, please make that requirement visible in the CLI/docs and consider surfacing a diagnostic when Herdr sees an omp process without OMP integration events.

Impact

Oh My Pi users lose the main Herdr value proposition for that pane: at-a-glance agent awareness. The pane can look like ordinary terminal activity even though a supported coding agent is running, so users cannot reliably see whether OMP is idle, working, blocked, or done from the sidebar.

This is especially confusing because related OMP support work was closed as merged in #80, and the docs mention herdr integration install omp.

Related issues / context

• Feature Request: Add agent detection support for omp CLI #80 — requested omp CLI detection; closed after OMP integration was merged, but a later comment reports detection still failing.
• pi integration installs to ~/.pi/agent/extensions but oh-my-pi (OMP) only discovers from ~/.omp/agent/extensions #223 — older OMP extension-path issue around ~/.pi vs ~/.omp; closed as not planned, but it shows users can silently end up with an integration that does not load if paths are wrong.
• Current docs mention herdr integration install omp and state that OMP reports semantic state but does not provide native session restore.

Suggested acceptance criteria

• Running omp in a Herdr pane results in an OMP/agent row instead of unknown/plain shell activity.
• If the native OMP integration is missing or not loaded, Herdr either falls back to process/screen detection or clearly tells the user what to install/check.
• herdr integration status distinguishes Pi and OMP paths and reports the OMP-loaded location clearly.
• Add a regression test for omp process identification or for the chosen diagnostic behavior.

Environment

• Herdr version: unknown from public report; please verify on latest stable and preview/master
• Update channel: unknown
• Operating system: unknown
• Terminal: unknown
• Shell, if relevant: unknown
• Relevant config, if any: OMP installed as omp; OMP integration may or may not be installed

[kangal-bot]

hi @riccardo-algorime, thanks for opening this.

this issue does not appear to use the full bug report template. herdr issues are only for reproducible bugs and maintainer-created or maintainer-converted work items.

bug reports must include the reproducible-bug confirmation, current behavior, expected behavior, reproduction, impact, and environment fields with herdr version, operating system, and terminal.

feature requests, ideas, questions, contribution proposals, and direction checks belong in discussions:
https://github.com/ogulcancelik/herdr/discussions

please read the contributing guidelines before opening issues or prs:
https://github.com/ogulcancelik/herdr/blob/master/CONTRIBUTING.md

closing this so the issue tracker stays limited to actionable bug reports.