[nuwandavek]

Thanks! Not sure, I think the term has been in the ether for a while.

Yeah, I see that too. I think for the longest time there was no leverage in doing this sort of retrofitting (except for grammarly type of use cases). But with better intent capture (llms help here), we can actually fix up any existing gaps!

[Erazal]

A Grammarly-style retrofit would’ve actually been appropriate here—I made a syntax error.

If you don’t mind, I’ll be stealing and using that analogy!

We were talking about that approach today with a friend who unifies parking apps across the country. He calls his engine UMM—Ultimate Macro Machine.

I’m working in the “classic” generic browser-automation agents with a unified API for meeting bots (transcription, voice input, etc.).

[nuwandavek]

Haha, the analogy is totally yours to use :) Nice, yeah, there is a lot of leverage in building agent-like hooks into current workflows. Even if the agents are pretty mid right now (they are for any complex use case that needs long horizon planning), it's a great place to be in time for the next generation models to drop!