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

Fix documentation: Correct default value of planner_interval from 4 to 1 #594

Conversation

pppp606
Copy link
Contributor

@pppp606 pppp606 commented Feb 7, 2025

The documentation incorrectly states that the default value of planner_interval is 4, whereas the actual default value in the code is 1.

Issue

In the documentation:

planner_interval: Number of steps between planning phases. Defaults to 4.

However, in the Agent class constructor, the default value is explicitly set to 1:

planner_interval: int = 1, # Run planner every N steps

Fix

Updated the documentation to reflect the correct default value (1) to match the actual implementation.

@pppp606 pppp606 marked this pull request as ready for review February 7, 2025 06:39
@@ -48,7 +48,6 @@ agent = Agent(
- For GPT-4o, image processing costs approximately 800-1000 tokens (~$0.002 USD) per image (but this depends on the defined screen size)
- `save_conversation_path`: Path to save the complete conversation history. Useful for debugging.
- `system_prompt_class`: Custom system prompt class. See <a href="/customize/system-prompt">System Prompt</a> for customization options.
-
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed an unnecessary - to improve readability. This is unrelated to the default value fix.

@MagMueller MagMueller merged commit e283cd8 into browser-use:main Feb 12, 2025
2 checks passed
AryamanParida pushed a commit to AryamanParida/browser-use that referenced this pull request Mar 7, 2025
…oc_planner_interval_defaults

Fix documentation: Correct default value of planner_interval from 4 to 1
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

Successfully merging this pull request may close these issues.

2 participants