Improve agent loop tracking and make concurrent limit configurable #6944
+0
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves how we track and manage concurrent agent loops:
max_concurrent_conversations
to AppConfig (default: 3)start_time
tracking to Session classPreviously, when the limit of concurrent agent loops was reached, the system would try to guess which was the oldest by reversing the list of session IDs. This was inaccurate. Now we track the actual start time of each session and use that to accurately determine which session is the oldest when we need to close one.
The limit of 3 concurrent conversations has also been moved from a hardcoded constant to a configurable value in AppConfig.
To run this PR locally, use the following command: