Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

headsup: newest autogenstudio changes the db tables #37

Closed
scruffynerf opened this issue Jun 2, 2024 · 5 comments
Closed

headsup: newest autogenstudio changes the db tables #37

scruffynerf opened this issue Jun 2, 2024 · 5 comments

Comments

@scruffynerf
Copy link

scruffynerf commented Jun 2, 2024

@jgravelle in trying to track down a bug in AutogenStudio, I updated to the very latest code

https://pypi.org/project/autogenstudio/0.0.56rc12/
pip install autogenstudio==0.0.56rc12

ignore that current code claims to be 0.0.56, but is dated March 21st, the above is May30th

This stuff is all related to the new changes from this issue:
microsoft/autogen#2425
which went live 3 weeks ago, but the code hasn't been updated for pip/etc yet (due to the version issue above)

The database.sqlite tables changed, which confused the hell out of me, cause the old tables were there, but unused. (ie autogenstudio suddenly lost all of my data, but it was in db still)

Tables changed quite a bit, not merely the names (which went from multiples like skills to skill) so you'll have to change it all soonish.

Best answer: unless they write a conversion from old to new, export everything to json files and then blow your old db away (or move/rename it, if you don't live on the edge), and then update and run autogenstudio and let it make the new db with just the new tables. The effect of running the new code with a older DB is it makes a mess, and you end up both old and new tables.

@jgravelle
Copy link
Owner

jgravelle commented Jun 3, 2024 via email

@scruffynerf
Copy link
Author

Suggestion (I'm working thru the above needed changes and doing research into improvements):

I've been having issues with the autogen chatgroup not correctly handling the workflow of who should be next, etc.

Looking at https://microsoft.github.io/autogen/blog/2023/12/29/AgentDescriptions
The description field of the agent should be an objective ("this agent is", not "you are") short idea/summary the workflow mod can use to decide who to call on. It defaults to the system message, which is bad, as that's usually 'You are' style prompts.

Your autogroq moderator bot is similar.

@jgravelle
Copy link
Owner

jgravelle commented Jun 5, 2024

Looking at https://microsoft.github.io/autogen/blog/2023/12/29/AgentDescriptions The description field of the agent should be an objective ("this agent is", not "you are") ...

Good call. Done... -jjg

PS: https://discord.gg/Yp77yCU3

@scruffynerf
Copy link
Author

Good call. Done... -jjg

Um, not sure that's right (given the commit I just saw to the prompts)... will discuss. It's important to realize that "system prompt" is the prompt for the model "You are..." and prompts the LLM to do XYZ tasks, but description should be a simple summary like "This agent, XYZ doer, is responsible for X, Y, and Z tasks."

I'm trying to work on pieces so I can do separate PRs, so you making changes to main branch is a bit difficult. Hazards of one dev vs inviting others to help.

@jgravelle
Copy link
Owner

jgravelle commented Jun 5, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants