Is there any indication of what compute resources this will actually require (in its various incarnations)? Does it incorporate any of the optimisations pioneered by Google (such as TurboQuant, MTP) or some other original innovations to make the frontier quality realistically available to local users?
This is pretty cool as a prototype, nice job! I'd say it needs some progression (one-on one to one-on-multiple, think 1xL against 2xS, etc.), as well as some more map variation (channels, islands, hazards like a giant whirlpool, kraken, the works). As a final shape, multiplayer would be pretty cool, but of course that's quite a bit more difficult... But I for one would be there for it :)
Ah, the xterm "read title" bug, I seem to remember that was fixed some while ago, wasn't it? But yes, that is true, it's possible to exploit anything with enough determination; it wasn't that long ago that "viruses in image files" was a joke, but then we had the Android wallpaper bricker a few years ago... In the meantime, we have a few more layers of indirection between the code and the user, each one of them adding potential surfaces.
Maybe not a vulnerability per se, but definitely conducing to ones, as others have noted. However, those completions are quite unfortunate to say the least, thus one would hope JetBrains would endeavour to improve the local (S)LM they're using, or at least offer the user the option to use one of their own, better tuned ones instead?
Well, technically it's not the curl itself that is the problem, but the "| <shell>" coming afterwards that does the damage. So, if the process is somehow broken up into 1) curl <the_script>; 2) analyse <the_script> and 3) only if safe, then execute <the_script> -- then it's not nearly as bad. Of course, that "analyse" step does all the heavy lifting, and if it happens to involve some form of local LLM then... excitement is guaranteed as they say.