Examples Auto Run

Defaults (overridable via env)

• EXAMPLES_INTERACTIVE_MODE=auto
• EXAMPLES_INCLUDE_INTERACTIVE=1
• EXAMPLES_INCLUDE_SERVER=0
• EXAMPLES_INCLUDE_AUDIO=0
• EXAMPLES_INCLUDE_EXTERNAL=0
• Auto-approvals in auto mode: APPLY_PATCH_AUTO_APPROVE=1, SHELL_AUTO_APPROVE=1, AUTO_APPROVE_MCP=1

Log locations

• Main logs: .tmp/examples-start-logs/main_*.log
• Per-example logs (from run_examples.py): .tmp/examples-start-logs/<module_path>.log
• Rerun list: .tmp/examples-rerun.txt
• Stdout logs: .tmp/examples-start-logs/stdout_*.log

Notes

• The runner delegates to uv run examples/run_examples.py, which already writes per-example logs and supports --collect, --rerun-file, and --print-auto-skip.
• start uses --write-rerun so failures are captured automatically.
• If .tmp/examples-rerun.txt exists and is non-empty, invoking the skill with no args runs rerun by default.

Behavioral validation (Codex/LLM responsibility)

The runner does not perform any automated behavioral validation. After every foreground start or rerun, Codex must manually validate all exit-0 entries:

1. Read the example source (and comments) to infer intended flow, tools used, and expected key outputs.
2. Open the matching per-example log under .tmp/examples-start-logs/.
3. Confirm the intended actions/results occurred; flag omissions or divergences.
4. Do this for all passed examples, not just a sample.
5. Report immediately after the run with concise citations to the exact log lines that justify the validation.