-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat(agent): support multiple tool groups #1556
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
Conversation
Summary: Supported by llamastack/llama-stack#1556 Test Plan: Tested in llamastack/llama-stack#1556
payload=AgentTurnResponseStepStartPayload( | ||
step_type=StepType.tool_execution.value, | ||
step_id=step_id, | ||
input_messages = input_messages + [message] |
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.
all of this code inline in this method is becoming quite hard to scan through. I think we need another file where we write some simple functions (all of these inside the agent_instance
object is also a FAIL mode that I had long before initiated ever since our first agent impl lol)
llama_stack/providers/inline/agents/meta_reference/agent_instance.py
Outdated
Show resolved
Hide resolved
}, | ||
) as span: | ||
tool_execution_start_time = datetime.now().astimezone().isoformat() | ||
tool_result = await self.execute_tool_call_maybe( |
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.
can this fail or throw?
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.
Yes, maybe we can have a catch all and return some generic error message.
llama_stack/providers/inline/agents/meta_reference/agent_instance.py
Outdated
Show resolved
Hide resolved
Overall, I feel like there are quite a few changes to the code here and substantial ones. If we are convinced all the changed code paths are exercised by our integration tests then that's OK otherwise adding either an integration test or some kind of smaller scoped unit tests would be advisable. |
Summary: Test Plan: Summary: Test Plan: Summary: Test Plan:
Summary: Test Plan: Summary: Test Plan:
# Summary: Includes fixes to get test_agents working with openAI model, e.g. tool parsing and message conversion # Test Plan: ``` LLAMA_STACK_CONFIG=dev pytest -s -v tests/integration/agents/test_agents.py --safety-shield meta-llama/Llama-Guard-3-8B --text-model openai/gpt-4o-mini ``` --- [//]: # (BEGIN SAPLING FOOTER) Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/meta-llama/llama-stack/pull/1550). * #1556 * __->__ #1550
Summary:
closes #1488
Test Plan:
added new integration test
Stack created with Sapling. Best reviewed with ReviewStack.