Skip to content

0.4.7: a gate's instruction restarts the loop breaker; stops say why - #85

Merged
mjwsolo merged 4 commits into
mainfrom
release/0.4.7
Sep 26, 2026
Merged

mjwsolo merged 4 commits into
mainfrom
release/0.4.7

Conversation

@mjwsolo

@mjwsolo mjwsolo commented Sep 26, 2026

Copy link
Copy Markdown
Owner

The plateau breaker kept its no-progress count running across gate send-backs, so after the placeholder gate (or the todo gate, or the build-errors gate) told the model to do new work, the breaker could stop the session seconds later while it was reading the file it had just been told to fix. Seen live three times today. Every gate send-back now calls plateau.freshInstruction(). When the breaker does stop a session it shows a toast with the round count and files changed. Plugin-only; no binary change. Unit test added; the 4 remaining bun failures are the known pre-existing ones.

…p says why

The model was stopped 9 s after the placeholder gate sent it back to fix a line,
because the no-progress counter still ran from a nudge 48 minutes earlier. Every
gate send-back (open todo, placeholder, build errors) now restarts the budget. When
the breaker does stop a session it shows a toast with the round count and files
changed instead of a bare 'Interrupted'.

(cherry picked from commit 24e3d5c)
test_completed_download_flips_to_done failed on CI with progress_pct 6 after status
'done': a progress line from a worker flushing its last output (or a stale worker for
the same key) landed after completion and moved the entry backwards. Terminal entries
are now immutable to progress updates.
@mjwsolo
mjwsolo merged commit a59694d into main Sep 26, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant