• Working on main bot outside of greenfield refactor. Located reported bug where trying to “edit” a campaign using /campaign start caused an error. Now there is a /campaign edit button that allows you to easily edit existing campaign information. (7/14/25)
• Starting a greenfield refactor the bot in its entirety. I have MVP at this point, and need to clean up a number of files and code.
• Made progress on Vector Database. Agents are now able to use tools to query the VDB, but need to fine-tune the embedding processes.
• Patched the Discord update break using a pull request from Pycord. Temporary fix unfortunately (6/24/25)
• Discord made an update about a week ago. It appears that is causing the bot to not be able to connect to voice channels consistently. This is a widespread issue amongst other developers. If the bot doesn’t join, try again in an hour or so. (6/23/25)
• Working on switching the database over to a vector-based database. This should eventually allow for ‘@chronicler’ calls directly in Discord. (6/10/25)
• Server backups have been set up so we can avoid data wipes better in the future 6/7/25
• The server host wiped the bot’s database of previous session information including the backups. It is back up and running, but you will need to anticipate putting in your previously entered context information and campaign start, most likely. (6/6/26)
• The bot was letting a webhook time out during processing, which caused session notes to not post. I edited the logic so we don’t have the cool message editing, but now it should be much more stable.(5/25)
• Session recovery tool is working well. Have recovered several sessions already (5/25)
• Created session recovery tool to attempt to rescue some failed session notes. (5/25)
• Fixed bug where usernames with underscores caused the bot to crash. Also the bot should handle unconventional disconnects such as network errors or channel kicks more gracefully.
• Utilized chunked recording writing to disk periodically to overcome memory management. Also overhauled the transcript merger logic to include transcript clean up and priming for LLM analysis. (5/25)
• Encountered issue where session data is lost after /stop command is triggered. Working on more effective memory management. (5/25)
• Bot is back up as of 5/1. Rate limit handling and the dependency issues have been patched. But will need to work a more robust solution in the future.
• Bot is currently down 4/30/25. Fixing dependency issues. Should be back up within 24 hrs.
• Sent links to various sites and forums (4/25)
• Recently set up server support for beta testing (4/25)
• Addressed bug with /stop not being triggered appropriately (4/25)