0.9.0

Six defects, all of them found by exercising what the app promises on its own screens.

A dropped connection said "network error" — English either way, past the reach of any dictionary, printed in red in the middle of a conversation written in Portuguese. It also withheld the one fact that matters: the server is the reader's own, and it stopped.

The research blamed the search engine for everything. A request with no question ran the whole pipeline for nine seconds before saying "no search results". And DuckDuckGo answers a blocked request with HTTP 200 and an anti-bot challenge page, so "no results" was what appeared when waiting would have fixed it. The block is now recognised and named, and the reason travels to the final error.

The research report opened with the model discussing its own tooling — "simple writing task from a single source, not worth fanning out agents". That cost more than tidiness: the same prose broke the JSON parse of the search plan, so the planner fell back to searching the question verbatim and the research read one source instead of four. With the prompt fixed it plans four angles and reads four.

The empty-state sentence contradicted itself, saying "you already turned on 2 AIs" and "both are turned off" in one line — and blaming the reader for AIs the app found by itself.

Verified along the way and found sound: the whole chat screen (ask, regenerate, edit, delete, export, automatic title), first run on a machine with no AI installed at all, the anonymous chat — which really does store nothing — and the file-editing mode, with a path outside the project folder refused.