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

@getmegabrain/cli

v7.4.18-mb.24

Published

An agentic coding assistant for your terminal. Ask in plain language, and it reads, edits and runs code in your project -- with 500+ models behind one account.

Downloads

3,869

Readme

MegaBrain CLI

An agentic coding assistant for your terminal. Ask in plain language, and it reads, edits and runs code in your project -- with 500+ models behind one account.

Website · Install · Gateway · Pricing

Install

npm install -g @getmegabrain/cli

Or run it once, without installing:

npx @getmegabrain/cli

Node.js 18 or later. The package pulls a single prebuilt binary for your platform.

Getting Started

Run megabrain in any project directory to launch the interactive TUI:

megabrain

Run a one-off task:

megabrain run "add input validation to the signup form"

Features

  • Code generation -- describe what you want in natural language
  • Terminal commands -- the agent can run shell commands on your behalf
  • 500+ AI models -- through the MegaBrain Gateway, or your own provider keys
  • MCP servers -- extend agent capabilities with the Model Context Protocol
  • Multiple agents -- plan, code, review, or define your own
  • Sessions -- resume previous conversations and export transcripts

Models and providers

Out of the box the only connected provider is the MegaBrain Gateway: sign in once and every model routes through it, with no provider API keys to manage.

Bringing your own keys works exactly as it does upstream. /connect in the TUI, or megabrain auth login, connects Anthropic, OpenAI, Google, GitHub Copilot, a local Ollama, or any OpenAI-compatible endpoint. Those providers appear alongside the gateway -- nothing is locked down.

Commands

| Command | Description | | -------------------------- | -------------------------- | | megabrain | Launch interactive TUI | | megabrain run "<task>" | Run a one-off task | | megabrain auth | Manage authentication | | megabrain models | List available models | | megabrain mcp | Manage MCP servers | | megabrain session list | List sessions | | megabrain session delete | Delete a session | | megabrain export | Export session transcripts |

Run megabrain --help for the full list.

What this is built on

MegaBrain CLI is a fork of Kilo CLI, which is itself a fork of OpenCode. Both are MIT licensed, and so is this. Our changes are kept as a reviewable patch set -- see MEGABRAIN.md in the repository.

Some internals still carry the upstream name on purpose: configuration lives in .kilo/ and ~/.config/kilo, and environment variables are KILO_*. Renaming them would break existing configs and make every upstream rebase more expensive than it is worth.

Links

License

MIT