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

[Feature Request] Add warning when token limit or context window reached in agent memory #1472

Open
1 of 2 tasks
Wendong-Fan opened this issue Jan 20, 2025 · 4 comments · May be fixed by #1591
Open
1 of 2 tasks

[Feature Request] Add warning when token limit or context window reached in agent memory #1472

Wendong-Fan opened this issue Jan 20, 2025 · 4 comments · May be fixed by #1591
Assignees
Labels
good first issue Good for newcomers P1 Task with middle level priority
Milestone

Comments

@Wendong-Fan
Copy link
Member

Wendong-Fan commented Jan 20, 2025

Required prerequisites

Motivation

For multi-round step, we may reach the token or context window(e.g., 50) limitation and remove some content in the message, but user may not know this behaviour, we need to add warning when token limit or context window reached in agent memory to make user know this

Solution

No response

Alternatives

No response

Additional context

No response

@Wendong-Fan Wendong-Fan added the enhancement New feature or request label Jan 20, 2025
@lightaime
Copy link
Member

What is the default 50?

@Wendong-Fan Wendong-Fan added good first issue Good for newcomers call for contribution P1 Task with middle level priority and removed enhancement New feature or request labels Jan 26, 2025
@Wendong-Fan Wendong-Fan added this to the Sprint 22 milestone Jan 26, 2025
@zoezyn
Copy link
Collaborator

zoezyn commented Feb 4, 2025

@Wendong-Fan Hi, I'd like to work on this issue. I didn't find where the default context window setting is (is it only 50)? Probably need some guidance though.

@Wendong-Fan
Copy link
Member Author

Hey @lightaime @zoezyn , apologies for the confusion. In CAMEL, we don't set a default value for message_window_size. The value 50 is just an example that the user could choose to set

@coolbeevip
Copy link
Collaborator

Is the handling strategy for exceeding limits configurable, such as printing warning logs or throwing exceptions? Because sometimes truncation is not the optimal strategy.

@zoezyn zoezyn linked a pull request Feb 12, 2025 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers P1 Task with middle level priority
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

4 participants