oloop/canary
oloop/canary@1.0.7
sha256:42faddb25ed8… full digest
sha256:42faddb25ed83a5d16a9cd340a59c47ff45ca9fa40f80cc57207df0e0549008f
License: MIT
Resolves to your machine and records what it chose.
What this agent may touch
tools.allow | write · edit · read |
tools.deny | (none declared) |
Run this
oloop exec oloop/canary@1.0.7
This command fetches version 1.0.7. A row for an existing server needs that server to be running.
Saved tracks the artifact entry, not a version pin. A return visit keeps this version visible and never merges a newer version's evidence.
Long form: pull, then run
oloop pull oloop/canary@1.0.7
oloop exec manifest.yaml
Bundle bytes are delivered by oloop pull; pulling needs a free handle.
AGENT.md
# Canary
Write `OK` to `answer.txt` with the write tool, then stop.
It is the official Outerloop canary: the smallest manifest that proves the
publish → pull → run → verify loop on a real machine.
Its manifest
Read the manifest at manifest.yaml.
# Writes one file and stops, so the check is mechanical.
schemaVersion: 2
license: MIT
task:
prompt: "Write OK to answer.txt with the write tool, then stop."
workdir: "{{WORKDIR}}"
params: { timeoutMs: 240000, temperature: 0 }
runtime: { model: ollama/qwen3.8:latest, harness: opencode, router: none }
tools: { allow: [write, edit, read] }
oracle: { type: file_exists, target: answer.txt }
How it is judged
The oracle checks whether the named file exists. It does not check the file's contents.
Versions
All versions: dates, messages, digests, and compare links.