Looper-Go Live Test
Overview
Run a real looper-go iteration in a fresh temp directory to validate task selection and summary application, then report what happened.
Workflow
- •Locate the
looperbinary. Preferlooperon PATH; otherwise setLOOPER_BINto a specific path (for example~/looper-go/bin/looperorgo run github.com/nibzard/looper-go/cmd/looper). - •Run the helper script:
~/.codex/skills/looper-live-test/scripts/run-live-test.sh - •Watch the output until it finishes; note the
Task:line andSummary:line. - •Inspect the temp project directory printed by the script; check
to-do.jsonand any created files. - •Report: selected task line, summary line, files created, and any errors or unexpected behavior. Mention the temp dir path.
Manual fallback (only if the script cannot run)
- •Create a temp directory and
PROJECT.md. - •Create a
to-do.jsonwith tasksT10andT2(both priority 1). - •Run:
MAX_ITERATIONS=1 looper run - •Observe output, then inspect
to-do.jsonand created files.
Looper-Go Specific Notes
- •Looper-Go uses
looper runas the main command (notlooper.sh to-do.json) - •Configuration is loaded from
.looper/config.json, environment, or CLI flags - •Logs are stored in
looper-logs/runs/<run-id>/events.jsonl - •Use
looper doctorto check dependencies and configuration