⭐️Now supported GPT-4 Turbo⭐️
- There is a risk of inadvertently damaging the environment. Please execute primarily in a virtual environment such as Docker.
- The objective may not be achieved and it may continue to loop. The amount of API usage may increase in such cases, so please use responsibly.
- It is recommended to use GPT-4 Turbo or higher as it has been mainly verified with GPT-4 Turbo or higher. (If you are using GPT-4-8k, it is recommended to use v2 of the older BabyCommandAGI.)
BabyCommandAGI is designed to test what happens when you combine CLI and LLM, which are older computer interaction interfaces than GUI. Those who are not familiar with computers may not know, but CLI is an old computer interaction interface. Even now, many computer operations can be done through CLI (common Linux servers mainly use CLI). Imagine LLM and CLI having a conversation. It's exciting to think about what could happen. I hope you will all try it out and find new use cases.
This system is recommended to be run with an API of GPT-4 Turbo or higher.
BabyCommandAGI has the potential to be used in various cases. Please try using it to find use cases.
Below are some known useful use cases.
Create an app automatically just by providing feedback
- Reversi https://x.com/saten_work/status/1674855573412810753
- Snake Game https://x.com/saten_work/status/1723509089471492563
Automatic Environment Setup
- Install Flutter in a Linux container environment, create a Flutter app, launch a web server, and make it accessible from outside the container
This script works by executing the following continuous loop:
- Retrieve the first task from the task list.
- Determine if that task is a command task or a planning task.
- If it's a command task:
- Execute the command.
- If the command execution result has a Status Code of 0 and no response: Proceed to the next task.
- Otherwise: Analyze the result of the command execution with LLM, check if the objective is complete, and if not, create a new task list.
- If it's a planning task:
- Execute the plan with LLM.
- Analyze the executed plan with LLM and create a new task list.
Please follow the steps below:
git clone https://github.com/saten-private/BabyCommandAGI.git
- Enter the BabyCommandAGI directory with
- Create a file to insert environment variables with
cp .env.example .env.
- Set the OpenAI key to OPENAI_API_KEY.
- Set the name of the table where the task results are saved to the TABLE_NAME variable.
- (Optional) Set the objective of the task management system to the OBJECTIVE variable.
- (Optional) Set the system's first task to the INITIAL_TASK variable.
As a prerequisite, docker and docker-compose must be installed. Docker desktop is the simplest option https://www.docker.com/products/docker-desktop/
Please execute the following:
docker-compose up -d && docker attach babyagi
Note: Even if you exit with Ctrl+C, it will not stop unless you stop the container with Docker Desktop or similar. Please be careful.
Note: The agent might loop indefinitely if it cannot achieve its objective. Please be aware of the cost of OpenAI API usage.
The AI's generated items will be created in the
If you fail, you can resume from where you left off by running it again.
Changing the OBJECTIVE will clear the list of future tasks and OBJECTIVE feedback.
The following are saved up to the point where they were executed:
- Tasks executed up to a certain point are saved under the
- The last current directory is under the
- The dump of the last environment variables is under the
If you want to reset the environment, please delete the Docker container of BabyCommandAGI once and change the RESULTS_STORE_NAME in
(BabyCommandAGI executes various commands, so the environment may be broken)
Feedback to AI
By entering "f", you can give user feedback to the AI. This allows you to provide feedback to the AI on information that may not be clear from the CLI, like a GUI.
The logs during execution are saved under the
The log file name is determined by the OBJECTIVE identifier and the RESULTS_STORE_NAME.
BabyCommandAGI is still in the early stages, determining its direction and the steps to get there. Currently, BabyCommandAGI is aiming for simplicity. To maintain this simplicity, when submitting PRs, we kindly ask you to follow the guidelines below:
- Focus on small, modularized fixes rather than large-scale refactoring.
- When introducing new features, provide a detailed explanation of the corresponding specific use cases.
Note from @saten-private (May 21, 2023):
I am not used to contributing to open source. I work another job during the day and I don't know if I can check PRs and issues frequently. However, I cherish this idea and hope it will be useful for everyone. Please feel free to let me know if there's anything. I am looking forward to learning a lot from you all. I am a novice, I cannot speak English, and I barely know cultures outside of Japan. However, I cherish my ideas, and I hope they will be of use to many people. (I'm sure I will continue to come up with many boring ideas in the future)
✨ BabyCommandAGI's GitHub Sponsors ✨
The maintenance of this project is made possible thanks to all of the following sponsors. If you'd like to become a sponsor and have your avatar logo displayed below, please click here. 💖 You can become a sponsor for $5.