From 02f6e4911b9f34f3dadd98d87b4dd704effb72fb Mon Sep 17 00:00:00 2001 From: Anton Osika Date: Sun, 16 Jul 2023 17:41:40 +0200 Subject: [PATCH] Improve roadmap phrasing --- ROADMAP.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ROADMAP.md b/ROADMAP.md index fd8994d..688619b 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -7,20 +7,20 @@ There are three main milestones we believe will greatly increase gpt-engineer's ## Our current focus: -- [x] **Continuous evaluation of our progress ๐ŸŽ‰** +- [x] **Continuous evaluation of progress ๐ŸŽ‰** - [x] Create a step that asks โ€œdid it run/work/perfectโ€ in the end of each run [#240](https://github.com/AntonOsika/gpt-engineer/issues/240) ๐ŸŽ‰ - [x] Collect a dataset for gpt engineer to learn from, by storing code generation runs ๐ŸŽ‰ - [ ] Run the benchmark multiple times, and document the results for the different "step configs" [#239](https://github.com/AntonOsika/gpt-engineer/issues/239) - - [ ] Document the best performing configs + - [ ] Improve the default config based on results - [ ] **Self healing code** - [ ] Run the generated tests - [ ] Feed the results of failing tests back into LLM and ask it to fix the code - [ ] **Let human give feedback** - - [ ] Ask human for what is not working as expected in a loop, and feed it into GPT4 to fix the code, until the human is happy + - [ ] Ask human for what is not working as expected in a loop, and feed it into LLM to fix the code, until the human is happy - [ ] **Improve existing projects** - [ ] Decide on the "flow" for the CLI commands and where the project files are created - [ ] Add an "improve code" command - - [ ] Design how gpt-engineer becomes a platform + - [ ] Architect how gpt-engineer becomes a platform - [ ] Integrate Aider ## Experimental research