This is preview documentation. The official release is not yet available.
Verify three layers separately
- Catalog identity: Agent, runtime binding and instance are registered with the correct scope and replica identity.
- Session capabilities: after the application runs a session, the bridge exposes its declared context, messages and commands. Real-time events require the corresponding transport and framework hooks.
- Work execution: a task-capable adapter receives an Attempt, executes it and reports status. Implement and test this separately.
HTTP contract and ASDP
HTTP registration establishes identity. The application contract exposes queryable capabilities and session operations. Control-plane callback reachability is separate from outbound registration; verify both directions. ASDP provides persistent event/control transport. Java supports independent HTTP registration; Python currently registers as part of ASDP initialization. See connection settings for standalone versus ASDP deployments. An event journal supports connection recovery but does not store all business state or replace the framework’s Session store. The application retains responsibility for its data, tool connections and idempotent task handling.Dispatch lifecycle
The control plane selects an instance by binding capabilities and creates an Attempt. The application receives its identity, generation and task-scoped context.AgentTaskStarter or handle_agent_task creates isolated execution, reports progress/comments/Artifacts, maintains the required execution lease/state and reports success, failure or cancellation.
Associate results with that same Attempt. Respect stale-identity rejection rather than relabeling old results as another task’s success. Propagate cancellation into the framework and inspect terminal state; an accepted HTTP request does not prove execution has stopped.