A2A agent testing in the browser
Use a browser test page to load an agent card, send messages and inspect A2A task and streaming responses.
What it is
Inside A2A Test is a browser page for checking an agent that supports the Agent-to-Agent protocol, or A2A. You can load the agent's card, send test messages and inspect its responses. Streamed messages can show response text, task status and activity as they arrive.
Who uses it and why
Developers use the page to check agent discovery, follow-up context and streamed or non-streamed behaviour. It is a testing interface; messages go to the selected agent and can trigger that agent's configured actions.
Where to find it
Open the standalone Inside A2A Test page supplied by Powerfront for your environment. It has no Settings menu entry.
The left panel contains connection fields, Agent Card, Last Request and Last Response. The conversation panel contains the message box and Send.
How it works
- Enter the complete agent address in A2A endpoint. The initial address is a prefix, so add the specific agent before testing.
- Enter Bearer token, optional only when the selected target requires it. The page sends it to that target.
- Select Load to retrieve Agent Card and determine whether the agent advertises streaming.
- Leave Send mode on Auto, stream when supported, or select the explicit streamed or non-streamed mode.
- Enter a message and select Send. Enter sends the message; Shift+Enter adds a line break.
The page shows the request body in Last Request and the latest response or error in Last Response. Streaming can display generated text, task status and an expandable Activity log. Non-streamed responses display returned task history.
Keep Context ID unchanged for follow-up messages. Select New to generate a fresh context. Select Clear Chat to clear the displayed conversation without changing its context.
List Tasks retrieves up to 20 tasks from the selected agent and displays the response in Last Response.
Configure it
Connection choices are saved in the current browser. The page restores the agent address, bearer token, context and send mode when opened again. Loading a card saves the address and token; sending a message also saves the context and mode.
Load the card after choosing an agent so automatic mode can use its streaming capability. On a fresh page, automatic mode uses a non-streamed request until a loaded card reports streaming support.
For an INSIDE agent, ask an operator with the Settings or Developer role to check the associated feature in Settings › AI › Features and confirm that it is active, enabled and available over A2A. Use the complete address for that agent.
Fields
| Field | Where | Required | What it is for |
|---|---|---|---|
| A2A endpoint | Inside A2A Test | Yes | Selects the agent to test. Enter the complete agent address before loading its card or sending a message. |
| Send mode | Inside A2A Test | No | Chooses automatic streaming when supported, an explicit streamed request or an explicit non-streamed request. The initial selection is Auto, stream when supported. |
| Bearer token, optional | Inside A2A Test | No | Sends the entered bearer token to the selected target when its authentication requires one. |
| Context ID | Inside A2A Test | No | Identifies the conversation context for follow-up messages. The page supplies an ID if none is saved; New creates another. |
Limits and good to know
- The page stores entered bearer tokens in browser storage. To remove a saved token, empty Bearer token, optional and select Load or send a test message again. You can also clear the page's browser site data.
- Clear Chat and New do not remove saved credentials or delete server-side tasks.
- List Tasks has no next-page control and does not filter by the displayed Context ID.
- The page has no task-cancellation or stream-resume control.
- Testing another origin depends on that target permitting browser requests from this page.
- Stream activity depends on the updates the selected agent sends. A stream ending alone is not proof that the underlying task completed successfully; inspect the task status.
Depends on and works with
View all connections as a list
This feature uses
- Autopilot connections through A2ARelated
Use the browser tester to check discovery, messages and tasks on an INSIDE A2A endpoint.
Used by
- Autopilot connections through A2ARelated
Use the A2A test page to check agent discovery and message delivery.
FAQ and troubleshooting
Why does automatic mode send a non-streamed message?
Select Load first. Automatic mode streams only when the loaded agent card advertises streaming support.
Why can the agent remember earlier messages after Clear Chat?
Clear Chat only clears the display. Select New to use a fresh conversation context.
Why does my token appear again after reopening the page?
The page saves it in browser storage. Empty the token field and select Load, or clear this page's browser site data.
Why does Load fail?
Check the full agent address, any required authentication and browser-origin restrictions. For an INSIDE agent, also check that its AI feature is active, enabled and available over A2A.
Where are the rest of the tasks?
List Tasks requests up to 20 tasks and has no paging control. Use the supported agent integration tools when you need further task access.