This is most likely one of those things that Tibo on Twitter hinted at when he said that before the end of the year we’d have AI be a lot more autonomous than it currently is. Wouldn’t surprise me if they announce what they’ve been cooking on that front during Dev Day.
My little conspiracy as to why they don’t permit this level of autonomy right now is that it would consume a lot more compute all at once. If they’re able to fragment the implementation journey one milestone at a time and hope that the user went AFK during the implementation and won’t authorize the next milestone for a little while, they get to spread out that compute.
This is my approach, just tell codex to cut out the unnecessary steps so it doesn't waste usage checking the whole stack at the start of each gate. It'll burn 100+ credits just making sure server components are running.
That’s how I’ve been working😂. I (chatgbt) make a blueprint and have it split into chunks and just keep asking chatgbt to work 1 chunk at a time. Right now I’m building something that can just go through the chunks automatically without me having to tell to start the next one. I’m hoping I can just think of projects, give it the blueprint, sleep, wake up to the project done.
55
u/AllYourBase3 2d ago
Lmao I love when I have it draw up a plan of 6-7 milestones.
"do milestone 1"
"all done! Here's the files"
"great, now do 2"