---
title: "Manifests: agent bundles and machine setups"
description: "What a manifest is, how it differs from a machine setup, and how to fetch one someone shared or publish your own."
canonical: https://oloop.run/manifests
updated: 2026-10-05
---

# Manifests

A manifest is the agent bundle: a declarative outerloop.yaml plus a versioned AGENT.md. A setup is the machine config that runs it. Fetch a manifest when someone shares its name and version.

## Machine setups

The catalog lists every published setup with its pins and its evidence. The measured pages cover the classes with a passing record.

- [All setups](/setups)
- [Measured setups](/local)

## Measurements

Benchmarks are measured runs on stated hardware. The leaderboard ranks handles by distinct verified runs and saves. Neither is a quality score.

- [Benchmarks](/insights)
- [Leaderboard](/leaderboards)

## What verification means

Checked at publish: the bundle passed the size, path, and shape checks. The recorded digest identifies the bytes.

A pass is not a security review.

- Verified run: the manifest's oracle passed in a reported real run.
- Failed run: the run reached the oracle and did not pass.
- Below 3 verified runs, the page says “Fewer than 3 verified runs for <v>.” It never shows a count.
- When a page has no record, it says “No run evidence yet.”
- Official is provenance: published by the reserved Outerloop account. It is not a pass, a review, or a security claim.

## Fetch a public manifest

Install the CLI first. Then pull the exact name and version you received. Fetching writes files; it does not run the agent.

The public manifests are listed above. If someone hands you a name and version, pull that exact pair.

```sh
curl -fsSL https://oloop.run/install.sh | sh
oloop pull <owner>/<name>@<version>
```

- [Install and requirements](/docs#install)
- [Fetch details](/docs#pull)

## Publish a manifest

Claim a free handle, then publish the manifest from your directory. Pulling and publishing need a handle; running a local manifest does not.

- [Claim a handle](/claim)
- [Publish details](/docs#publish)

## What a manifest contains

- outerloop.yaml: the declarative settings, including the model and tool allow list.
- AGENT.md: the versioned instructions the agent reads.
- skills/: optional skill files the agent can load.

- [The memory guide](/guides/local-coding-model-by-memory)

## Questions

### Manifest or setup?

A manifest is the agent bundle you publish or pull. A setup is the machine config that runs it. A setup page carries hardware and a model; a manifest carries instructions and declared settings.

### Do I need a handle to fetch a manifest?

Pulling a public manifest with the CLI needs a free handle. Running a manifest that is already on your machine does not.

### Can I browse every public manifest?

Yes. The directory above lists the newest public manifests with their latest version, one-line summary, license, and links to their versions and run evidence. When the list is cut, the page says so. Search filters the list by name, handle, summary, or license; with JavaScript off the full list is shown.

Updated 2026-10-05 · Outerloop