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

@linzumi/cli

v1.0.5

Published

Linzumi CLI — point a Codex agent at the real code on your laptop, with your team watching and steering from shared threads.

Readme

Linzumi

▓▓╗     ▓▓╗▓▓▓╗   ▓▓╗▓▓▓▓▓▓▓╗▓▓╗   ▓▓╗▓▓▓╗   ▓▓▓╗▓▓╗
▓▓║     ▓▓║▓▓▓▓╗  ▓▓║╚══▓▓▓╔╝▓▓║   ▓▓║▓▓▓▓╗ ▓▓▓▓║▓▓║
▓▓║     ▓▓║▓▓╔▓▓╗ ▓▓║  ▓▓▓╔╝ ▓▓║   ▓▓║▓▓╔▓▓▓▓╔▓▓║▓▓║
▓▓║     ▓▓║▓▓║╚▓▓╗▓▓║ ▓▓▓╔╝  ▓▓║   ▓▓║▓▓║╚▓▓╔╝▓▓║▓▓║
▓▓▓▓▓▓▓░░░░░░░░╚▓▓▓▓║▓▓▓▓▓▓▓╗╚▓▓▓▓▓▓╔╝░░░░░░░░▓▓║▓▓║
╚═══▒▒▒@@@@@@@@▒▒═══╝╚══════╝ ╚════▒▒▒@@@@@@@@▒▒╝╚═╝
 ▒@@@@@@@@@@@@@@@@▒             ▒@@@@@@@@@@@@@@@@▒
@@@@@@@@@@@@@@@@@@@@@           @@@@@@@@@@@@@@@@@@@@@
   @@@@@@@@@@@@@@@                 @@@@@@@@@@@@@@@
          ║║                             ║║
          ║║                             ║║
          ║║        ()-().----.          ║║
          ║║         \"/` ___  ;_________║║_.'
          ║║          ` ^^   ^^          ║║
──────────╨╨─────────────··────··────────╨╨──────────────
secure mission control for all your agents on your computers

Linzumi is a lightweight, Slack-like chat built for native AI Engineering teams. Your coding agents run on your computer, reach you in your browser or on your phone, and build context for your team about what's going well, what's blocked, and what's ready to ship. Ship more, regret less.

Try it

Paste this into your terminal:

npx -y @linzumi/cli@latest signup

Linzumi will ask for your email, send you a sign-in code, help you pick the repos where Codex may work, start useful first tasks, and open Mission Control in your browser with the work already running.

Why a CLI

Your agent runs on the laptop you trust, with your real env vars, your real dotfiles, and your real branches. No "works in the sandbox VM, breaks in your repo" surprises. The chat side runs in your browser; the work side runs locally. This npm package is the local half.

What you'll have in three minutes

  • A Linzumi workspace in your browser.
  • A local Commander connected to one trusted project folder.
  • A live Coding agent thread your team can watch and steer.
  • Optional browser editor and preview forwarding for the running app.

Manual Runner Setup

Install the CLI or run it with npx:

npm install -g @linzumi/cli@latest
npx -y @linzumi/cli@latest signup
npx -y @linzumi/[email protected] --version
linzumi --version

Start a local runner from a trusted folder:

linzumi paths add ~/code/my-app
linzumi start ~/code/my-app

For explicit runner roots, pass a comma-separated allowlist:

linzumi start ~/code/my-app --allowed-cwd <paths>

For non-production Linzumi servers, connect accepts either API URL flag:

linzumi connect --linzumi-url ws://127.0.0.1:4140 --workspace default --allow-port-forwarding-by-default

Agent-first launch path

The fastest path is the npx -y @linzumi/cli@latest signup command above. It signs you in, lets you trust local projects, connects the Commander, and starts the first visible Coding agent threads.

What just happened

Linzumi keeps the browser/chat surface separate from the local work surface. The CLI authenticates your local Commander, publishes runner capabilities, and lets Kandan ask that Commander to start Codex inside trusted folders only.

MCP for coding agents

Commander-started Codex sessions are preconfigured with a local MCP server named linzumi. It lets the agent use the same approved local-runner auth to read the scoped Linzumi message, thread, or channel context, and to send a bounded DM to the Commander owner when configured.

Manual MCP commands are available for other MCP-compatible agents:

linzumi mcp doctor --api-url https://serve.linzumi.com --workspace <workspace> --channel <channel>
linzumi mcp config --api-url https://serve.linzumi.com --format codex
linzumi mcp config --api-url https://serve.linzumi.com --format claude-code
linzumi mcp server --api-url https://serve.linzumi.com

The shipped tools are linzumi_get_message, linzumi_get_thread, linzumi_get_channel, and linzumi_dm_owner.

Three things to try first

  • Ask the Coding agent to make a small UI change and watch the thread.
  • Open the browser editor from the thread controls.
  • Share the preview URL with a teammate or your phone.

Working as a team

Use the Linzumi thread as the shared source of truth. Humans can reply, steer, interrupt, or inspect output while the actual commands still run on the trusted local machine.

Trusted folders

Linzumi only edits inside folders you've explicitly trusted.

linzumi paths add ~/code/my-app

The trust list lives at ~/.linzumi/config.json. The bootstrap agent adds /tmp/hello_linzumi for you on first run. For linzumi connect, the selected --cwd is also trusted for that runner process.

When something looks wrong

Run linzumi --help or reconnect with linzumi start ~/code/my-app. If the browser says no runner is connected, check that the terminal running the Commander is still open and that the folder is listed in ~/.linzumi/config.json.


Slack-shaped on the surface. A multiplayer compiler underneath.

linzumi.com · agents.md ·