Summary
Users installing the senpi-based omo-ai@beta can still execute a cached legacy omo wrapper in the same zsh session. The installation succeeds, but omo shows the legacy oh-my-opencode command help instead of launching the bundled senpi CLI.
Primary packaging issue: code-yeongyu/oh-my-openagent#6686
Reproduction
- Have
~/.local/bin/omo from legacy OMO and invoke it once in zsh.
- Keep the npm global bin directory earlier in PATH.
- Run
npm i -g omo-ai@beta.
- Run
omo in the same zsh session.
Observed:
cached=/Users/jgp/.local/bin/omo
omo --version => 4.19.4
Usage: oh-my-opencode [options] [command]
After rehash:
omo --version => 2026.8.9-2
The latter is the expected bundled @code-yeongyu/senpi version, confirming that the senpi package itself is installed and runnable.
Impact
Migration users may conclude that senpi/omo-ai was not installed, reinstall repeatedly, or report a false binary/package conflict. which -a omo can show the npm binary first while zsh still executes its cached path, making diagnosis non-obvious.
Workaround
Opening a new shell also clears the stale command resolution.
Requested coordination
Please keep this issue as the senpi-side consumer report and cross-reference the packaging fix in code-yeongyu/oh-my-openagent. The actionable launcher/install changes belong to that repository; no senpi core behavior change has been identified.
Environment: macOS Darwin 25.5.0 arm64, zsh, Node.js 24.14.0, omo-ai@5.0.0-0.beta.3. Internal tracking: LAB-39.
Summary
Users installing the senpi-based
omo-ai@betacan still execute a cached legacyomowrapper in the same zsh session. The installation succeeds, butomoshows the legacyoh-my-opencodecommand help instead of launching the bundled senpi CLI.Primary packaging issue: code-yeongyu/oh-my-openagent#6686
Reproduction
~/.local/bin/omofrom legacy OMO and invoke it once in zsh.npm i -g omo-ai@beta.omoin the same zsh session.Observed:
After
rehash:The latter is the expected bundled
@code-yeongyu/senpiversion, confirming that the senpi package itself is installed and runnable.Impact
Migration users may conclude that senpi/omo-ai was not installed, reinstall repeatedly, or report a false binary/package conflict.
which -a omocan show the npm binary first while zsh still executes its cached path, making diagnosis non-obvious.Workaround
Opening a new shell also clears the stale command resolution.
Requested coordination
Please keep this issue as the senpi-side consumer report and cross-reference the packaging fix in
code-yeongyu/oh-my-openagent. The actionable launcher/install changes belong to that repository; no senpi core behavior change has been identified.Environment: macOS Darwin 25.5.0 arm64, zsh, Node.js 24.14.0,
omo-ai@5.0.0-0.beta.3. Internal tracking: LAB-39.