Commands

miso install

Summary: install dependencies · Aliases: i · Usage: miso install

Installs all dependencies from your lockfile using the project’s package manager.

When to use

After cloning a project, or after pulling changes that touched package.json or the lockfile.

How it works

Miso detects your package manager (bun, npm, pnpm, yarn) and runs its install. Aliased as miso i.

Examples

miso install
miso i

Gotchas

• In simple mode ("packageManager": false) there are no built-in commands — install resolves as a script instead.
• A scripts/ entry or a package.json script named install shadows this command.

miso add

Summary: add dependencies · Usage: miso add <pkg>

Adds one or more dependencies to your project.

When to use

To pull in a new package. Flags pass straight through to the underlying package manager.

How it works

Delegates to the detected package manager’s add/install, forwarding every flag and package name unchanged.

Examples

miso add zod
miso add -D vitest    # dev dependency
miso add -E lodash    # exact version

Flags

All flags are forwarded to the package manager (-D, -E, --global, …).

Gotchas

• A scripts/ entry or a package.json script named add shadows this command.

miso remove

Summary: remove dependencies · Aliases: rm · Usage: miso remove <pkg>

Removes one or more dependencies from your project.

When to use

To drop a package you no longer need. Aliased as miso rm.

How it works

Delegates to the detected package manager’s remove/uninstall, forwarding the package names.

Examples

miso remove lodash
miso rm react redux

Gotchas

• A scripts/ entry or a package.json script named remove shadows this command.

miso run

Summary: run a script · Usage: miso run <script>

Runs a script by name from your scripts folder or package.json.

When to use

To execute a defined script. miso run <script> resolves the scripts folder first, then package.json, then falls back to the package manager.

How it works

Pass one script to run it, or several to run them in sequence. Arguments after -- are forwarded to the script.

Examples

miso run build
miso run lint test
miso run test -- --watch

Gotchas

• Unknown script names fall through to the package manager as a passthrough command.

miso dev

Summary: run the dev script · Usage: miso dev

Shortcut for running the dev script.

When to use

Day-to-day local development. Equivalent to miso run dev, with per-command flag configuration.

How it works

Resolves a dev script from the scripts folder or package.json; if none exists, runs the package manager’s dev. When the TUI is enabled it launches there.

Examples

miso dev

Gotchas

• In a monorepo, dev fans out across discovered workspace members.

miso scripts

Summary: list scripts · Usage: miso scripts

Lists every script miso can run, from both the scripts folder and package.json.

When to use

To discover what you can run in a project.

How it works

Prints the scripts folder entries and the package.json scripts, grouped by source.

Examples

miso scripts

miso env

Summary: validate environment variables · Usage: miso env

Validates environment variables against the schema declared in miso.json.

When to use

Before running or building, to fail fast on a missing or malformed variable. Often chained as a pre-build gate.

How it works

Reads the env blocks from the root miso.json and from every workspace member’s miso.json, loads the referenced .env files, and validates every declared variable against its type. Runs without a package manager.

Examples

miso env

Gotchas

• miso env validates all scopes (global, per-target, per-member), even though injection at run time only uses the resolved subset for the target.
• Traversal covers every workspace member in every repo mode, delegated (repo: "turbo"/"nx") included — a clean exit means the whole repo’s declared variables checked out.
• A member miso.json that won’t parse fails the run rather than being skipped, since a skipped schema would read as a pass.
• Membership comes from package.json workspaces or pnpm-workspace.yaml. A miso.json in a directory that isn’t a workspace member isn’t traversed.

miso init

Summary: scaffold a miso.json in this project · Usage: miso init

Scaffolds a miso.json in the current project.

When to use

Once per project, to adopt miso. Works with no existing config.

How it works

Interactively confirms the orchestration engine and package manager, then writes a miso.json. Runs before any project is loaded.

Examples

miso init

miso upgrade

Summary: update miso to the latest version · Usage: miso upgrade [--local]

Updates miso to the latest version.

When to use

To get the newest miso release.

How it works

Upgrades the globally installed binary by default. Runs before any project is loaded.

Examples

miso upgrade
miso upgrade --local

Flags

• --local — upgrade miso as a local project dependency instead of the global binary.

miso skills

Summary: manage miso agent skills · Usage: miso skills

Manages miso’s AI agent skills for your coding harness.

When to use

To install or remove the miso skill set for an agent harness (Claude Code, OpenCode, Codex, Gemini CLI, Cursor).

How it works

Detects installed harnesses on your PATH and, with --add or --rm, installs or removes the skills for the chosen harness(es). --yes selects every detected harness non-interactively.

Examples

miso skills --add
miso skills --rm
miso skills --add --yes

Flags

• --add — install the miso skills.
• --rm — remove the miso skills.
• --yes — apply to every detected harness without prompting.

Gotchas

• --add and --rm are mutually exclusive.
• With neither flag, skills falls through to normal routing.

miso completion

Summary: print a shell completion script · Usage: miso completion <bash|zsh|fish>

Prints a shell completion script for bash, zsh, or fish.

When to use

Once, to enable tab-completion of miso commands and scripts.

How it works

Emits the completion script for the named shell to stdout. Source it from your shell profile.

Examples

miso completion bash
miso completion zsh
miso completion fish

Gotchas

• Completions cover built-in commands and your project’s scripts, not passthrough package-manager subcommands.

miso version

Summary: print the miso version · Aliases: v · Usage: miso version

Prints the installed miso version.

When to use

To check which miso you’re running. Aliased as miso v.

How it works

Prints the version baked in at build time. Runs before any project is loaded.

Examples

miso version
miso v

miso help

Summary: show this help · Usage: miso help

Shows miso’s help — the command list, or documentation for one command.

When to use

miso help prints the grouped list of built-in commands. miso help <command> prints this kind of detailed page for a single command.

How it works

Runs before any project is loaded, so it works anywhere. miso, miso --help, and miso -h all print the grouped list.

Examples

miso help
miso help add
miso help env