This repository demonstrates how a simple iterative coding loop, with history and resume capability, can be can be implemented in the AutoGen Framework.

This project is the result from an extension of the paradigm demonstrated in AutoGen_MemoryManager(MAKE THIS A LINK), where allowing an agent to have a fixed, trustworthy memory relieves the cognitive burden that would otherwise be necessary to achieve the desired effect. The inspiratiom for this work comes from the author's personal struggles in achieving performant code from the AutoGen Examples for use-cases sufficiently different than those in the example. While in its current state this flow is able to achieve better results on cases that failed in the examples, this Repo should also serve as an example of a more generic code production workflow.

(CONSIDER A DIAGRAM SHOWING THE BREAKDOWN OF STEPS)

Currently this Repo only works to produce python code. With some work, this can be adapted.

(MAKE SOME CONTENT FOR AN EXAMPLE)

The program runs in two phases: the Planning Phase, and the Iterative Phase.

The planning phase consists of a chat between the human user (Manager) and an AI Planner assistant (Planner). The Manager is first prompted:

What python creation would you like? Type below:

Here the Manager can request the python app they would like. Eg:

Make me a python app that displays the current time on an analog clock face.

The Planner will then create a list of functional requirements that define a successful completion of the task. If the Manager deems the plan sufficient, they can direct the plan to be saved.

This concludes the Planning Phase.

The iterative phase consists of individual chats between the Manager and either the Programmer, or the Reviewer.

If coming directly from the planning phase, the Iteration phase will begin with the Programmer producing the first attempt at satisfying the plan.

The Programmer's output will be recorded to a python script file in the working directory, starting at script_v1.py.

The reviewer will then be presented with the Plan and the content of the most recent script, and is asked to evaluate the code and produce a list of criticisms/comments to be used to guide the next iteration.

The Manager can also test the code if desired and provide feeback to the reviewer or programmer.

After the first iteration, the main iterative loop begins.

The programmer will be presented with the Plan, the latest code iteration, and the latest reviewer comments. They will then produce another iteration of the code, attempting to resolve the reviewer comments while also adhering to the plan.

The reviewer will then be presented with the Plan and the content of the most recent script, and is asked to evaluate the code and produce a list of criticisms/comments to be used to guide the next iteration.

The Manager can also test the code if desired and provide feeback to the reviewer or programmer.

The author assumes you have installed AutoGen and have it running on your system.

Before you begin, be sure the directory defined in working_dir exists in the active directory - this is where the Plan will be stored, as well as all script iterations.

Also, be sure the file AndyTools.py is in the same directory as IterativeCoding.py - this contains overridden AutoGen GroupChat and GroupChatManager classes to allow manual control of group chat speakers.

To start a fresh project, be sure the working_dir contains no files.

Start the program with python IterativeCoding.py

The planning phase will begin with the User entering the desired application:

Make a python app that writes the current time to an analog clock.

After hitting Enter, the User will be prompted to direct who speaks next:

Who speaks next: planner

The user should enter planner to allow the planner to produce an initial plan:

Plan:

1. Create a graphical user interface (GUI) for the analog clock.
2. Implement a function to retrieve the current time.
3. Implement a function to convert the current time into the corresponding positions of the clock hands.
4. Update the GUI to display the clock hands at the correct positions based on the current time.
5. Continuously update the clock display to show the current time in real-time.

---

Who speaks next:manager

After the planner responds, the user should direct the manager to speak next. If the user desires other features be included, or has any problems with the plan, they can tell the planner what changes they desire. After this, the user should allow the planner to speak again.

Once the planner returns a plan that is acceptable, the user should say "sounds good" through the manager. The user should then direct the recorder to speak next. The recorder will make a function call to write the Plan to the working directory, finalizing the application requirements. The manager must be used to execute the function call by sending a blank response (auto-reply). The manager must then exit the conversation to conclude the planning phase.

A full planning phase will run something like this:

