-
Notifications
You must be signed in to change notification settings - Fork 230
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
[Docs] Improved Conversation Patterns documentation #1005
Merged
Merged
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
d6ea677
Fix swarm use case image links
marklysze 22e9107
Restructure and sequential chat page added
marklysze 075d086
secrets
marklysze 0e0baaa
Nested chat text and example
marklysze edb18c0
Secrets args revert
marklysze c5a6fba
revert secrets baseline
marklysze df89f65
Swarm orchestration documentation includes simple group chat example
marklysze 1627b03
resolved conflicts
davorrunje 4e3aae3
.secrets.baseline updated
davorrunje bea2eda
wip
davorrunje 19d5994
Merge branch 'main' into ag2docsconvpatterns
davorrunje 861e816
GCM ValueError test
marklysze a0ec44d
Merge remote-tracking branch 'refs/remotes/origin/ag2docsconvpatterns…
marklysze 990334b
Merge branch 'main' into ag2docsconvpatterns
marklysze 96add84
Formatting and secrets
marklysze da2edca
Missed test update, test_lmm.py
marklysze 69c245b
mock_credentials.llm_config
marklysze c3ca166
Move Reference Agents to User Guide, fix tests
marklysze cec1bc1
test_chats remove mock credentials
marklysze 01e89fa
Reference Agent links, added api_type openai to llm configs in tests …
marklysze 907d198
Revert api_type openai on a test due to llm validation bug.
marklysze File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a test to pass the codecov CI.
Is
llm_config
always required when this method_create_internal_agents
is called?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ultimately, yes it requires a configuration as it creates an agent internally (so there's no mechanism here for a developer to configure that agent to respond any other way).
If the GroupChatManager doesn't have
llm_config
set or the GroupChat doesn't haveselect_speaker_auto_llm_config
set, it won't be able to use an LLM.What was happening was that when no LLM config was set, this internal agent was returning a blank reply and that was resulting in it just returning the next agent in the list. This was silent for the user so it looked like it was determining the next agent with an LLM but wasn't.