love these guys. instead of spending time on something akin to those creepy "dots" or obnoxious @Claude in Slack, they ship actual improvements to speed. you can't imagine what kinds of UX a fast LLM can enable! and for coding I have always been a proponent of strong compile-time type systems and handing off only the actual boilerplate typing, all to maximize actual thinking and speed of high-precision prototyping.
I actually built a small prototype that integrates with JetBrains IDEs - it tracks your in-IDE activity (kinda like JetBrains' own "file-scale tab-completion" feature) but you can invoke Codex with all that context at any moment to let back-then GPT-5.4-nano finish the miniature task. say, you wrote a new use case and your goal is to expose it through a new endpoint, but it's kinda boilerplate-y and DRY is not your style either. then you open a needed file, press a shortcut, tell what you want, and you get it. JetBrains Air kinda absorbed that functionality, Codex tokens are hella expensive (don't get me started on API costs), and JetBrains is ready to front that cost through "Junie Lite" (which is currently Qwen 3.6 27B), so I decided to abandon that prototype. but I do miss the combination of speed and control over resulting code.
I may revisit this idea with Mercury 3, or ask JB to integrate it.
I will argue that part of the push for this kind of new and novel methods are because the "dots" style of applications demand new technologies to work better.