What task do you ask? Type it below: Make a python app that writes the current time to an analog clock ←[33mmanager←[0m (to chat_manager): Make a python app that writes the current time to an analog clock -------------------------------------------------------------------------------- Who speaks next:planner ←[33mplanner←[0m (to chat_manager): Plan: 1. Create a graphical user interface (GUI) for the analog clock. 2. Implement a function to retrieve the current time. 3. Implement a function to convert the current time into the corresponding positions of the clock hands. 4. Update the GUI to display the clock hands at the correct positions based on the current time. 5. Continuously update the clock display to show the current time in real-time. -------------------------------------------------------------------------------- Who speaks next:manager Provide feedback to chat_manager. Press enter to skip and use auto-reply, or type 'exit' to end the conversation: Can you make the hour hand pink too? ←[33mmanager←[0m (to chat_manager): Can you make the hour hand pink too? -------------------------------------------------------------------------------- Who speaks next:planner ←[33mplanner←[0m (to chat_manager): Adjusted Plan: 1. Create a graphical user interface (GUI) for the analog clock. 2. Implement a function to retrieve the current time. 3. Implement a function to convert the current time into the corresponding positions of the clock hands. 4. Update the GUI to display the clock hands at the correct positions based on the current time. 5. Adjust the color of the hour hand to pink. 6. Continuously update the clock display to show the current time in real-time. -------------------------------------------------------------------------------- Who speaks next:manager Provide feedback to chat_manager. Press enter to skip and use auto-reply, or type 'exit' to end the conversation: sounds good ←[33mmanager←[0m (to chat_manager): sounds good -------------------------------------------------------------------------------- Who speaks next:recorder ←[33mrecorder←[0m (to chat_manager): ←[32m***** Suggested function Call: write_settled_plan *****←[0m Arguments: { "the_plan": "1. Create a graphical user interface (GUI) for the analog clock.\n2. Implement a function to retrieve the current time.\n3. Implement a function to convert the current time into the corresponding positions of the clock hands.\n4. Update the GUI to display the clock hands at the correct positions based on the current time.\n5. Adjust the color of the hour hand to pink.\n6. Continuously update the clock display to show the current time in real-time." } ←[32m*******************************************************←[0m -------------------------------------------------------------------------------- Who speaks next:manager Provide feedback to chat_manager. Press enter to skip and use auto-reply, or type 'exit' to end the conversation: ←[31m >>>>>>>> NO HUMAN INPUT RECEIVED.←[0m ←[31m >>>>>>>> USING AUTO REPLY...←[0m ←[35m >>>>>>>> EXECUTING FUNCTION write_settled_plan...←[0m ←[33mmanager←[0m (to chat_manager): ←[32m***** Response from calling function "write_settled_plan" *****←[0m None ←[32m***************************************************************←[0m -------------------------------------------------------------------------------- Who speaks next:manager Provide feedback to chat_manager. Press enter to skip and use auto-reply, or type 'exit' to end the conversation: exit 

At this point the terminal should be released. The iteration phase can now begin.

Whether starting the iteration phase directly after planning or resuming it after stopping a previous run, the iteration phase runs the same.

Begin the iteration phase by calling the main script again: python IterativeCoding.py

The user can continually enter exit as the feedback to let the iterations run without additional input.

The user can provide feedback/direction on the process to either the programmer or the reviewer, although this functionality has not been thoroughly tested.

The iteration will begin with a chat with the programmer, passing in the Plan, and if not the first iteration, the last code iteration and the last review comments as well for context.

Replying exit to the programmer will result in a function call to format and write the programmers last message to a script file with incrementing version numbers.

After this, the reviewer will be presented with the Plan and the latest code and be asked to make comments/criticisms on the code direction. If it concludes another iteration is required, it will end with ITERATE. If it concludes testing is required, it will end with TEST.

Replying exit to the reviewer will end the current iteration. If n_code_iterations has not been exceeded, another iteration will begin by starting a chat with the programmer, passing in the Plan, the last code iteration, and the last code review comments as context.

The user is able to run any script iterations in the working_dir while the iterative process is running. Feedback from the code execution can be provided by the user to either the programmer or the reviewer to incorporate into the program.

Sometimes the reviewer will produce a 100+ point list of the same issue.

Due to above issue, reviewer may perpetually suggest to "iterate".

Make the planning phase not require a group chat - while demonstratitive in how a manual group chat can be made, it is not necessary for the flow to run as intended.

Add logic to create working directory if it doesn't exist. Tie in with logic to select which project to continue working on based on directory names.

Include automated testing and code execution during iterations - feed back error messages or Manager comments.

Write the latest review comments to a text file with similar versioning as the scripts - allow resumption with last comments brought in as well.