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

cruise-code

v0.1.0

Published

Cruise Codex plugin and terminal client

Readme

Cruise

Cruise is a small Codex plugin and optional terminal launcher. Its five intent-based skills help Codex use the right amount of planning and autonomy for a coding task without introducing a separate workflow system.

Cruise keeps only one local record: .cruise/ORIGIN.md, containing the exact request that started the most recent Cruise run. It is a convenience note, not an approval or source of authority. Codex's usual permissions, approvals, and native Goal state continue to govern all work and effects.

Choose a skill

| Skill | Use it when | | --- | --- | | build | You need to shape a project or milestone before implementation. | | quick | The requested change is small, understood, and low risk. | | refine | The outcome is finite but needs a short plan first. | | goal | The work is consequential or multi-step and should run to completion. | | debug | You have a clear or vague failure, or want adversarial UX quality control. |

goal is the autonomous lane: it starts with a compact codebase-aware plan for the first micro-goal, then implements, verifies, realigns, and advances ready, in-scope work until the native Goal is complete. Plans launch implementation; they are not a completion boundary. For risky changes, Cruise can use bounded independent breakage probes before advancing. It still asks for material product decisions, secrets, scope changes, and any approval Codex requires for an external or destructive action.

Invoking cruise goal is itself the authorization for ordinary in-scope plan, Goal, contract, and phase transitions. Cruise never asks you to copy a digest or magic approval phrase back to it. That does not bypass Codex approvals for real external, destructive, or otherwise sensitive effects.

Install

Requirements

  • A signed-in Codex app or CLI with plugin support
  • Node.js 20 or later for the optional terminal launcher

Install the Codex plugin

Cruise is installed from a configured Codex plugin marketplace. First inspect the marketplaces and plugins available to your Codex installation:

codex plugin marketplace list
codex plugin list

If your marketplace already exposes Cruise, install it with its listed marketplace name. For example, the local development marketplace uses agent-local:

codex plugin add cruise@agent-local

If no suitable marketplace is configured, add the marketplace source supplied by your team or distribution channel, then install Cruise from it:

codex plugin marketplace add <marketplace-source>
codex plugin add cruise@<marketplace-name>

Verify that Cruise is installed and enabled, then start a new Codex task before using its skills:

codex plugin list | rg '^cruise@'

Use the terminal launcher (optional)

Install the npm package globally to make cruise available on your shell path:

npm install --global cruise-code
cruise --help

For local development, run the launcher directly from a clone of this repository:

node scripts/cruise.mjs --help

To make cruise available on your shell path for local development, link the package once from this repository:

npm link
cruise --help

Use Cruise

In Codex, invoke the matching skill explicitly:

Use $cruise:build to define the next project milestone.
Use $cruise:quick to make this exact small change.
Use $cruise:refine to plan and implement this bounded feature.
Use $cruise:goal to complete this migration with verification.
Use $cruise:debug to find and repair this failing test.

The terminal launcher starts a normal Codex task in the target directory:

cruise quick -C ~/src/app "Fix the failing parser test"
cruise refine -C ~/src/app "Add bounded retry handling"
cruise goal -C ~/src/app "Migrate the API without breaking existing clients"
cruise worker --level 6 -C ~/src/app "Run the focused verification"

Cruise preferences are request-scoped, not persistent configuration. In Codex, put a preference directly in the invocation—for example, “Use a higher-level worker for this run” or “Respond professionally” after $cruise:quick. The terminal worker leaves Codex's model choice untouched unless --level <1-7> is explicitly present; that flag takes priority for that worker invocation only. The retired cruise config command exits immediately with this guidance and never launches a task.

Debug also accepts request-scoped swarm controls in natural language, such as “swarm always, size 8, depth 3, aggressive, fix related confirmed bugs.” A clear reproduction uses Focused mode; a symptom without a reliable path or a general quality-control request uses Swarm mode to exercise distinct UX paths in adversarial waves. Once a cause is confirmed, Debug searches semantically similar code paths for related instances and verifies each before grouping any authorized repair. Swarm depth is separate from worker level and is always capped at 4.

Every invocation replaces .cruise/ORIGIN.md with that invocation's exact request. Cruise does not create run directories, YAML workflows, approval receipts, archives, or retry ledgers.

Troubleshooting

| Symptom | What to check | | --- | --- | | Cruise is absent from the plugin list | Run codex plugin marketplace list and codex plugin list; confirm the intended marketplace exposes cruise. | | The skill is unavailable in a task | Start a new task after the plugin is installed, then invoke $cruise:<skill> explicitly. | | cruise: command not found | Run node scripts/cruise.mjs --help from the clone. If that works, add the optional npm link setup above. | | The terminal launcher will not start a task | Check node --version, codex --version, and codex app-server --help. The launcher needs Node 20+ and a working, authenticated Codex CLI. | | A worker or stream fails | Treat the reported transport category as evidence. Cruise may retry one pre-effect transport failure; otherwise, rerun the normal command when appropriate—there is no special retry phrase or reset procedure. |

Use cruise --help to see the supported terminal commands. Normal Codex approvals remain in effect for commands, file changes, network access, and other external effects.

Development

npm test
npm run validate
node --check scripts/cruise.mjs

License

MIT. See LICENSE.