npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

oh-my-codebuddy

v0.12.4

Published

Multi-agent orchestration layer for CodeBuddy CLI

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tienchingtienching

Keywords

codexopenaicliagentsorchestrationmulti-agent

Readme

oh-my-codebuddy (OMB)

npm version License: MIT Node.js Discord

oh-my-codebuddy is a multi-agent orchestration layer for CodeBuddy CLI workflows.

It keeps the underlying coding agent as the execution engine, then adds:

  • a guided workflow layer ($deep-interview → $ralplan → $team / $ralph)
  • reusable skills and role prompts
  • durable team runtime with tmux/worktree orchestration
  • MCP/CLI parity for state, memory, trace, and code-intel surfaces
  • repository guidance scaffolding through AGENTS.md

Primary command: omb

Website: https://tienching.github.io/oh-my-codebuddy/ Docs: Getting Started · Agents · Skills · Integrations · OpenClaw guide · Demo

What this project actually does

OMB is not a replacement model runner. It is the orchestration/runtime layer around your coding CLI workflow.

In practice, OMB gives you:

  • A default workflow
    • $deep-interview for clarification
    • $ralplan for plan approval and tradeoff review
    • $ralph for persistent single-owner completion loops
    • $team for coordinated parallel execution
  • A durable team runtime
    • omb team ...
    • omb team status
    • omb team resume
    • omb team shutdown
  • Read-only repo exploration and shell helpers
    • omb explore --prompt "..."
    • omb sparkshell ...
  • Install / repair / support surfaces
    • omb setup
    • omb doctor
    • omb uninstall
    • omb hud
  • Stateful project runtime
    • primary runtime/state under .omb/
    • compatibility for older project state is still preserved where needed

Recommended environment

OMB is primarily designed for:

  • macOS or Linux
  • Node.js 20+
  • tmux available
  • a compatible coding CLI already installed and authenticated

Native Windows is supported less aggressively than the macOS/Linux path. If you want team mode on Windows, WSL2 is usually the safer option.

Install

1. Install your coding CLI

Make sure your preferred coding CLI is already installed and authenticated before using OMB.

2. Install OMB

npm install -g oh-my-codebuddy

3. Run setup

omb setup

Setup installs and refreshes:

  • prompts
  • skills
  • native agent configs
  • scoped AGENTS.md
  • config and managed hooks
  • HUD / notification wiring

4. Smoke-test the install

Do not stop at setup alone. Verify the runtime surfaces you actually plan to use:

omb doctor
omb --help
omb team --help
omb explore --prompt "find where team state is written"

If you plan to use team mode, also verify tmux is available:

tmux -V

Fast start

Start an interactive session:

omb --madmax --high

If you explicitly want the leader session inside tmux:

omb --tmux --madmax --high

Then use the canonical workflow inside the session:

$deep-interview "clarify the task and constraints"
$ralplan "turn the clarified request into an approved plan"
$ralph "carry the approved plan to completion"
$team 3:executor "execute the approved plan in parallel"

Rule of thumb

  • use $deep-interview when requirements are unclear
  • use $ralplan before non-trivial implementation
  • use $ralph when one owner should keep pushing until verified completion
  • use $team when the work benefits from parallel lanes

Core commands

Session / runtime

omb
omb --tmux
omb resume
omb doctor
omb cleanup
omb version

Team runtime

omb team 3:executor "fix the failing tests with verification"
omb team status <team-name>
omb team resume <team-name>
omb team shutdown <team-name>
omb team api --help

Exploration / shell helpers

omb explore --prompt "find where team state is written"
omb sparkshell git status
omb sparkshell --tmux-pane %12 --tail-lines 400

Setup / uninstall

omb setup
omb uninstall

Other surfaces

omb ask --help
omb autoresearch --help
omb agents --help
omb agents-init .
omb state --help
omb hooks --help
omb tmux-hook --help
omb hud --help

Repository layout and runtime data

Tracked project assets

OMB ships and maintains project assets such as:

  • skills/
  • prompts/
  • templates/
  • agents/
  • .codex/ project skill/prompt/agent content where applicable

Runtime / state assets

Primary runtime state lives under:

  • .omb/state/
  • .omb/plans/
  • .omb/logs/
  • .omb/notepad.md
  • .omb/project-memory.json

Compatibility support for older project state is still present in parts of the runtime, but the current primary path is .omb/.

Platform notes

tmux install

| Platform | Install | | --- | --- | | macOS | brew install tmux | | Ubuntu/Debian | sudo apt install tmux | | Fedora | sudo dnf install tmux | | Arch | sudo pacman -S tmux | | Windows (native) | winget install psmux | | Windows (WSL2) | sudo apt install tmux |

Why tmux matters

The durable team runtime depends on tmux-style pane/session orchestration for the best experience. That is why macOS/Linux remains the recommended default.

Typical workflow

  1. omb setup
  2. launch omb --madmax --high
  3. clarify with $deep-interview
  4. approve with $ralplan
  5. execute with $ralph or $team
  6. inspect/monitor with omb team status, omb hud, omb doctor, omb trace, or MCP parity surfaces as needed

Documentation

Languages

Community

  • Discord: https://discord.gg/PUwSMR9XNk
  • npm: https://www.npmjs.com/package/oh-my-codebuddy
  • GitHub issues: https://github.com/Tienching/oh-my-codebuddy/issues