Skip to content

[FEAT]: Agent max limits to prevent #3679

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

Open
timothycarambat opened this issue Apr 18, 2025 · 0 comments
Open

[FEAT]: Agent max limits to prevent #3679

timothycarambat opened this issue Apr 18, 2025 · 0 comments

Comments

@timothycarambat
Copy link
Member

Add a way for the user in some way to specify hard caps on tool calls or other possible "overthinking" during agent execution, so that runaway calls do not result in surprise costs for some models or even lower-end models that hyper-focus on tool calls.

Hey @timothycarambat, thanks for the reply and for digging into the issue! I tested the agent with Claude 3.5 Sonnet and Gemini 2.5 Flash, and both worked well, finishing tasks quickly without burning through tokens or getting stuck in loops.

It does seem like 3.7’s behavior is the main culprit. Your idea of a tool iteration cap sounds like a solid fix to stop this kind of overuse with models like 3.7. Maybe something like Gemini’s thinking budget could also work here?

Originally posted by @LinusAurel in #3675

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

No branches or pull requests

1 participant