Document getCurrentAgent() context propagation - sync for agents#712 #26921
+40
−1
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.
Summary
Documents that
getCurrentAgent()properly propagates connection context through async operations, including tool execution functions. This sync reflects the bug fix from cloudflare/agents#712.Changes
/agents/concepts/agent-class.mdx: Enhanced Context Management section to clarify thatgetCurrentAgent()works inside nested async functionsgetCurrentAgent()inside AI SDK tool execution to access the connection that triggered the chatRelated PR
Technical Context
The original PR fixed a bug where
getCurrentAgent()was not returning the connection context inside tool execution functions called fromonChatMessage. The fix wrapsonChatMessageexecution inagentContext.run()to properly propagate the connection context to nested async functions.This documentation update ensures users understand that
getCurrentAgent()reliably works in tool execution and other nested async contexts.🤖 Generated with Claude Code