Hi, I’m Gerard, CTO at Latitude. We encountered this while adding first-class telemetry support for Cloudflare Think and Codemode in latitude-dev/latitude-llm#3956.
Problem
Connector callbacks receive the Codemode executionId, but there is no public hook exposing that ID when an execution starts. This prevents telemetry integrations from associating the active parent trace context with an execution before sandbox callbacks cross the async boundary.
Request
Add an execution/pass start hook, such as onPassStart(executionId), called after the execution ID is created and before sandbox code runs. It should pair with onPassEnd and support concurrent executions and resumed passes.
This would let integrations store execution-scoped context by ID and safely recover it from connector callbacks.
Hi, I’m Gerard, CTO at Latitude. We encountered this while adding first-class telemetry support for Cloudflare Think and Codemode in latitude-dev/latitude-llm#3956.
Problem
Connector callbacks receive the Codemode
executionId, but there is no public hook exposing that ID when an execution starts. This prevents telemetry integrations from associating the active parent trace context with an execution before sandbox callbacks cross the async boundary.Request
Add an execution/pass start hook, such as
onPassStart(executionId), called after the execution ID is created and before sandbox code runs. It should pair withonPassEndand support concurrent executions and resumed passes.This would let integrations store execution-scoped context by ID and safely recover it from connector callbacks.