Install oberth

The installer does three things: resolve the latest release, verify the platform archive, and put the binaries on PATH. It does not touch your project, and it does not start the daemon.

One line, macOS and Linux

install · macOS or Linux

curl -fsSL https://raw.githubusercontent.com/SheathedSharp/option-berth/main/install.sh | sh

The script reads uname, picks the matching darwin/linux and amd64/arm64 archive, verifies its same-named .sha256, then installs. No administrator rights are needed.

Binaries: ~/.local/bin/oberth and ~/.local/bin/jev-attention.
Licenses and build manifest: ~/.local/share/option-berth.
PATH: one line added to an existing shell startup file, never a new one.
Runtime state: ~/.option-berth, which the installer neither creates nor modifies.

Pin a version with --version v1.0.0, change the directory with --dir "$HOME/tools/bin", or leave your shell files alone with --no-modify-path. The script also probes mirrors when the official host is slow or unreachable; a mirror must report the same SHA256 before the install continues.

Windows

install · Windows PowerShell

irm https://raw.githubusercontent.com/SheathedSharp/option-berth/main/install.ps1 | iex

Binaries land in %LOCALAPPDATA%\option-berth\bin, and only the current user's PATH is changed. Pin with -Version, leave PATH with -NoModifyPath. Before replacing files, the installer stops a running oberth daemon; it does not stop your services for you.

Other ways in

Installation channels
Channel	Command	What it is for
go install	`go install github.com/sheathedsharp/option-berth/engine/cmd/oberth@latest`	Go 1.25+, lands in `GOPATH/bin`; a module proxy is enough.
Homebrew	`brew install sheathedsharp/tap/oberth`	The engine CLI from a self-hosted tap; not homebrew-core.
Release archive	download, verify `SHA256SUMS`, put it on PATH	When you would rather not run a script.
Linux packages	`.deb` or `.rpm`	Distribution-managed installs; details in the install contract.

Check the build

first commands

oberth version --json
oberth doctor

version --json returns version, commit, built and platform for the binary you actually installed. doctor checks the manifest, the daemon, the CLI path, the log directory and whether the current process can see listeners. A blind listener check is reported as blind, with the next step; it is not written as “nothing is listening”.

Platform boundaries

Full service scenarios are verified on macOS and Linux. Windows has a native build and smoke test plus an arm64 cross-build; that is not a promise that the full lifecycle is verified there. The engine has no graphical interface: the macOS client is a separate product, and the coding-agent skill is another one.

Upgrade and remove

Upgrade by rerunning the installer for your platform; after upgrading, run oberth daemon stop once and the next call starts the new build. Uninstall with uninstall.sh on macOS and Linux, or uninstall.ps1 on Windows. The uninstaller stops the daemon first and keeps ~/.option-berth unless you pass --purge-state. The exact flags and per-platform paths are in Install and uninstall.

Edit this page