A framework for autonomous agents who can work together to accomplish tasks.
You will need at least Node 10.
npm install
Rename the .env.template file at the root of the project to .env and add your secrets to it:
OPENAI_API_KEY=... # obtain from https://platform.openai.com/account/api-keys
# the following are needed for the agent to be able to search the web:
GOOGLE_SEARCH_ENGINE_ID=... # create a custom search engine at https://cse.google.com/cse/all
GOOGLE_API_KEY=... # obtain from https://console.cloud.google.com/apis/credentials
You'll also need to enable the Google Custom Search API for your Google Cloud account, e.g. https://console.cloud.google.com/apis/library/customsearch.googleapis.com
Start the program:
npm run start [# of agents] [gpt-3.5-turbo|gpt-4]
Interact with the agents through the console. Anything you type will be sent as a message to all agents currently.
After spinning up a new agent, you will often see them make some mistakes which generate errors:
- Trying to use an action before they've asked for
helpon it to know what its parameters are - Trying to just use a raw text response instead of a correctly-formatted action (or raw text wrapping a code block which contains a valid action)
- Trying to use a multi-line parameter value without wrapping it in the multiline delimiter (
% ff9d7713-0bb0-40d4-823c-5a66de48761b) This is a normal period of adjustment as they learn to operate themselves. They generally will learn from these mistakes and recover, althoughgpt-3.5-turboagents sometimes devolve into endless error loops and can't figure out what the problem is. It's highly advised never to leave an agent unattended, since such infinite loops can eat through your tokens quickly (especially if they're stuck on a high-token-count action such aswriteFile).
Each agent stores its state under the .store directory. Agent 1, for example, has
.store/1/memory
.store/1/goals
.store/1/notes
You can simply delete any of these things, or the whole agent folder (or the whole .store) to selectively wipe whatever state you want between runs. Otherwise, agents will pick up where you left off on restart.
A nice aspect of this is that when you want to debug a problem you ran into with a particular agent, you can delete the events in their memory subsequent to the point where the problem occurred, make changes to the code, and restart them to effectively replay that moment until you've fixed the bug. You can also ask an agent to implement a feature, and once they've done so you can restart, tell them that you've loaded the feature, and ask them to try it out.