Interesting project, thanks! Quick reactions from trying it out: One of my questions about this is the same as my question about "low-code" tools-- how they enable novices to debug errors or edge cases in the generated code. Example: I played the tower defense style game example you linked in the comments for a few minutes, and found a bug (or perhaps a gameplay edge case I'd want to treat differently: a second bulle…
As of right now you still need to be familiar with the code that it gives you. But personally even when I work on a game I resolve bugs by chatting with the AI about it. We're also trying to surface any kind of actual errors that happen so you can feed it back to the AI. So far I haven't seen a bug I can't fix in this way, but then I've been coding for 20+ years.
As for the "//...rest of the code" stuff, yeah it's my white whale. We're just limited by the context size. We have a bunch of things coming up to separate the code into multiple files and various tricks to squeeze more of the context size. It's a constant battle.
Another thing we're toying with is automatic debugging that lets it go back and forth on bugs until it actually works.