Skip to content

fix(web): chat and agents show Not running with a Restart action after a hub restart (CL-8507) - #903

Merged
TheGreatAxios merged 1 commit into
mainfrom
cl-8507-agent-restart
Sep 18, 2026
Merged

TheGreatAxios merged 1 commit into
mainfrom
cl-8507-agent-restart

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Contributor

Summary

  • listChatAgents now reports each agent's latestStatus (the newest deployment's status for its asset), alongside the existing liveAddress.
  • Chat page (new-chat and thread) and /agents distinguish a terminal deployment (released/failed/destroy_failed/stopped/never deployed) from a starting one (pending/recovering): terminal now shows "Not running" plus a Restart button (useMutation calling redeployRoomAgent, invalidating the chat-agents query and, on the chat page, the thread query too). While restarting, the UI shows "Starting…"; the composer stays disabled until the agent is live.
  • agentRosterStatus gains a third state (not-running); the roster's status pill and body copy follow.
  • Kept the existing 3s refetch while an agent isn't live, and added the same polling to /agents so a restart or a released→deployed transition shows up without a reload.

Closes CL-8490.

Test plan

  • bunx tsc -p apps/web --noEmit
  • bun run lint
  • bun run fmt
  • cd apps/web && bun run build
  • cd apps/web && bun test ./src

@linear-code

linear-code Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

CL-8507

CL-8490

@TheGreatAxios
TheGreatAxios merged commit ecf224d into main Sep 18, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant