Learn
Install oloop, then read the reference for compatibility and pulls. If you are choosing a machine or a model, start with a guide.
Install
Run this in a terminal on macOS or Linux. Node.js 20 or newer, curl, and tar are required. The installer prints the PATH line for your shell.
curl -fsSL https://oloop.run/install.sh | shWhat the checks mean
Operator evidence means Outerloop ran this pinned setup on the stated hardware. It is not a security review.
Community runs are distinct handles with a passing run, counted per exact version. Below 3 users we show no number; failed runs are separate.
A checksum identifies the published bytes. It does not prove the agent is safe.
An oracle pass means its configured check passed. It does not guarantee a correct answer.
Docs
The reference covers install, compatibility, pulling a manifest, publishing, and the data the Hub keeps.
Guides
Each guide covers a choice the catalog cannot measure.
| Guide | What it answers | Page |
|---|---|---|
| Why own the agent runtime | One manifest, one root, a lock, checksums, and evidence: what oloop owns, what you own, and what removal actually deletes. | Read the guide |
| Local coding model by memory size | What fits at 8, 16, 24, 32, 64, 128, and 192+ GB, which classes we measured, and where the catalog has no record. | Read the guide |
| Windows local AI: the stack and a coding agent | What Windows ML, Foundry Local, and Phi Silica do, what they do not give a coding agent, and the WSL2 path that works today. | Read the guide |
| Self-hosted coding agent for a team | How a team runs one pinned coding setup on its own machines: shared manifests, one root per project, the measured L4 path, and a self-managed AWS L4. | Read the guide |
| Secure local coding agent | What a local coding agent sends, what the Hub stores, the evidence you can keep, and the compliance claims we do not make. | Read the guide |
Questions
What should I read first?
Install oloop, then read the compatibility rule in the docs. If you have not chosen a machine, start with the setup catalog and the measured pages.
Do I need a handle to install or read?
No. Installing, reading, and running a local manifest need no handle. A handle is required to publish and to pull a public manifest with the CLI.
Where are the platform requirements?
The docs state the supported hosts, the POSIX prerequisites, and the Windows boundary. The install block on this page carries the command and the short prerequisite line.