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.
Python: Fix ClaudeAgent reusing one SDK client across distinct fresh sessions #7404
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
base: main
Are you sure you want to change the base?
Python: Fix ClaudeAgent reusing one SDK client across distinct fresh sessions #7404
Changes from all commits
84451e43be125eFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How are sessions isolated when callers use the public
client=path? This branch ignoresresume_session_idand returns one stateful provider conversation for every session, so sequential tenants inherit context and concurrent runs can consume each other's responses. Could this path require a per-run client factory or otherwise prevent one injected conversation from crossing session boundaries?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could structured output remain scoped to the run rather than the agent? Run A stores its result in
self._structured_outputand then suspends here during disconnect, allowing run B to overwrite that field before A's finalizer reads it. On a shared hosted agent, A can therefore receive B's structured data across the session or tenant boundary.Uh oh!
There was an error while loading. Please reload this page.