Installation

Direct Install

curl -fsSL https://omegon.styrene.io/install.sh | OMEGON_BOOTSTRAP_VERIFIER=/absolute/path/to/independently-trusted/omegon-maintain sh

Downloads the latest signed release pair, shipped content pack, and product componentcore:codescan for your platform (macOS arm64/x86_64, Linux x86_64/aarch64). The required OMEGON_BOOTSTRAP_VERIFIER must name an absolute, independently acquired and trusted omegon-maintain executable. The installer downloads the archive, canonical package manifest, and Sigstore bundle; the external verifier authenticates all three before extraction. A checksum is only an integrity aid. No verifier acquisition URL is implied by this command. The authenticated staged companion then checks the exact extracted tree before the installer atomically activates the full product under /usr/local/binby default.

Options

# Install to a custom directory
curl -fsSL https://omegon.styrene.io/install.sh | OMEGON_BOOTSTRAP_VERIFIER=/absolute/path/to/independently-trusted/omegon-maintain INSTALL_DIR=~/.local/bin sh

# Install latest nightly (bleeding-edge from main)
curl -fsSL https://omegon.styrene.io/install.sh | OMEGON_BOOTSTRAP_VERIFIER=/absolute/path/to/independently-trusted/omegon-maintain sh -s -- --channel=nightly

# Install the 0.28.0 stable release
# Replace 0.28.0 with the release you actually want
curl -fsSL https://omegon.styrene.io/install.sh | OMEGON_BOOTSTRAP_VERIFIER=/absolute/path/to/independently-trusted/omegon-maintain sh -s -- --version=v0.28.0

# Non-interactive (CI)
curl -fsSL https://omegon.styrene.io/install.sh | OMEGON_BOOTSTRAP_VERIFIER=/absolute/path/to/independently-trusted/omegon-maintain sh -s -- --no-confirm

Deferred Package Channels

Homebrew, Nix, and OCI packaging remains under pre-publication validation. These are not supported public installation channels yet; use an authenticated release archive or the externally verified direct installer.

GitHub Releases

Download release artifacts directly fromGitHub Releases. Stable and nightly release archives include:

• Pre-built omegon and omegon-maintain companions for macOS and Linux
• Resident composition locks for both executables, bound by the signed package manifest
• The versioned omegon-shipped content pack under share/omegon/content-packs/
• Signed product component core:codescan under share/omegon/extensions/
• SHA-256 checksums
• Sigstore cosign signatures (keyless)
• Installer/update metadata used by /update for verification before install

Stable releases additionally include a signed CycloneDX SBOM and GitHub build-provenance attestations. Nightlies retain archive checksums and signed package-manifest bundles but omit those stable-only assets.

Nix and OCI Candidate Composition

Candidate Nix packages and Nix-built OCI images contain the default compiled host but no product-component binaries. These distributions are host-only, not full-product equivalents. Codescan is unavailable as service:codescan until the operator installs and manages a compatible SDK extension. OCI deployments can provide that extension through an init container and the shared OMEGON_HOME volume.

Legacy npm package files remain in the source tree, but npm is not a supported installation or publication channel.

Verify a Download

omegon-maintain --json release verify \
  --archive /absolute/path/omegon-<version>-<target>.tar.gz \
  --manifest /absolute/path/omegon-<version>-<target>.tar.gz.manifest.json \
  --bundle /absolute/path/omegon-<version>-<target>.tar.gz.manifest.sigstore.json

This offline check binds release identity, provenance, executable digests, protocol ranges, target support, required/optional state, fallback, and both resident locks to compiled trust policy. Required lock failure is fail-closed. It does not extract or execute optional contributions.

Verify the Installed Pair

omegon --version
omegon-maintain --version
omegon --which
omegon-maintain --which
omegon-maintain --json identity

Supported packages install matching omegon and omegon-maintainversions. Supported packages also install the shipped content pack beside the pair. A missing, incompatible, or non-launching companion is an incomplete installation. Missing optional content does not block kernel or maintenance startup, but shipped skills, prompts, and catalog data are unavailable. Do not copy a companion from another release; reinstall through the owning channel.

For a linked source checkout, both --which results must identify the same current checkout and report stale: no. Re-run just link if either launcher reports stale metadata.

Upgrades require no configuration rename: existing disabled_tools inputs remain accepted and are translated to capability admission policy. Older archives are not retrofitted with resident locks; install the complete pair from one current release rather than mixing files.

Provider Setup

After installing, you need at least one inference provider configured. Three fast paths:

Option A: Anthropic/Claude interactive subscription path

omegon auth login anthropic
om

Opens a browser for OAuth authentication. Interactive TUI use is the intended low-friction path. If this is your only Anthropic credential, headless execution emits an explicit operator-risk warning and proceeds; it does not silently switch providers or pretend subscription OAuth has API-key automation semantics.

Option B: API key path

omegon secret set ANTHROPIC_API_KEY --stdin
om

Use this when you want clean automation semantics for prompts, smoke runs, or cleave workers.

Option C: OpenAI/Codex OAuth, Ollama Cloud, or local Ollama

# OpenAI/Codex OAuth
omegon auth login openai-codex
om

# Hosted Ollama
omegon auth login ollama-cloud
om

# Or local inference
ollama pull qwen3:32b
om

Omegon auto-detects Ollama for local-tier work. OpenAI/Codex gives you the ChatGPT/Codex-backed route without requiring an OpenAI API key. Ollama Cloud is a separate hosted provider from local Ollama, authenticated via OLLAMA_API_KEY and configurable through /auth login or /secrets.

Omegon installs two normal-runtime entrypoints from the same binary:om (slim, copy-friendly, familiar terminal mode) andomegon (full harness), plus the distinct omegon-maintainrecovery companion. You can override normal startup posture with om --fullor omegon --slim; maintenance is not an alias or mode.

See Providers for representative auth postures and current boundaries.

Updates

Omegon checks for updates automatically at startup (non-blocking). When a newer version is available, the TUI shows a notification.

Future package-manager installs

Package-manager ownership must remain external to Omegon when those channels are enabled. The in-app /update command will redirect rather than overwrite a managed binary.

Script installs

# Re-run the install script to update
curl -fsSL https://omegon.styrene.io/install.sh | OMEGON_BOOTSTRAP_VERIFIER=/absolute/path/to/independently-trusted/omegon-maintain sh

Source checkouts should run just link. Every update path replaces and validates the pair together. See Maintenance & Recovery when normal startup is unavailable. A compatible content-pack replacement can be installed independently; Omegon admits it on the next process boot and does not migrate active sessions.

Script-managed installs stage each matching executable pair and its receipt in an immutable~/.omegon/versions/<version>/ directory. One atomic~/.omegon/current switch activates all three together, so an interrupted update leaves the previous complete release active and available for rollback.

Supported Platforms