
By Thomas Cohen, founder of Maestro
Behind an application update: a signed-out assistant no longer goes unnoticed
A tester tells us they installed their AI assistant without ever signing in. The software treated 'please sign in' as completed work. Here are the three fixes released in version 0.1.17, and the two defects we are leaving open until the next pass.
An entire application update can come down to a misread sentence. A beta tester wrote, 'it installed Claude for me but I never signed in' (beta feedback, August 31, 2026): their assistant returned 'Not logged in' among its normal responses, and our software treated that line as delivered work.
An error that does not look like an error
A failing program ordinarily reports it through a separate channel reserved for errors, which the calling software monitors. This assistant reports its missing sign-in through the ordinary response channel. From our side, nothing distinguished the line from a short result. The conversation closed, the step was marked complete, and the tester faced a product showing finished work when no work had happened. They thought Maestro was broken; we thought their assistant was running.
One detector at all three exits
The fix follows one principle: the same check everywhere an assistant response becomes an accepted fact. We had three such places: the conversation workshop, monitoring work in progress, and execution of a method step. A single detector now reads the response before it counts, recognises forms of 'you are not signed in', and turns the false result into a clear message with the action to take. It is the discipline we learned with our notification bell: one path, never two.
We added a probe before the session's first job: it asks whether the assistant is ready to respond, caches the result, stops itself after three seconds, and never blocks startup. Installation from the application now leads to the sign-in screen instead of leaving you to think everything is ready. Our first tester had already hit the same wall, for another reason: twice in a row, the product left someone facing a screen that did not tell the truth about its own state.
The banner that was wrong
The second fix that evening. When you take over existing software, Maestro displays a banner saying code analysis is in progress. It also appeared for new projects, where there was nothing to analyse, and stayed on screen after analysis finished. A banner that remains lit after the event it announces teaches readers to ignore it; when it eventually says something important, they no longer see it. It now disappears as soon as analysis ends and never appears for a project created from scratch.
No approval gate on an empty document
The third fix is the most useful for a business owner. The product asks you to approve each document with 'Looks good to me'. When an assistant returned an empty shell, the document arrived almost blank but the approval gate still appeared, inviting you to approve nothing. An empty document is now recognised: no gate, a card saying 'remained empty', and a button to redo the work. Approval only matters when there is something to approve: that is the whole point of this gate.
What we are leaving open
Two known remaining issues, written here so we do not forget them: manually stopping a workflow launched outside our method is not recorded in the activity feed, and a macOS banner displayed by the application is not removed when its purpose has passed. Neither causes lost work. They will be fixed in a later pass. Version 0.1.17 was published and distributed on the evening of August 31, 2026: existing installations updated themselves.
In practice
If you test a tool that controls an AI assistant, try the experiment our tester inadvertently gave us: deliberately sign out of the assistant, then launch a job. A good tool tells you in one sentence what is missing and what to do. An average tool displays a completed step. The latter will waste hours before you realise nothing ever ran. Do the same with a document: request a specification, cut the network halfway through, and see whether the tool still offers to approve the result.
Read the complete guide: build an application without coding