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

@bytehumi/swarmcode

v0.1.1

Published

Multi-agent AI coding CLI — coordinate Claude, Codex, Gemini, Kimi, and more as a unified dev team

Readme

swarmcode

Run multiple AI coding agents as one team

Claude plans. Codex implements. Gemini researches. All from one terminal.

npm license node

Install

npm install -g @bytehumi/swarmcode

Get started

swarmcode init    # detect CLIs, pick brain + agents
swarmcode         # launch the swarm

What happens when you run it

You type a task. The brain (Claude, Codex, or whichever you picked) splits the work into waves and fires off multiple agents in parallel:

Wave 1 - Codex scaffolds the project

Wave 2 - Codex builds components, Gemini writes types, Kimi creates hooks (parallel)

Wave 3 - Codex wires everything together

Verify - Brain checks: builds? runs? all connected?

Each wave commits to git. You see the diff after every step.

Agents

| | Agent | What it does | CLI | |---|---|---|---| | Brain | Claude Code | Plans, reviews, coordinates the swarm | claude | | Brain | Codex CLI | Can also be the brain, or an implementer | codex | | | Gemini CLI | Research, code generation, analysis | gemini | | | Kimi Code | Implementation, file operations | kimi | | | Open Code | Multi-model coding | opencode | | | Aider | Pair programming with git | aider | | | Ollama | Local, private models | ollama | | | Custom | Any CLI that takes a prompt | your-cli |

Any agent can be the brain or a sub-agent. You choose during swarmcode init.

Commands

| Command | Description | |---|---| | swarmcode | Interactive mode | | swarmcode init | Setup wizard | | swarmcode run "task" | One-shot mode | | swarmcode plan "task" | Dry run | | swarmcode providers | List agents | | swarmcode providers --test | Health check agents | | swarmcode config | View config |

How orchestration works

Plan, check, execute. The brain follows a strict loop:

  1. Analyze the codebase
  2. Plan - break work into small tasks, assign to agents
  3. Check - validate the plan before running (dependencies, file conflicts)
  4. Execute - fire agents in parallel waves
  5. Commit + diff - atomic git commit per wave
  6. Verify - do files exist? real code? all wired? builds clean?
  7. Fix - if broken, run a fix wave
  8. Repeat until done

Parallel waves - independent tasks run at the same time across different agents. Wave 2 doesn't start until Wave 1 finishes. Two agents never touch the same file in one wave.

Atomic commits - every wave produces a git commit with a full diff, so you always know what changed and which agent did it.

Verification - after all waves, the brain checks from your perspective: files exist, code is real (not stubs), everything is wired together, and it builds without errors.

Auto-fix vs escalate - the brain auto-fixes bugs, missing deps, and type errors. It escalates architectural changes to you.

Config

.swarmcode.yml in your project:

version: 1

orchestrator:
  command: claude

agents:
  codex-cli:
    displayName: Codex CLI
    command: codex
    args: ["exec", "{{prompt}}", "-a", "on-request", "--sandbox", "danger-full-access", "-C", "."]
    capabilities: [implementation, code-writing, bug-fixing, refactoring, testing]
    role: Code implementer
    enabled: true

Add any CLI as a custom agent:

agents:
  my-model:
    displayName: My Model
    command: ollama
    args: ["run", "codellama", "{{prompt}}"]
    capabilities: [implementation, code-writing]
    role: Local code generation
    enabled: true

Development

git clone https://github.com/niladri-hazra/swarmcode.git
cd swarmcode
npm install
npm test
npm run build

MIT License • Niladri Hazra@bytehumi

If this helped you, give it a star :)