@jackice/omp-extensions
v0.1.4
Published
Extensions for the omp coding agent - subset shared with pi-extensions via symlinks, excludes features omp provides natively (goal, plan-mode, btw)
Readme
@jackice/omp-extensions
A collection of extensions for omp (Oh My Pi) coding agent, published and evolved independently from pi-extensions.
Extension list
| Extension | Description |
|---|---|
| notify.ts | Desktop notifications: alert when the agent completes / waits for user selection / errors. Notification channels degrade by priority: OSC 777 (Ghostty, iTerm2, WezTerm, incl. tmux passthrough) → growlrrr → osascript |
| review.ts | Code review workflow: /review starts a review, /end-review ends it and returns to the original position. Supports PR references, session-tree navigation, and branch summaries |
| permission-gate.ts | Confirmation for dangerous shell commands: rm -rf, sudo, chmod/chown 777, git push, gh/glab repository management operations |
| uv.ts | Python toolchain management: intercepts pip/poetry, rewrites python/python3 to uv run |
| whimsical.ts | Replaces working messages in the agent's thinking with random witty copy |
| answer/ | QnA: /answer extracts a question from the context and answers interactively in an editor form |
Installation
Use as an omp plugin. Install it in the omp plugin directory (e.g. ~/.omp/plugins):
cd ~/.omp/plugins
npm install @jackice/omp-extensionsThen enable the plugin in omp-plugins.lock.json (or let the omp plugin manager discover it automatically).
Requirements
- Runtime: omp 17.2.10+ (depends on the runtime-bundled
@earendil-works/pi-tuiand@earendil-works/pi-coding-agentAPIs) - Optional dependencies:
grrr(growlrrr, desktop-notification fallback path),uv(python redirection)
Development
This package is an independently published extension collection, decoupled from pi-extensions — the two codebases evolve separately and changes are not synced.
The code ships as TypeScript source directly (no build step); extension files are loaded by the runtime according to the omp.extensions list in package.json. Note: theme/component calls inside the package must match the runtime-bundled pi-tui API shape (the types published on npm may be stale); after changing any pi-tui-related calls, verify in a real omp session.
