Coding Agents & Terminal · recorded 2026-08-29 · applies to 1 tool(s) ✓ Verified

Problem: omp install <plugin> fails or behaves unexpectedly — the command in tutorials is outdated —— Trove problem library

Verified 2026-08-29omp install and omp plugin install are different — use the explicit subcommand `omp plugin install <name>` to avoid ambiguity.

Quick fix

# One-liner: use the explicit subcommand — least ambiguous
omp plugin install <plugin-name>

What you will run into

Following online tutorials, omp install <plugin-name> fails or behaves unexpectedly; the correct form is omp plugin install <plugin-name>. Tutorials and the actual command don't line up.

Why this happens

The npm page once gave the wrong instruction omp install (source: issue #36).

In 18.0.9, omp install has been implemented as an alias of omp plugin install (help text says "alias of plugin install/plugin link"), but old site docs still spread the wrong form, so mixing old and new causes confusion.

CommandStatus
omp plugin install <name>✅ Explicit correct form
omp install <name>⚠️ Alias (per help text); old tutorials still spread the wrong formomp install <name>⚠️ Alias (per help text); old tutorials still spread the wrong form

This is a "doc fossil" left by CLI surface evolution: early versions designed the install command as omp install (issue #36 points out the npm page said exactly that);

later the surface was redesigned into the plugin subcommand system, and omp install was kept as an alias so as not to break old muscle memory.

The real problem is tutorial propagation lag — tutorial authors used the old version, so the tutorials are older than the command surface, and both old and new forms circulate online.

omp --help is the source of truth for the command surface: the subcommands and alias annotations it lists (alias of plugin install/plugin link) are the actual behavior of the current version — newer than any tutorial.

Step by step

1. Explicitly use omp plugin install — Required

omp plugin install <name>

2. When unsure, check yourself first — Required

omp --help

Both install / plugin subcommands are listed (measured: install marked as "alias of plugin install/plugin link").

How to confirm it works

Help text and command behavior correct (measured output shape):

omp --help → lists both install (alias of plugin install/plugin link) and plugin subcommands (measured)
omp plugin install <name> → installs normally

Other environments

EnvironmentNotes
Old tutorialsomp install is the wrong-form source (issue #36)
18.0.9omp install is an alias; works but confusing
Unsureomp --help to check subcommands

Symptom

Following online tutorials, omp install <plugin> fails or behaves unexpectedly; the correct form is omp plugin install <plugin>.

Cause

The npm page once gave the wrong instruction omp install (source: issue #36); in 18.0.9 omp install is implemented as an alias of omp plugin install (help text says "alias of plugin install/plugin link"), but old site docs still spread the wrong form, mixing old and new causes confusion.

Solution

  1. Explicitly use omp plugin install <name> (least ambiguous).
  2. When unsure, check subcommands yourself with omp --help (both install and plugin are listed).
Verification Evidence
  • Verified in this marketplace (2026-08-28): omp --help output contains both install (marked alias of plugin install/plugin link) and the plugin subcommand.

Applicable tools (1)

This problem is linked from the tool pages below — reachable from either side.

oh-my-pi

Source & evidence

Recorded Verified ✓ VerifiedApplies to 1 tool(s)
Entries contain locally measured or reviewable-source solutions; unmeasured items are explicitly labeled.

← Coding Agents & Terminal domain | Problem Catalog Experience | Facing another issue? Go to the Helpdesk