欧米伽

Install

curl -fsSL https://omegon.styrene.io/install.sh | sh

Nightly channel one-shot:

curl -fsSL https://omegon.styrene.io/install.sh | sh -s -- --channel=nightly

Or with Homebrew:

brew tap styrene-lab/tap
brew install omegon

Stable docs: <https://omegon.styrene.io/docs/install> Nightly/staging docs: <https://omegon.styrene.dev/docs/install>

---

Build from source

cargo build --release

Release binary:

target/release/omegon

Common development commands:

just build
just test-rust
just lint
just link

just link writes a sourceable dev alias file at ~/.omegon/dev-alias.sh and wires the current shell profile so omegon and om point at the newest local build. It does not overwrite package-manager owned binaries.

---

Quick example

Launch Omegon in a repo:

om

Then prompt it normally:

Read README.md and summarize the architecture.

Or make it do real systems work:

Inspect the auth flow, identify the weakest boundary, propose a minimal fix, add tests, and commit it.

Or lean into lifecycle mode:

We need to refactor the session model. Explore the design space, surface assumptions, write a spec, and then implement it.

---

Tutorial that actually does work

/tutorial is an interactive overlay, not a static lesson reader. It can read code, store memory, create lifecycle artifacts, and walk an operator through real work.

---

Configuration

Mutable user state lives under:

~/.config/omegon/      settings and provider auth
~/.omegon/             installed skills, agents, extensions, dev aliases

Common files: - auth.json — provider credentials - settings.json — user settings - AGENTS.md — global directives

Project-local control surfaces include: - AGENTS.md - .omegon-version - .omegon/openapi.toml - ai/memory/facts.jsonl - openspec/ - docs/

---

API-key path

omegon secret set ANTHROPIC_API_KEY --stdin
om

For operator-owned tokens, use the same keyring-backed secrets engine. Raw values can be entered through hidden TUI input:

/secrets set VAULT_ROOT_TOKEN

Recipes can alias existing keyring entries without copying values:

omegon secret set VAULT_TOKEN --recipe keyring:VAULT_ROOT_TOKEN

Benchmarking and signal shaping

Omegon ships with an in-repo token-efficiency comparison harness under scripts/benchmark_harness.py and ai/benchmarks/.

Use it to compare harnesses against the same task and acceptance criteria, then inspect totals, wall clock, and Omegon's sys/tools/conv/mem/hist/think buckets before changing prompt, history, or tool-surface behavior.

Current stance:

• om is the comparison profile for mainstream CLI coding agents.
• omegon is the full systems-engineering harness profile.
• omegon --slim and om --full remain valid overrides.
• the benchmark harness stays in-repo while it is coupled to --usage-json, omegon_context, auth/provider behavior, and clean-room runtime mechanics.