KOMU CLI supports normal package installs, editable installs, and pipx installs. Because it is a CLI product, pipx is the recommended path for most end users.
KOMU also supports both:
- local / self-hosted model workflows through
ollamaandopenai-compatible - hosted API workflows through
claude,openai, andgemini
python -m pip install --user pipx
python -m pipx ensurepathRestart PowerShell, then install from a local checkout:
pipx install .
komu --helpFuture GitHub install:
pipx install git+https://github.com/<owner>/<repo>.gitFuture PyPI install:
pipx install komu-clipython3 -m pip install --user pipx
python3 -m pipx ensurepath
pipx install .
komu --helppython -m pip install .
komu --helppython -m pip install --user .Then confirm PowerShell can find the installed command:
Get-Command komu
where.exe komuIf not, add your Python user Scripts directory to PATH and reopen the shell.
For contributors:
python -m venv .venv
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\.venv\Scripts\Activate.ps1
python -m pip install -e .[dev]On Linux/macOS:
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -e .[dev]After any successful install:
komu --version
komu --help
komu providers list
komu profiles list
python -m komu_cli --helpProvider validation:
komu providers list
komu providers capabilities
komu providers health
komu providers check openaiUse .env.example as the starting point for provider configuration.
Common local / self-hosted settings:
KOMU_OLLAMA_BASE_URLKOMU_OLLAMA_MODELKOMU_OLLAMA_TRUSTKOMU_OPENAI_COMPAT_BASE_URLKOMU_OPENAI_COMPAT_MODELKOMU_OPENAI_COMPAT_TRUST
Common hosted settings:
KOMU_CLAUDE_API_KEYKOMU_OPENAI_API_KEYKOMU_GEMINI_API_KEY
Preferred secret setup:
- use real shell environment variables first
- use
.envonly as a local convenience file - enable optional keyring support with
KOMU_SECRET_BACKEND=keyringif you want secrets outside plaintext files
Avoid storing raw API keys in config.json.
- venv install:
komulives in.venv\Scriptsor.venv/bin - user install:
komulives in the user Scripts/bin directory pipxinstall:pipxexposes the command through its managed command path
For Windows-specific troubleshooting: