Refactored HistoryManagement a little and attempts to fix function calling setting carrying over previous value despite a new tool is set and thus deletes the guild_id column altogether which should not retain the previous value, this is the most complex issue i've encountered but most likely this is due to initialization step is called twice, pls review.
This one is harder to debug, so many regressions. This is a "for now" solution
Use YAML to register tools and models
Summarize: send the summary into file when the embed character limit reaches to 4096 characters
Refactored
HistoryManagementa little and attempts to fix function calling setting carrying over previous value despite a new tool is set and thus deletes theguild_idcolumn altogether which should not retain the previous value, this is the most complex issue i've encountered but most likely this is due to initialization step is called twice, pls review. This one is harder to debug, so many regressions. This is a "for now" solutionUse YAML to register tools and models
Summarize: send the summary into file when the embed character limit reaches to 4096 characters
Probably other things