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

@mauribadnights/claunch

v0.4.0

Published

Universal agent launcher for Claude Code — manage project-specific agents from anywhere

Readme

claunch

Universal agent launcher for Claude Code. Manage project-specific agents from anywhere.

npm version License: MIT

Why I Built This

I don't know about you, but as I started making different agents for different things, and was simultaneously working on a hundred different projects, I got tired of constantly running long commands to navigate to the directory I want and call the agent I need. At first I fixed it using shell aliases, but that got messy fast and I couldn't keep track of all of them:

alias claude-cto="cd ~/projects/myapp && claude --agent cto"
alias claude-designer="cd ~/projects/myapp && claude --agent designer"
alias claude-devops="cd ~/infra && claude --agent devops"
# ... 15 more aliases that I'll definitely forget about ...

So I built a smart fuzzy agent and project picker to get into my projects faster than ever.

The Fix

npm install -g @mauribadnights/claunch
$ claunch

agent > _                    |  ▐▛███▜▌
> cto          [myapp]       | ▝▜█████▛▘  hey!
  designer     [myapp]       |   ▘▘ ▝▝
  devops       [infra]       |
  builder      [global]      |   cto
  (plain claude) [global]    |   Technical architect and
                             |   engineering lead
6 | type to filter | enter   |

One command. Split-panel TUI. Fuzzy search. No aliases.

Quick Start

# Install
npm install -g @mauribadnights/claunch

# Register a project (auto-discovers agents from .claude/agents/)
claunch add myapp ~/projects/myapp
claunch add infra ~/infrastructure

# Or auto-discover everything under a root
claunch scan ~/projects

# Launch interactively
claunch

# Or directly
claunch myapp cto

How It Works

claunch reads agent definitions from each project's .claude/agents/ directory -- the same place Claude Code already looks for agents. No new config format to learn.

~/projects/myapp/
├── .claude/
│   └── agents/
│       ├── cto.md          <- claunch discovers these
│       ├── designer.md
│       └── devops.md
├── src/
└── ...

When you run claunch myapp cto, it:

  1. cds to ~/projects/myapp/
  2. Runs claude --agent cto (plus any default flags you've configured)

The interactive TUI goes further -- after picking an agent, you get a second panel to pick which directory to launch in, with fuzzy search on both. It tracks what you use most with frecency ranking (Mozilla-style exponential decay, 14-day half-life) so your favorites float to the top over time.

Usage

claunch                              Interactive project/agent picker
claunch <project>                    List agents for a project
claunch <project> <agent> [args...]  Launch an agent in project context

claunch add <name> <dir>             Register a project
claunch remove <name>                Unregister a project
claunch scan [root-dir]              Auto-discover projects
claunch list                         List all projects (non-interactive)
claunch init                         Create default config
claunch update                       Update claunch to the latest version
claunch completions <zsh|bash|fish>  Print shell completions

Configuration

Config lives at ~/.claunch/config.yaml:

defaults:
  claude_flags: []  # flags appended to every launch

scan_roots:         # directories for `claunch scan`
  - ~/projects
  - ~/work

projects:
  myapp:
    dir: ~/projects/myapp
  infra:
    dir: ~/infrastructure
    agents_dir: ~/shared-agents  # override agent discovery path

Agent Overrides

For agents that need a different working directory or extra flags:

projects:
  myapp:
    dir: ~/projects/myapp
    overrides:
      cto-code:
        dir: ~/projects/myapp/packages/core  # launch from subdirectory
        add_dirs:
          - ~/projects/myapp/docs            # --add-dir flag
        agent: cto                           # use the cto agent definition

Shell Completions

Tab-complete project and agent names:

# zsh
eval "$(claunch completions zsh)"

# bash
eval "$(claunch completions bash)"

# fish
claunch completions fish > ~/.config/fish/completions/claunch.fish

Requirements

  • Node.js >= 18
  • Claude Code installed and available as claude in PATH

License

MIT