Try the demo: what should a coding-agent run prove before it continues?

[Keesan12]

The interactive demo is live now: https://martinloop.com/demo

The question I want to sharpen is simple: before an AI coding agent gets another attempt, what proof should it have to show?

The shape MartinLoop is testing is:

• remaining budget
• verifier movement
• failure class
• changed files
• rollback evidence
• explicit halt reason
• a run receipt a human can inspect later

The point is not to slow agents down. It is to stop the loop from spending credits on the same failure while still letting useful attempts continue.

If you are already running Claude Code, Codex, OpenCode, Cursor, or similar loops, I would love blunt feedback on the demo:

• what signal is missing?
• what would make you trust the stop/continue decision?
• what would make this worth trying from npm on a real run?

Fast path:

• demo: https://martinloop.com/demo
• npm: https://www.npmjs.com/package/martin-loop
• repo: https://github.com/Keesan12/martin-loop

If this kind of guardrail belongs in your stack, a star helps keep the OSS version alive.