Sunday planning

[AntonOsika]

Publicly sharing preparation for planning of what to work on today for myself!

• Finalise benchmarks, create a table of results ✅ ❌ 📈 @carthome @AntonOsika
• Add a "did it work" step, and take that input to improve the codebase
• Prompt engineer a graceful exit 🪦
• Add a "run over all files" and prompt to automatically "improve/fix" them step: This should solve the "placeholders" problem 🏃 @AntonOsika
  • Can be done in parallel to speed things up 🚀
• [Enabler] Functionality to generate and apply diffs to existing files, given a file and a prompt
  • This would allow us to use GPT Engineer on existing codebases ✨
• Add functionality for a human to go over existing code, write comments, and then let GPT Engineer address all comments in the code by rewriting files with comments 🙋‍♂️🤖

[AntonOsika]

Regarding this step:

• Add functionality for a human to go over existing code, write comments, and then let GPT Engineer address all comments in the code by rewriting files with comments

A solution could be that GPT Engineer is pointed to a codebase, snapshots it, goes into "listening mode" monitoring diffs continuously, and when a human writes "ai:ready" in the codebase it will immediately replace ai:ready with AI:PROCESSING, and try to rewrite that file completely.