The second milestone of Exerakt: a client that reads Matrix messages the way Element shows them. The interesting problems were not in drawing but in other people’s code, and every feature was checked side by side with Element.
Why Exerakt is written for Wayland only and draws its own interface instead of using a cross-platform toolkit, how this choice was checked in the first milestone, and how the result compares with Element.
What 204 questions asked to both Jev and Claude showed: Jev is almost never confidently wrong, it is unsure on the questions that need careful reading, and the data says almost nothing about how well it catches problems.
How the local Bonsai model did as the executor over 28 cards: the logic was almost always right, and almost every failure was code that did not compile. And the mistake I made in how I ran it.
How Claude, Jev and a local Bonsai model are put together into one pipeline, and what its first run showed: most failures that looked like the executor’s were mine.
Why I started Exerakt: to see how far models can get writing a real program on their own, in a structured process and without a big bill, and to get a Matrix desktop client I actually want to use.