Skip to main content
The Radius app includes the CLI and makes it available automatically in terminals opened by Radius. On first launch, Radius also creates ~/.local/bin/radius for external terminals and adds that directory to your shell PATH when needed.

​
The shell says radius: command not found

Open a new terminal window after Radius starts. If the command is still missing, run:
Confirm the output contains $HOME/.local/bin. Then choose Radius → Repair Terminal Command… and open another terminal window.

​
Repair the terminal command

Choose Radius → Repair Terminal Command… to check the launcher, shell PATH, bundled CLI version, and login-shell configuration. Radius repairs a missing, stale, or broken Radius-owned launcher without replacing another command at the same path. The Radius application menu showing Repair Terminal Command Radius supports automatic PATH setup for zsh, bash, sh, and fish. For another shell, add this directory to your PATH:

​
A different radius command runs

Run:
The app-managed command is $HOME/.local/bin/radius. If another command appears first, adjust your PATH only if you want the app-bundled CLI to take precedence.

​
Verify the app connection

With Radius running:
If Radius is not running, start it from the CLI:

​
Install the standalone npm package

Most users should use the CLI included with Radius. For a standalone installation, macOS and Node.js 20 or newer are required:
npm installations update through npm. The CLI included with Radius updates when the app updates.

​
More than one Radius instance is running

The CLI asks you to select an instance instead of guessing. See Multiple Radius instances.