I'm not sure the utility of this kind of stuff anymore. It's relatively easy to sketch a layout on a napkin + prompt and then prompt claude code to use python textual as as TUI layer. I've had pretty good success with Textual+Claude so have a few colleagues. You could probably use Figma + claude etc as well.
lazygit supports vim style keybindings and mouse click and scroll. I mostly use the key shortcuts but sometimes the mouse is useful. But i agree that a well thought out state machine that can be navigated through via keyboard is a dream to work with. Lazygit is superb. But this is not a distinction between TUI and GUI.
My main concern is not that a direct Claude command is prompt injected to do something evil but that the generated code could be evil. For example what about simply a base64 encoded string of text that is dropped into the code designed to be unpacked and evaluated later. Any level of obfuscation is possible. Will any of these fast scanning heuristics work against such attacks? I can see us moving towards a future where ALL LLM output needs to be scanned for finger printed threats. That is, should AV be running continuous scans of generated code and test cases?
> the only viable solution becomes giving the movement its demands.
This interpretation reeks of Western naivete. Students were not merely arrested — they were gunned down en masse in the streets and even in hospitals. They were provoked by the U.S. president, who promised support to take on the institutions, but that support never materialized. The likely endgame of this current gunboat diplomacy is similar to Venezuela: the U.S. secures resource access while leaving the existing system intact, and the student protesters are hunted down. In other words, nothing changes for the people demanding reform.