AAWEA.ORG

Investigation Script Loop

Write a small throwaway script to reproduce a bug, run it, read output, and iterate until the root cause is proven.

👁 1,544 views 📥 1,031 installs 👤 by loops!

Manual start

↓

1

Write probe script

Create a ~20-line script that reproduces the bug or queries the failing state. One file only.
2

Run and read

Execute the script and capture stdout/stderr. No guessing — read actual output.
3

Adjust hypothesis

Update the script or notes based on output. Stop when root cause is demonstrated.

↓

✓

Exit condition: manual

Root cause demonstrated by script output with a written summary

📊 Flow Diagram

flowchart TD Start(["Manual start"]) Start --> S0 S0("Write probe script") S1("Run and read") S0 --> S1 S2("Adjust hypothesis") S1 --> S2 Exit{"Root cause demonstrated by script output with a written summary"} S2 --> Exit Exit -- "No" --> S0 Exit -- "Yes" --> Done(["Success"]) style Exit fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#92400e style Done fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#065f46

Run "Investigation Script Loop" in your agent

Prompt only

Deeplinks and "Open in Cursor" only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace.

Kickoff prompt

Start the "Investigation Script Loop" loop.

Goal: prove the root cause with a minimal repro script
Max iterations: 8
Between iterations run: node scripts/investigate.mjs
Exit when: script output demonstrates root cause

Step 1: Write a tiny throwaway script that reproduces the issue. Run it and iterate on what the output shows.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.