My Helix fork tutors me

The other day I wrote about how I'm now writing in a WebAssembly fork of Helix. This is working great, even though (i) my vim / Helix knowledge is uneven and (ii) the WebAssembly fork is still buggy. Some extra infrastructure is addressing both of these problems: The editor now saves a rolling history of my N most recent keypresses and recent states of the buffer. Every so often, this information gets sent to a decision model, which determines whether it describes some sort of Helix user error or inefficiency. If the decision model says "yes" with sufficiently high confidence, the same information is sent to a slow LLM, which generates a prose description of what I did wrong and can improve. The recent states of the editor are also sent to an LLM when I request code changes via an Improve button at the top of the screen. Here's what it looks like when a tip pops up: And here's the Improve modal: Some further notes: Constant monitoring combined with decision-model judgments (or some…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town