Repository navigation
v0.8.3 — Agent loops that stop honestly, a guard against unverified "done", and a faster check
This release helps you build AI agent loops that stop when the work is genuinely finished, closes a hole where a feature could look done without its tests ever running, makes the pre-push check faster, and ships native Japanese and Chinese documentation.
If you build your own agent loop, cladding now gives that loop an honest "are we actually done?" answer and a clear "here's what's still broken" list. These loop features are for loop engineering — they harden when the loop may stop and what it fixes next, not the AI's code quality (cladding's own A/B testing is the receipt: this kind of governance is separate from code correctness).
Heads-up — two things to know when you upgrade:
- The strict check now flags any feature marked done whose declared tests don't actually run. A feature that looked green but was never truly verified will surface after upgrade.
- Setting up a project now also writes an
AGENTS.mdfrom your spec, so AGENTS.md-aware AI tools pick up your project's context on their own. Your existing files aren't touched.
Added
- Tell your agent loop when it's genuinely finished — a read-only check answers "is this actually done?" using the very same gate as a real completion; it only reports, it never changes anything.
- The loop gives up gracefully instead of spinning — when repeated attempts stop making progress, it escalates rather than looping forever.
- The loop remembers what already failed to build — past build failures are fed back in, so the AI stops resubmitting the same broken fix.
- Errors come back as exact file-and-line pointers, so the loop fixes them in one pass instead of re-running just to find where the problem was.
- New projects get an
AGENTS.mdgenerated from their spec (closes #199), so any AGENTS.md-aware AI tool inherits the project's intent; cladding's own copy is protected from being overwritten. - More toolchains detected — Swift, Flutter, Dart, plus TypeScript-with-Jest and mixed-file-extension projects.
- Native Japanese and Chinese READMEs — written natively, not machine-translated, with translated diagrams. The docs switch between English · 한국어 · 日本語 · 中文.
Changed
- The pre-push check runs your tests once, not twice (closes #215) — about 28% faster, with the "did the tests really run?" guard fully intact.
- Tidier evidence bookkeeping — some spec entries record their supporting material more accurately, and the self-check emits a standard test report.
- The tool self-checks its own advertised detector count, so the docs can't quietly drift from the code.
Fixed
clad checkno longer crashes when its output is piped into something that stops reading early — likehead(closes #221).
Security
- Closed a "looks green but was never verified" hole — a feature marked done whose tests don't actually run is now caught. cladding treats a check that can be tricked into a false pass as a trust issue, and this closes one way it could be tricked.