feat(web): show swarm agent status in chat#188
Merged
Conversation
Signed-off-by: Chengcheng Ding <billdin1999@gmail.com>
warren618
added a commit
that referenced
this pull request
Jun 8, 2026
Collaborator
|
Merged — really nice work. Bridging runtime events into the session SSE stream without changing the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
127.0.0.1to avoid Windows localhost resolving to::1while the API binds IPv4.Why
The terminal swarm dashboard already shows each agent's waiting/running/done/failed/blocked/retry state, but the web chat only showed the top-level
run_swarmtool as a long-running tool. This PR brings the same status visibility into the chat timeline and keeps the existing swarm page/API wire shape intact.Changes
SwarmTooland emitswarm.started/swarm.eventframes through session SSE without changing/swarm/runsor/swarm/runs/{id}/events.SwarmRunStatus/SwarmAgentStatusfrontend types, a swarm event reducer, and an inlineSwarmStatusCardin the chat timeline.run_swarmtool result for reconnect/history scenarios.http://127.0.0.1:8899.Test Plan
pytest --ignore=agent/tests/e2e_backtest --tb=short -q).venv\Scripts\python.exe -m pytest --ignore=agent/tests/e2e_backtest --ignore=agent/tests/test_e2e_harness_v2.py --tb=short -q: 3057 passed, 2 skipped; 6 failed and 9 errored due to local Windows-only environment issues outside this change: symlink privilege errors inagent/tests/factors/test_registry.py, Windows chmod mode assertions inagent/tests/test_oauth_token_cache.py, and cache-home path expectations inagent/tests/test_loader_retry_helpers.py..venv\Scripts\python.exe -m pytest agent/tests/test_swarm_status_hydration.py agent/tests/test_swarm_worker_report.py -q(32 passed)cd frontend && npm run test:run -- SwarmStatusCard(5 passed)cd frontend && npm run buildpassed.127.0.0.1.Checklist
src/agent/,src/session/,src/providers/) without prior discussion