fix: allow agent host to define a custom host and port #452
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I was trying to run locally two instances of the Demo UI + Agent Host, and noticed that even when I defined a different env var "A2A_UI_PORT" to run the Demo UI in another port everything was working but the state was shared between the two UI instances, because they pointed to the same Host Agent (hardcoded to run in localhost:12000).
To solve this I propose this change in the Demo UI code, to allow to also run two instances of Agent Host, each per instance of Demo UI.
This follows the same logic that was implemented here:
A2A/demo/ui/main.py
Lines 155 to 160 in 35f51ce