Repository navigation
agents: forward flowStartedAt and firstAttemptAt through ConnectorStepContext - #1799
Merged
Merged
Conversation
…nnectorStepContext Released connectors read call.context.flowStartedAt and firstAttemptAt. The tool Step's ConnectorStepContext did not forward them, so such an operation failed with a TypeError inside an agent tool Step.
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
ConnectorStepContext(TypeScript) now exposesflowStartedAtandfirstAttemptAtfrom the tool Step's context. The conformance test that pins its member list includes them, and a new test runs a connector operation that reads both throughConnectorToolSource.Why
Released connectors read these Context members inside a Call: the Gmail connector's send builds its Message-ID from
call.context.runIdandcall.context.flowStartedAt, and six operations readcall.context.firstAttemptAt. Inside an agent tool Step both wereundefined, so a Gmail send always failed (flowStartedAt.getTime()threw, reported asVALIDATION: message could not be encoded). An audit of everycall.context.*read in the connectors library found no other missing member. The Python side follows in a separate PR.Testing
npm run typecheck(the package's lint gate).connector-tool-source.integration.test: 26/26, including the new test.connector-tools.integration.testagainst a real Dex engine (dexcli 1.47.3): 34/34.