Master Controller is the request ledger. Every ask you make is logged, tracked and checked off, so a model that stops halfway cannot tell you it finished. Open it and see exactly what was done and what is still owed.
The model said it was finished. The ledger says six rows are still open.
“It prematurely stops after completing only a portion, then provides a summary as if the entire task is complete.”
GitHub · anthropics/claude-code, TodoWrite premature-stop, v1.0.85. One filed case finished phases 1 to 3b and left 4a, 4b, 5 and 6 marked [NOT STARTED].
View the source ›
The model deciding it is finished is the model's bug. Whether you find out is ours. Master Controller keeps an independent ledger of every request, so a half-done run shows as half-done instead of reading like a success. You re-queue the tail in one click, from any device.
Every request is tracked as its own row, with its state. A summary that claims completion does not clear the row.
The things still owed to you, in one place, so you can see the tail of a run that quit early.
Click the name to see everything it does and switch individual pieces off. It is a tool, not a nanny.
Nine phases planned, three finished, a confident summary. The ledger still shows six open rows. You re-queue them without rereading the transcript to work out where it stopped.
Things you are still owed, in one place, on every device.
Every part of Master Controller is switchable. Run the full ledger on a production repo and turn most of it off for a scratch session.
Click the name to see everything it does and turn parts off.