You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Required extensions aren't enforced, so ExtensionSupportRequiredError is never raised #1467
The spec says that when an extension is marked required: true in the Agent Card and the client doesn't declare it, the agent MUST return ExtensionSupportRequiredError (§3.3.4, and again in §4.6.3). a2a-python defines the error and maps it on every transport, but nothing in src/ raises it, so a request without a required extension goes through.
The requested extensions are already parsed into the call context, so the check would fit next to validate_input_modes (#1269) as an opt-in flag on DefaultRequestHandler, off by default so existing servers don't change. a2a-go already does this check.
I'd like to take this if that shape works for you.
Hi @ConnorMoss02 , thanks for raising this.
Your are correct DefaultRequestHandlerV2._setup_active_task does not validate whether required extensions from agent_card are included in call_context.requested_extensions. As a result, ExtensionSupportRequiredError is never triggered when a client omits a required extension.
We would welcome a pull request introducing this check alongside unit tests.
Activity
rohityan commentedon Nov 15, 2026
Hi @ConnorMoss02 , thanks for raising this.
Your are correct
DefaultRequestHandlerV2._setup_active_taskdoes not validate whether required extensions fromagent_cardare included incall_context.requested_extensions. As a result,ExtensionSupportRequiredErroris never triggered when a client omits a required extension.We would welcome a pull request introducing this check alongside unit tests.
ConnorMoss02 commentedon Nov 16, 2026
Thanks @rohityan, opened #1482 with the check and tests.