loop-runner v1.1A

Immutable. This exact content is served forever at /api/v1/blob/6491c61915a112c4.

---
name: loop-runner
description: Execute and manage loop engineering primitives (init, run, status, audit) from an AI coding
  session via the agent-toolkit loop CLI.
origin:
  type: first-party
metadata:
  author: ulises-jeremias
  version: '1.1'
---
# loop-runner

> Execute and manage loop engineering primitives from an AI coding session.

---

## What this skill does

This skill wraps the **`agent-toolkit loop`** CLI (V product command), exposing loop
operations to AI coding agents without requiring the user to remember CLI flags.

**Loop engineering** is the practice of designing recursive, autonomous processes
that prompt AI agents — as opposed to prompting agents directly. Loops have
durable state (`STATE.md`), safety gates (allowlist/deny), cost budgets, and
rollout tiers (L1 report-only → L2 PR-gated → L3 unattended).

## Capabilities

| Subcommand | When to use |
|-----------|-------------|
| `loop init <pattern>` | Scaffold a new loop from a starter |
| `loop run <loop>` | Execute one loop iteration |
| `loop status` | Show all loops: tier, cadence, last run |
| `loop audit [loop]` | Summarize past run success/cost |
| `loop cost <loop>` | Estimate per-run token cost |
| `loop schedule <loop>` | Install systemd/launchd timer |
| `loop sync` | Push escalations to knowledge/todos |

## How to invoke

```bash
# Preferred — agent-toolkit V CLI
agent-toolkit loop status
agent-toolkit loop run daily-triage
agent-toolkit loop init oss-pr-monitor
```

Historical note: older docs referred to `./bin/loop` or `~/.ai-workspace/bin/loop`.
Those entrypoints are obsolete; use `agent-toolkit loop` after installing via
brew / AUR `agent-toolkit-bin` / GitHub Release / `uv tool install agent-toolkit-cli`.

## Routing

1. Prefer `agent-toolkit loop …` on PATH (V binary or PyPI launcher)
2. Otherwise guide the user to install per `docs/INSTALLATION.md`

## Runner hierarchy

When `agent-toolkit loop run` dispatches a loop, it tries runners in this order:

| Priority | Runner | How to enable |
|----------|--------|---------------|
| 1 | **runner** | `export HARNESS_RUNNER_DIR="$HOME/.local/share/agentic-workstation/dev-companion/runner"` |
| 2 | **`claude --print`** (Claude Code CLI) | `claude` in PATH — zero setup for Claude Code users |
| 3 | Skeleton plan | Always available |

For full multi-provider support (Anthropic, OpenAI, Ollama, OpenCode), set
`HARNESS_RUNNER_DIR` to point at the runner. Claude Code
users can skip this — `claude --print` is used automatically.

## References

- [agentic-harness loop docs](https://github.com/ulises-jeremias/agentic-harness/blob/main/docs/LOOPS.md)
- [Loop engineering patterns](https://github.com/cobusgreyling/loop-engineering)
- [docs/LOOPS.md](../../../docs/LOOPS.md) — full reference

---

## Rules

1. **Always start at L1** for new loops. Only graduate to L2/L3 after reviewing
   at least 3 consecutive clean L1 runs.

2. **Budget awareness** — report the estimated cost before running an expensive
   loop (pr-babysitter, ci-sweeper). Confirm with the user.

3. **Allowlist enforcement** — never take an action not in the loop's
   `allowlist`. If uncertain: escalate (`human_escalation` exit condition).

4. **Worktree hygiene** — loops create isolated git worktrees. Clean them up
   on success; preserve on failure for postmortem.

5. **Escalation first** — when in doubt, choose `human_escalation` over
   guessing. The user can always re-run.