Installation
Get access
Ogoron is distributed to customers directly.
If you do not have an Ogoron binary or container image yet, request access using the sign-up form:
Repository access for the CLI is granted per organization.
The repository token is issued in the personal cabinet of the organization owner or another organization member who manages billing/access for that organization:
Prerequisites
- An Ogoron binary for your OS or a container image (provided after onboarding)
- Git (recommended for CI/CD and for working with feature branches)
OGORON_REPO_TOKENfor your organization- For BYOK trial access only:
OGORON_LLM_API_KEY
Install (binary)
Windows
- Download
ogoron.exe. - Put it into a folder included in
PATH(or keep it next to your repository). - Verify:
ogoron --version
ogoron --help
Linux
- Download
ogoron. - Make it executable and verify:
chmod +x ./ogoron
./ogoron --version
./ogoron --help
To make ogoron available globally:
sudo mv ./ogoron /usr/local/bin/ogoron
ogoron --version
Run with Docker
Ogoron can be distributed as a container image that runs the same CLI.
Recommended pattern: mount your repository and run Ogoron inside it.
docker run --rm \
-e OGORON_REPO_TOKEN="$OGORON_REPO_TOKEN" \
-v "$PWD:/repo" \
-w /repo \
"$OGORON_IMAGE" \
ogoron --version
OGORON_IMAGE is provided during onboarding.
Configure repository access
Ogoron reads the repository token from:
OGORON_REPO_TOKENOGORON_KEY(legacy alias)
It can also load environment values from a .env file in the current working directory.
Recommended: set OGORON_REPO_TOKEN in CI secrets and in your local shell profile.
BYOK trial only
If your organization is on a BYOK trial, also set the LLM API key:
OGORON_LLM_API_KEYOPENAI_API_KEY(fallback alias)
Recommended: prefer OGORON_LLM_API_KEY in CI and local shell profiles so the Ogoron-specific intent is explicit.
Update
If you use the binary distribution, update by downloading a newer binary.
If you use a container image, update by pulling a newer image tag.