-
Notifications
You must be signed in to change notification settings - Fork 832
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
Genesis stuck in ToolCreator loop #150
Comments
I've had this issue a couple times even with more basic agents. I think it might be related to OpenAI API having issues from time to time, but I can add a response validator to prevent this in genesis |
This issue is stale because it has been open for 30 days with no activity. Please upgrade to the latest version and test it again. |
This issue was closed because it has been inactive for 14 days since being marked as stale. If the issue still persists, please reopen. |
Came back and retried new scenario with latest build (as of 10/01/2025) and it still got stuck in the tool creation loop. |
Have just had a loop upon loop with user input experience.
Genesis creating a tool before experiencing no change to its approach and repeating the same over and over infinitum. It never actually works out its issue and just keeps saying it has tried a different approach (which is always the same exact approach that doesn't function).
`
Please make sure to now test this tool if possible.
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
🐨 ToolCreator 🛠️ Executing Function
Function(arguments='{"agent_name":"BrandStrategist","chain_of_thought":"To re-test the InterviewTool, I will provide mock inputs for the client's name and interview questions. The tool should simulate asking the
questions and storing the responses, using a local dictionary to simulate the shared_state for testing purposes.","tool_name":"InterviewTool","arguments":"{"client_name":"John
Doe","interview_questions":["What is your unique value proposition?","What are your personal brand aspirations?"]}"}', name='TestTool', output=None)
What is your unique value proposition? I provide value
What are your personal brand aspirations? To have a working example
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
TestTool ⚙️ Function Output
Error: Error running tool InterviewTool: 'NoneType' object has no attribute 'set'
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
🐨 ToolCreator 🗣️ @AgentCreator
It seems the issue persists. The error indicates that the shared_state is still not being handled correctly. To resolve this, I'll ensure that the shared_state is properly managed within the tool's context.
I'll update the InterviewTool to ensure it uses a local dictionary to simulate the shared_state for testing purposes.
• Conduct in-depth client interviews to gather information about their unique value propositions and personal brand aspirations.
• Store and organize the interview data for further analysis.
• Use a local dictionary to simulate the shared_state for testing purposes.
Let's proceed with modifying the tool.
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
🐨 ToolCreator 🛠️ Executing Function
Function(arguments='{"agent_name":"BrandStrategist","tool_name":"InterviewTool","requirements":"This tool will conduct in-depth client interviews to gather information about their unique value propositions and
personal brand aspirations. It should be able to store and organize the interview data for further analysis. Use a local dictionary to simulate the shared_state for testing purposes.","mode":"modify"}',
name='CreateTool', output=None)
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
CreateTool ⚙️ Function Output
Certainly! Below is the revised InterviewTool class that meets the specified requirements and uses a local dictionary to simulate the shared_state for testing purposes:
from agency_swarm.tools import BaseTool
from pydantic import Field
from typing import List, Dict
class InterviewTool(BaseTool):
"""
This tool will conduct in-depth client interviews to gather information about their unique value propositions and personal brand aspirations.
It should be able to store and organize the interview data for further analysis.
"""
Example usage:
tool = InterviewTool(client_name="John Doe", interview_questions=["What is your unique value proposition?", "What are your personal brand aspirations?"])
tool.run()
In this version, the shared_state is simulated using a local dictionary within the InterviewTool class. This allows for testing the tool's functionality without relying on an external shared state mechanism. The
interview data is stored in this local dictionary for further analysis.
Please make sure to now test this tool if possible.
`
The text was updated successfully, but these errors were encountered: