Skip to content

Oasis CLI

System Requirements

Oasis CLI is a single statically linked binary. It has no runtime dependencies. No interpreter, no shared libraries, no package manager. If the architecture and kernel below match, copying the file onto the machine is the whole installation.

Supported architectures

Every artefact is a static musl build, so one file per architecture runs on both glibc and musl hosts. There is no separate glibc build to choose.

ArchitectureCommon namesBuild targetSupport
x86-64x86_64, amd64, Intel 64x86_64-unknown-linux-muslFull. Built and verified on every release
ARMv8 (64-bit)AArch64, arm64aarch64-unknown-linux-muslFull. Built and verified on every release
ARMv7 (32-bit)armv7, armhf, ARM hard-floatarmv7-unknown-linux-musleabihfBest-effort. Published when it builds; a failure does not hold up a release

32-bit x86 (i686/i386) is not supported. There is no build target for it.

ARMv7 is best-effort

An ARMv7 artefact is published whenever the target builds cleanly, but it is not a release gate. If your fleet depends on ARMv7, pin a version you have tested rather than tracking latest, and confirm the artefact exists before you plan a rollout.

Supported operating systems

Operating systemSupportNotes
Linux, any distributionFullKernel 3.2 or newer. Static musl linkage means the distribution and its libc do not matter.
Windows via WSL 2FullInstall the Linux binary inside the WSL distribution, not on the Windows side.
Windows (native)Not supportedNo native Windows build. Use WSL 2.
macOSNot supportedNo macOS build, on Intel or Apple silicon.

Artefact size

ArtefactSizeLinkage
oasis-agent, x86_649.24 MiBStatic, position-independent

Every artefact is checked against a 25 MB budget and a static-linkage assertion before it is published. A build that grows past the budget or picks up a dynamic dependency fails the release rather than shipping.

Runtime requirements

RequirementDetail
Model endpointAn OpenAI-compatible endpoint reachable from the machine. Required, because the binary supplies the agent, not the model. See Configuration.
setcapOnly for EtherCAT. Used by install to grant CAP_NET_RAW and CAP_NET_ADMIN. Debian and Ubuntu ship it in libcap2-bin. Absent, the install succeeds and prints the command to run later.
Disk~10 MiB per installed version. Three versions are retained by default, so budget ~30 MiB plus conversation history.
Writable $HOMEConfiguration, conversation history, the audit log and installed versions all live under ~/.oasis. Set OASIS_ROOT to relocate them.
NetworkOnly to your model endpoint, plus the release host if you use oasis-agent update. Nothing else is contacted.

Elevated privileges

Oasis CLI runs as an ordinary user. Two capabilities need more, and both are opt-in:

CapabilityRequirementWhy
EtherCAT bus acquisitionCAP_NET_RAW, or rootAcquiring a fieldbus segment needs a raw socket on the interface. Every acquisition prompts for approval regardless of permission mode, and --skip-permissions does not waive it.
Some PREEMPT_RT checksRead access to /proc, /sys, and kernel boot parametersUsually readable by any user. A check that cannot read its source reports not_applicable with a reason rather than guessing.

Nothing else in the tool surface requires privilege. Restricting which interfaces may be acquired is covered in Capability Packs.

Terminal

The interactive REPL needs a terminal that supports ANSI escape sequences, which every modern terminal emulator, and the Windows Terminal under WSL. Colour is auto-detected and can be disabled with --no-color or the standard NO_COLOR environment variable.

One-shot mode, background agents, check, audit and the control protocol need no terminal at all and run correctly under cron, CI and systemd.

software-defined automation