Documentation
Reference material for running loop: how a run moves through its phases, every key in loop.yaml, and how prompt templates shape what the agent sees. These pages are rendered from the docs/ folder of the repository.
Command reference
Every command looks for loop.yaml in the current folder or any parent; -C <dir> points it elsewhere. Items are addressed by anything a source understands: login
Workflow, gates and merge policies
monitor polls the PR every workflow.poll_interval and decides in this order:
Configuration reference (loop.yaml)
Paths are relative to the folder containing loop.yaml. Durations use Go syntax (45m, 1h30m, 90s).
Prompt templates
Templates are Go text/template files. loop init copies the built-in defaults to prompts/ so you can edit them; loop show <item> --prompt prints the rendered ses
Security
loop hands an autonomous agent a checkout of your repository, the text of your tickets, and the ability to commit. This page lists what loop does to keep that c
Session with comments
Session prompt template shown as source.
Session without comments
Session prompt template shown as source.