AGiXT is a dynamic AI Agent Automation Platform that seamlessly orchestrates instruction management and complex task execution across diverse AI providers. Combining adaptive memory, smart features, and a versatile plugin system, AGiXT delivers efficient and comprehensive AI solutions.
Major changes are coming with this update to how the back end works.
Implemented MagicalAuth to add an easy magic link login with multi-factor authentication if the environment variable AUTH_PROVIDER is set to magicalauth. This will allow you to have a multi-user AGiXT instance.
File based mode has been removed and is now only used for database imports upon initial launch of AGiXT. It was getting to be too much to try to support the file mode and its limitations, which is why I built the database mode. (These were the files in the fb folder)
Database mode uses Postgres or SQLite which can be defined in your .env file using the environment variables DATABASE_TYPE, DATABASE_NAME, DATABASE_USER, DATABASE_PASSWORD, DATABASE_HOST, and DATABASE_PORT. These all have defaults set and the docker-compose will launch a postgres database with the back end to use if nothing is filled in. I would at minimum recommend setting the DATABASE_PASSWORD in your .env file.
User schema in the database was changed. If you were previously using the database mode, you may need to modify the database schema manually or wipe your data folder to start a fresh database.
No errors from tests, must be fine¯\_(ツ)_/¯
Merging to main to be tested before official v1.6.0 release.
v1.6.0
Major changes are coming with this update to how the back end works.
AUTH_PROVIDER
is set tomagicalauth
. This will allow you to have a multi-user AGiXT instance.fb
folder).env
file using the environment variablesDATABASE_TYPE
,DATABASE_NAME
,DATABASE_USER
,DATABASE_PASSWORD
,DATABASE_HOST
, andDATABASE_PORT
. These all have defaults set and thedocker-compose
will launch a postgres database with the back end to use if nothing is filled in. I would at minimum recommend setting theDATABASE_PASSWORD
in your.env
file.User
schema in the database was changed. If you were previously using the database mode, you may need to modify the database schema manually or wipe yourdata
folder to start a fresh database.must be fine¯\_(ツ)_/¯