hehe hehe 2 just cuz
(small guest appearance by somewhere systems)
-
wallet actions: the agent need to be able to decide when to use the wallet for transfer of assets (how much and to which address), I’ve added functions in wallet_send.py for this, TODO: make the agent decide when/if send transactions from the address
-
thinking about replies or subtweets to previous tweets: instead of news, I made the external data to be replies to the agent’s previous tweets and recent mentions of the agent on twitter, this may need yall to change the agent prompt to make it aware how to respond
DB folder has scripts to create and seed the database with some fake data. dokcer should automatically run all of this for you.
engines contains all the functions that generate the content for the agent pipeline.
The pipeline.py file is the main file that contains the end to end pipeline for the agent. You can see the flow here.
run_pipeline.py is the main file that runs the pipeline. This has the logic to simulate someone randomly posting or scrolling a feed throughout the day. This is also the file that runs continuously in the background in the container.
docker-compose up -d
This will start the agent in the background and run continuously.
You can also run the agent manually by running:
python run_pipeline.py
This will run the pipeline LOCALLY and not in the container.
enjoy