-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
max_iterations Not Limiting Agent Execution Steps #6857
Comments
Just want to check that you are running in development mode right? |
The version I am using is |
I'm working on a fix! @neubig can track my progress at all-hands.dev |
The max_iterations setting in the config file was not being enforced when running in headless mode. This was because we were only checking the iteration limit in the _step method, but not in the _handle_observation method. This meant that when an agent action triggered a command execution, the command output observation would trigger another step even if we had hit the iteration limit. Changes: - Modified _handle_observation to check iteration limit before processing observations - Added test case test_iteration_limit_in_headless_mode_with_agent_steps that verifies this behavior Fixes #6857
Ah I see. In evals, we don't actually read the
As you can see, we create an instance with those values, instead of loading it from the file. This fools me all the time... 😅 Cc: @neubig |
Thanks @enyst . I think long story short you'll need to pass in the configuration through command line arguments, not config.toml. So add This is yet another instance of #3220 , which I'd really like to fix but it's a big effort so we haven't gotten to it. Anyway, I'll close this for now since there should be a clear work-around. |
Description
I attempted to limit the agent’s execution steps by setting max_iterations = 1 in the config file. However, despite this setting, the agent continues executing up to step 6.
Config
Log
The text was updated successfully, but these errors were encountered: