OP here - this is Part 2 of a series documenting how we built NES (Next Edit Suggestions), our real-time edit model inside the Pochi editor extension.
The real challenge (and what ultimately determines whether NES feels “intent-aware”) was how we manage context in real time while the developer is editing live. For anyone building real-time AI inside editors, IDEs, or interactive tools.
I hope you find this interesting. Happy to answer any questions!
OP here - this is Part 2 of a series documenting how we built NES (Next Edit Suggestions), our real-time edit model inside the Pochi editor extension.
The real challenge (and what ultimately determines whether NES feels “intent-aware”) was how we manage context in real time while the developer is editing live. For anyone building real-time AI inside editors, IDEs, or interactive tools.
I hope you find this interesting. Happy to answer any questions!
Interesting, I'd love to figure out how we could do something like this in tambo.
Basically, listening to the user's interactions and suggesting different interfaces or tasks they could use for the assistant.
Thanks for sharing.
Emacs hippie-expand has a lot of lessons to teach here (not all of them good). Even traditional Emacs dabbrev could do the same ...