Install OmO

Check the install

Open a new terminal, so it picks up the updated PATH, and run:

omo --version

It prints the installed version. Then open a project, run omo, and describe the job.

If the terminal says omo: command not found (or omo is not recognized on Windows), see Fix your PATH.

Fix your PATH

When ~/.local/bin is not on your PATH, the installer adds it for you:

On macOS, Linux and WSL the edit is a block between # >>> omo installer >>> and # <<< omo installer <<<, so running the installer again never adds a second copy. A terminal that was already open does not re-read that file. Open a new one, or add the directory to the current session:

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

To add it yourself (for example after installing with OMO_NO_MODIFY_PATH=1):

# zsh
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
# bash (use ~/.bash_profile on macOS)
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
# fish
fish_add_path ~/.local/bin

# Windows PowerShell
$userPath = [Environment]::GetEnvironmentVariable('Path', 'User')
[Environment]::SetEnvironmentVariable('Path', "$userPath;$HOME\.local\bin", 'User')

On Windows the window you installed from can run omo right away. Other terminals see the new PATH after you open them again.

If omo --version prints something unexpected, another omo may come first on your PATH. command -v omo (macOS, Linux, WSL) or Get-Command omo (PowerShell) shows which one runs. The installer also reports an npm or Bun install of omo-ai it finds, and leaves it in place.

Pick a channel or version

The installer follows the latest channel, the same release as omo-ai@latest on npm. Pass beta for the beta channel, or an exact version:

curl -fsSL https://get.omo.dev/install.sh | bash -s -- beta
curl -fsSL https://get.omo.dev/install.sh | bash -s -- 5.1.1

& ([scriptblock]::Create((irm https://get.omo.dev/install.ps1))) beta

Settings, read from the environment:

In a pipe, set the variable on the bash side: curl -fsSL https://get.omo.dev/install.sh | OMO_INSTALL_DIR="$HOME/bin" bash.

Update

Run the install command again. It replaces the binary when the channel has a newer version and does nothing otherwise.

Uninstall

macOS, Linux and WSL:

rm ~/.local/bin/omo
rm -rf ~/.omo/binary-runtime ~/.omo/install.json

Then delete the # >>> omo installer >>> block from the shell file listed in Fix your PATH.

Windows PowerShell:

Remove-Item "$HOME\.local\bin\omo.exe"
Remove-Item -Recurse "$HOME\.omo\binary-runtime", "$HOME\.omo\install.json"

Then remove %USERPROFILE%\.local\bin from your User PATH if nothing else lives there.

~/.omo also holds your settings, sessions and memory. Delete the whole folder only if you want those gone too.

Behind a proxy or offline

The installer needs HTTPS access to get.omo.dev. If that fails, it falls back to registry.npmjs.org (to resolve the channel) and github.com (for the files). On macOS, Linux and WSL it downloads with curl (or wget), which honor the https_proxy / HTTPS_PROXY environment variables. Windows PowerShell uses the system proxy settings.

The binary is self-contained. On first run it unpacks its runtime into ~/.omo/binary-runtime/<version>/ without downloading anything, so it runs on a machine with no internet access. To install on such a machine, download the asset for your platform and SHA256SUMS from GitHub Releases on a connected machine, verify it, and copy it to ~/.local/bin/omo. The asset names and the manual steps are in the compiled binary guide. Teams with an internal mirror can point OMO_INSTALL_BASE_URL at a server that copies the get.omo.dev paths (/channels/<channel>, /v/<version>/<asset>).

Install with npm or Bun instead

The same OmO is published to npm as omo-ai:

bun add -g omo-ai
# or
npm i -g omo-ai

A package-manager install updates with omo update and uninstalls with bun remove -g omo-ai (or npm uninstall -g omo-ai). The unrelated omo package on npm belongs to someone else.

Looking for the OpenCode or Codex plugin editions instead? See Installation.