Direct file and shell control
Read and edit files, run shell commands, inspect output, and commit the result from one terminal session without handing work off to another app.
Preview / staging docs
A terminal harness for real software work.
Omegon gives an agent direct access to files, commands, memory, and lifecycle state without pretending a chat transcript is an engineering process.
Use it when the job is bigger than a one-shot prompt: inspect a repository, make a multi-file change, preserve decisions, and keep the execution path visible while the work is happening.
Read, edit, run, commit Memory across sessions Worktree-based decomposition
Terminal-native software harness
Release-candidate and nightly guidance lives here. Stable operator guidance stays on the public .io surface.
Install
Start with one binary.
Omegon installs two entrypoints from the same binary: om for the slim terminal-first posture and omegon for the full harness. Use the stable site for production recommendations and the preview site for RC/nightly evaluation.
curl -fsSL https://omegon.styrene.dev/install.sh | sh installs v0.15.10 Install docs
Preview channel
CHANNEL=rc curl -fsSL https://omegon.styrene.dev/install.sh | shNightly channel
CHANNEL=nightly curl -fsSL https://omegon.styrene.dev/install.sh | sh~19 MBsigned binary
10provider paths
53structured tools
0runtime Node deps
Why teams use it
Competent about the work itself, not just the words around it.
Persistent project memory
Store durable facts, decisions, and known issues across sessions so the agent can resume work with actual project context instead of starting cold.
Scoped parallel work
Split larger changes into git worktree children with bounded file scope, dependency ordering, and merge-back into the parent branch.
Design and spec discipline
Track design exploration in the design tree and tie implementation work to OpenSpec scenarios when the change is large enough to need them.
Provider transparency
Show the concrete backend in use — Anthropic/Claude, OpenAI API, OpenAI/Codex, or Ollama — along with runtime and quota context when the provider exposes it.
Operationally simple
One Rust binary, signed releases, no runtime Node.js dependency, and a docs/install surface that stays separate between stable and preview channels.