Install CLIO Coder

Install, update, and launch CLIO Coder on your machine.

Install

You need a model with tool calling. Linux, macOS and WSL are the primary platforms; native Windows is best effort. Every command below installs the latest release. Choose the tab for your system.

curl -fsSL https://coder.iowarp.ai/install.sh | sh

curl -fsSL https://coder.iowarp.ai/install.sh | sh -s -- --modify-path

irm https://coder.iowarp.ai/install.ps1 | iex

powershell -NoProfile -Command "irm https://coder.iowarp.ai/install.ps1 | iex"

npm install -g @iowarp/clio-coder

bun add -g @iowarp/clio-coder

Confirm the installation

Open a new terminal and run:

clio-coder --version

It prints the installed version. If the shell says clio-coder: command not found, the launcher directory is not on your PATH yet. Add the line the installer printed to ~/.bashrc or ~/.zshrc, or install again with --modify-path:

export PATH="$HOME/.local/bin:$PATH"

command -v clio-coder shows which file the name runs. If it is not ~/.local/bin/clio-coder, an older install comes first on your PATH; remove it or reorder PATH. clio-coder doctor checks the installation and connections.

Open a project

cd /path/to/your/project
clio-coder configure
clio-coder

On first launch, Guided setup asks what you have: an API key, a subscription, a model server or gateway, or a setup file from your lab or team. It sends the model one short test request and saves when the model answers. CLIO Coder has no account of its own; your provider may require credentials and charge for inference.

A new installation starts guided setup by itself, so clio-coder configure is optional. If you have used CLIO Coder before and no chat route is saved, it looks for a route it can use, such as a provider key in your environment, and opens chat with it. A model server found on a local port is used only after you say yes.

/config opens your connections inside a session, where Add a target runs setup again.

Prefer the desktop alpha? It is served from your own machine, opens in your browser, and shares the terminal's saved connections and settings. See the desktop app:

clio-coder gui --open

The browser has its own Guided setup; configuring in the terminal first is optional.

Update, roll back and remove

Installer installs update themselves in the background, at most once a day. On Linux and macOS, npm, pnpm, bun, and volta installs whose prefix you own update after an interactive session quits and no other process of that install remains. Set interface.autoUpdate: false or CLIO_CODER_AUTO_UPDATE=0 to keep only the notice. /upgrade reviews an update from inside the terminal. From the shell, update with the tool that installed it:

The installer keeps the previous version. clio-coder upgrade --rollback makes it current again. An install made with an exact --version stays pinned to that version until you run the installer with --version latest.

If an upgrade is refused over a setting the installed version cannot repair, the installer prints the new version's own doctor --fix command to run.

clio-coder uninstall removes your settings, credentials, sessions and caches, the launcher, the desktop app's background service, and for an installer install the managed Node and every package version. It previews what it will delete and asks first, and it stops with exit 1 while a session is open on this state directory. Add --keep-binary to keep the program, --keep-config to keep settings and credentials, or --dry-run to only look. Removing the program with npm or bun keeps those files. Project .clio-coder/ directories are never removed.

If coder.iowarp.ai is unreachable, the latest GitHub release carries the full installer, at https://github.com/iowarp/clio-coder/releases/latest/download/install.sh.

Give CLIO Coder a useful first task

Start with a request that lets you assess its understanding of your project:

Explain how this repository builds and runs its tests. Identify the main entry points and suggest one verification task. Do not change files yet.

Then ask for a small change, name the files or behavior you care about, and tell CLIO Coder which checks should pass. Review the diff and recorded results before accepting the work.

Follow the desktop and terminal walkthrough, or try a numerical change with seven tests.

Keep going

• Connect a model: setup, model selection, and saved settings.
• Commands and shortcuts: the controls you'll use most.
• Tools and permissions: understand changes and review checks.
• Check your installation: diagnose a connection or setup problem.

When you need more detail

These web guides cover the essentials. Detailed documentation ships with CLIO Coder; ask it to look up the bundled guide for the feature you're using. Each page also links to its full source guide.

Related tutorials