From acc37e156546bd27cbc2cc982cab6d99bd258918 Mon Sep 17 00:00:00 2001 From: Zongren Liu Date: Tue, 2 Jun 2026 09:18:46 -0400 Subject: [PATCH] fix(aws-transform-agent-toolkit): correct a2aSupported example and UpdateAgent claim MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two issues in agent-registration.md were causing users to register orchestrators that the AWS Transform webapp couldn't chat with: 1. The "Complete agentCard Example" set `a2aSupported: false`, which the chat backend interprets as non-routable. Users (or LLMs) following this as a template ended up with chat-broken agents. Flipped to `true` to match every other example in the file. 2. A note claimed `jobOrchestratorMetadata` is "fully updatable post-registration" via `UpdateAgent`. The registry's UpdateAgent API actually only accepts customerConfiguredAgentDependencies, marketplaceMetadata, and deprecated — it does NOT accept jobOrchestratorMetadata. Replaced with an accurate warning that matches troubleshooting.md. --- aws-transform-agent-toolkit/steering/agent-registration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aws-transform-agent-toolkit/steering/agent-registration.md b/aws-transform-agent-toolkit/steering/agent-registration.md index 104a6d3..8c39e2f 100644 --- a/aws-transform-agent-toolkit/steering/agent-registration.md +++ b/aws-transform-agent-toolkit/steering/agent-registration.md @@ -212,7 +212,7 @@ These MUST be kept in sync with the `discover_subagents()` tool in `tools/orches | `chatAgentIdentifier` | string | Yes | Unique identifier for chat routing (use agent name) | | `a2aSupported` | boolean | Yes | Whether agent supports Agent-to-Agent protocol | -> **Note:** If the agent is already registered (`ConflictException`), use `UpdateAgent` to modify `jobOrchestratorMetadata` (including `chatUILabel`) — it is fully updatable post-registration. +> **Warning:** `jobOrchestratorMetadata` (`chatUILabel`, `chatAgentIdentifier`, `a2aSupported`) is set at `RegisterAgent` time and **cannot be updated** afterward — `UpdateAgent` only accepts `customerConfiguredAgentDependencies`, `marketplaceMetadata`, and `deprecated`. To fix a wrong value (e.g. `a2aSupported: false`), you must re-register under a different agent name. Choose carefully. ### Complete Examples @@ -552,7 +552,7 @@ The minimum structure that passes boto3 and server-side validation (works for bo "tags": ["analysis", "assessment"], "capabilities": { "restartable": true, - "a2aSupported": false, + "a2aSupported": true, "legacyDashboard": false, "legacyTaskLink": false, "webAppV2": true,