Melious
CLI

Managing tools

The admin surface for coding tools melious launch hands off to. Install, update, override their models, and let the CLI find and fix the usual PATH problems when something doesn't run.

Status

melious tools

A table per supported tool: whether it's installed, which version, any per-tool model override, and how we integrate with it.

Install a tool

One tool:

melious tools install opencode

Everything that's missing:

melious tools install --all

Before installing, we check prerequisites — Node.js and npm for OpenCode on Windows, uv for Vibe on Windows. If a tool is already on disk but outside your PATH, we offer to fix the PATH instead of installing a second copy.

Check prerequisites

melious tools check

Reports on Node.js, npm, uv, and every tool binary. Installed entries show their version; missing ones get an install hint.

Update

One tool:

melious tools update opencode

All installed tools:

melious tools update

Tool info

melious tools info opencode

Prints a summary: what the tool is, its homepage, install status, version, command, prerequisites, the integration method, and the model config that'll be used if you launch it now.

Per-tool model overrides

Show the current models for a tool:

melious tools model opencode

Override the main model only for this tool:

melious tools model opencode deepseek-v3.2

Override every tier at once:

melious tools model opencode deepseek-v3.2 \
  --secondary qwen3-235b-a22b-instruct \
  --lightweight qwen3-30b-a3b-instruct

Drop the overrides and go back to the global config:

melious tools model opencode --clear

Overrides live under tool_models in config.json and only apply when launching that specific tool. Other tools keep reading models.*.

Diagnostics

Run checks on one tool:

melious tools diagnose opencode

Or every tool:

melious tools diagnose

What we look for:

  • Tool not installed
  • Tool installed but outside PATH
  • Missing prerequisites
  • Tool-specific config issues (bad paths, stale generated configs)

Results come with severity — error, warning, or info — and an offered fix where one exists.

PATH fixes

When a tool is installed somewhere your shell doesn't look (~/.local/bin, %APPDATA%/npm, and friends), run:

melious tools fix-path

We scan the usual install directories, find tools that aren't on PATH, and offer to add those directories permanently. Supports zsh, bash, fish, and PowerShell.

Restart your terminal after a PATH change. The new entries are written to your shell's rc file, but an already-running shell won't see them until it re-reads that file.

On this page