andrewmusselman opened a new issue, #24:
URL: https://github.com/apache/tooling-gofannon/issues/24

   ### Summary
   A user running multiple agents has no cross-agent view of what's running now 
or what just finished. To check on something started elsewhere, they have to 
navigate to that specific agent's runs page.
    
   ### Details
   **Problem:**
   The operational question "is my first run still going? Should I kill it 
before starting a second?" requires either tailing docker logs or having both 
agents' tabs open simultaneously.
    
   ### Proposed solution
   New module on HomePage above or beside the agents list. Lists the current 
user's runs across all agents:
    
   - Status chip (running / success / error / stopped)
   - Agent name
   - Started-at timestamp
   - Run ID
   Click → `/agent/:agentId/runs/:runId`. Auto-refresh by polling `GET /runs` 
every few seconds. Live status updates by re-fetching, not subscribing to SSE 
per row (overkill for a status overview).
    
   ### Acceptance Criteria
   - [ ] Fixed: `RunningJobsModule` component added to HomePage
   - [ ] Fixed: Polls `GET /runs` every ~5 seconds while mounted
   - [ ] Fixed: Status chips reflect run states (running, success, error, 
stopped)
   - [ ] Fixed: Click navigates to deep link `/agent/:agentId/runs/:runId`
   - [ ] Test added: Module shows runs across multiple agents
   - [ ] Test added: Module updates within polling interval when a run completes
   ### References
   - File: `webapp/packages/webui/src/pages/HomePage.jsx`
   - Tracker: FIXES.md item #5
   ### Priority
   **Medium** - Depends on ISSUE-003 (run registry) and ISSUE-005 (deep links). 
Modest frontend work once those land.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to