The field guide

Install just-vibe

One npm package. Your package manager. Your coding agent.

Before you start

You need Node.js 22 or newer and Codex CLI or Claude Code with native plugin support on your PATH. External workflows use your own service accounts and tools.

1. Run the installer

Select your package manager and host, then run this in your terminal. The default target is Codex.

Package manager
pnpm dlx just-vibe@latest setup

Node.js 22+ · Native plugins required · Full installation guide

The installer copies the bundled plugin into a persistent directory under ~/.just-vibe and registers it with the host’s native plugin manager. It survives package-manager cache cleanup. The default installation requires no GitHub access.

2. Start a new conversation

In Claude Code, run:

/just-vibe:help what is available?

In Codex, select the help skill from the just-vibe plugin and add your request. The Claude slash syntax is not the Codex skill-picker syntax.

3. Bring a real task

Start with auto when you know the outcome you want, orient for an unfamiliar repository, or tools to discover a specific workflow.

Prefer a project dependency?

Install the same package locally, then run its CLI. Installing the npm dependency alone does not register the plugin.

npm install -D just-vibe
npx just-vibe setup
pnpm add -D just-vibe
pnpm exec just-vibe setup
yarn add -D just-vibe
yarn just-vibe setup

Append --target claude to the setup command for Claude Code. Modern Yarn uses yarn dlx; a local dependency is also an option.

Claude installation scope

Claude defaults to user scope. From a project directory, use the following for shared project enablement. Each teammate still installs their own local marketplace.

pnpm dlx just-vibe@latest setup --target claude --scope project

Use --scope local for unshared project enablement. Keep the same scope for future operations. Codex does not take Claude’s scope option.

Preview before installation

pnpm dlx just-vibe@latest setup --dry-run

A dry run does not copy the payload or run host commands. The package manager may still fetch and cache the CLI. Read about updates and diagnostics