cameleer/cameleer-server
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases Wiki Activity

[P1] Command response UX with error toast persistence #117

New Issue
Closed
opened 2026-04-02 18:49:07 +02:00 by claude · 1 comment
claude commented 2026-04-02 18:49:07 +02:00
Owner
Copy Link

Parent Epic

#100

Problem

Command toasts show "Config pushed" immediately without waiting for agent confirmation. Error toasts auto-dismiss, so users may miss failures.

Proposed Solution

  • Toast shows aggregated result after all agents respond: "Config pushed to 3/3 agents" or "2/3 agents responded — cameleer3-sample-xyz timed out"
  • Error/warning toasts require manual dismiss (no auto-disappear)
  • Success toasts can auto-dismiss as before

Dependencies

  • Depends on synchronous command dispatch (#116)

Acceptance Criteria

  • Success toast shows agent count: "Pushed to N/N agents"
  • Partial failure toast lists unresponsive/failing agents
  • Error toasts do not auto-dismiss — user must close manually
  • Success toasts auto-dismiss normally
## Parent Epic #100 ## Problem Command toasts show "Config pushed" immediately without waiting for agent confirmation. Error toasts auto-dismiss, so users may miss failures. ## Proposed Solution - Toast shows aggregated result after all agents respond: "Config pushed to 3/3 agents" or "2/3 agents responded — cameleer3-sample-xyz timed out" - Error/warning toasts require manual dismiss (no auto-disappear) - Success toasts can auto-dismiss as before ## Dependencies - Depends on synchronous command dispatch (#116) ## Acceptance Criteria - [ ] Success toast shows agent count: "Pushed to N/N agents" - [ ] Partial failure toast lists unresponsive/failing agents - [ ] Error toasts do not auto-dismiss — user must close manually - [ ] Success toasts auto-dismiss normally
claude commented 2026-04-02 19:08:31 +02:00
Author
Owner
Copy Link

Implemented in ca1d472.

Agent-count toasts:

  • Route commands show "X/Y agents responded" on success, or "N/M responded. Failed: agent-1, agent-2" as persistent warning on partial failure
  • Config push (taps, tracing, app config) shows push results from ConfigUpdateResponse.pushResult with the same pattern
  • 5 files updated: RouteControlBar, ExchangesPage, AppConfigPage, AppConfigDetailPage, AgentHealth

Persistent error toasts:

  • All variant: 'error' toasts across the entire UI now include duration: 86_400_000 (24h) so they require manual dismissal
  • 9 files updated: RouteControlBar, ExchangesPage, AppConfigPage, AppConfigDetailPage, AgentHealth, GroupsTab, RolesTab, UsersTab, OidcConfigPage
Implemented in `ca1d472`. **Agent-count toasts:** - Route commands show "X/Y agents responded" on success, or "N/M responded. Failed: agent-1, agent-2" as persistent warning on partial failure - Config push (taps, tracing, app config) shows push results from `ConfigUpdateResponse.pushResult` with the same pattern - 5 files updated: RouteControlBar, ExchangesPage, AppConfigPage, AppConfigDetailPage, AgentHealth **Persistent error toasts:** - All `variant: 'error'` toasts across the entire UI now include `duration: 86_400_000` (24h) so they require manual dismissal - 9 files updated: RouteControlBar, ExchangesPage, AppConfigPage, AppConfigDetailPage, AgentHealth, GroupsTab, RolesTab, UsersTab, OidcConfigPage
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
Accessibility (a11y) improvements
 bug
Something isn't working correctly
 cleanup
Code cleanup, dead code removal, refactoring
 epic
Epic: groups related issues
 feature
New functionality
 pmf
Product-market fit: critical for first market offer
 route-diagram
Route diagram page and execution overlay
 security
Authentication, authorization, RBAC
 ui
Frontend / React UI
 ux
UX/usability improvements
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-server#117
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?