Original community demo · Video hosted on X
Input assistance
A community prototype explores a Next Edit Suggestion feature using Jev to anticipate a developer’s next change.
Opens the author's original post in a new tab.
The implementation ideas below are our interpretation of the community demo. Check the original post for the author’s actual setup.
An editor can suggest a likely follow-up action after a rename or a repeated change, keeping acceptance under the developer’s control.
Read a small editing context, build candidate follow-up actions, rank or select a candidate, and show a preview that the developer can accept or dismiss.
These examples explain a possible workflow; they are not recorded demo results or API request and response formats.
This is an experimental editing feature, not a complete code-generation system. Suggestions need syntactic validation and may be wrong when wider project context is missing.
Define the context and a small set of choices in the playground, then use the API guide to connect your application.
View demoA browser-extension experiment identifies advertising elements in the DOM and hides the elements it flags.
View demoA related Qwen-based experiment predicts categorical outputs for multiple JSON keys together on an Apple Silicon laptop.
View demoA PostgreSQL extension applies natural-language criteria to rows, exploring semantic filtering inside the database.
