interaction
wrapper at the real request boundary. It can generate an Interaction ID when the application does not
supply one. SDK startup and ordinary model calls do not create logical requests automatically.
A Session is a conversation or coherent job that can contain several Interactions. Supply the
application’s actual Session ID. A User ID is an opaque application identifier within the selected Product.
Add meaning without changing ownership
Usecontext to contribute Session, Interaction, User or deployment labels to existing work. Use span
for an application operation that automatic capture cannot observe. Neither replaces an owning request
wrapper or proves that a proposed tool actually executed.
An asynchronous handoff is explicit: the application confirms accepted publication before a successor
continues the Interaction. Merely returning a handle, buffering work or ending a span does not prove
completion or transfer. The SDK does not implement an application job store.
Capture and delivery are separate
The SDK preserves native results, errors, consumed stream output and observed effects. A tool proposal is distinct from execution. Missing content, usage or a validation schema stays unavailable rather than being inferred from neighboring records.flush attempts to deliver finished telemetry. shutdown drains and closes resources owned by the SDK.
Check delivery and cleanup separately, and match the fresh execution in Impact to establish Product readback.
The SDK reports supplied deployment labels; the platform resolves canonical Product, Environment and
Version associations. Context attributes do not grant access to another Product or capability.
Add request and Session context with the JavaScript
or Python examples. For accepted queue work, use the
JavaScript handoff or
Python handoff APIs.