Repository navigation
feat(tasks): multi-host board with 'All hosts' default and host filter - #15
HoangNguyen0403 wants to merge 11 commits into
Conversation
e7e6ab6 to
8aebbd4
Compare
|
@HoangNguyen0403 can you fix conflicts ? |
|
Thanks for the multi-host work and the test coverage. This branch currently conflicts with main, and #35 also implements a multi-host board. We need to select one approach before merging either change. For the selected approach, please verify host-specific action routing and identity handling, including agents and workspaces with the same IDs on different hosts, remote read failures, and disconnect/reconnect behavior. The final conflict-resolved revision will also need the required checks and two-host client validation. |
…lity check on remote tasks
…availability gating
…esolutions The merged handle now forwards main's refreshUnreads to every host's store. Keep the sidebar's showEmpty, the filter badge comment, the render tests' sessionStorage reset and the multi-host mock's store fallback that the merge resolutions carried.
Host joins FILTER_GROUP_ORDER first, so the sidebar's tabs, the filter bar and the sheet read Host, Agent, Labels, Project, Workspace. The tab layout tests and the filter bar's word order follow it.
…orkspaces apart - Selection, card lookups and reveal carry the card's host, so two hosts that know the same agent id select and open their own card. - Parent resolution takes the host, and the merged handle routes it to that daemon's store instead of the first store that knows the id. - Read, unread, archive and unarchive are daemon-bound RPCs: a remote card now says to open it on its host rather than hitting the local daemon with a colliding id. Permission answers, details reads, open and the opened mark use the card's own client. - Workspace and project filter values carry their host, so one host's workspace does not filter another's, and the projects of two hosts stay apart in the filter menus. - Two-host tests: colliding agent and workspace ids, parent routing, disconnect/reconnect (subscriptions released), plus selection identity.
8aebbd4 to
0b36bb8
Compare
|
Rebased onto
Host identity and action routing (the review question)Verified and fixed where the old merge crossed hosts:
Validation run
Open point: if read/archive on a remote card should be done from the board rather than opening its tab, that needs an SDK path that targets another daemon (today's read/archive RPCs are bound to the current daemon). Tell me if that is required for this PR or acceptable as the current hint. |
Resolve conflict and added test to covered |
Summary
This PR introduces multi-host support to better-paseo's Tasks board:
Unified Multi-Host Board by Default:
useHosts()andgetPaseoClient()).ready: trueimmediately for the local host while remote hosts stream in their initial snapshots without blocking on latency.First-Class Host Filters across All Surfaces:
Host ▾menu button with connection status indicators and an "All hosts" default toggle.[Server]/ Host) alongside Agent, Project, Workspace, and Labels with live task counters per machine.hostIdsunder parameterh(?h=srv_1,srv_2), defaulting to all hosts.Card Fields Setting & Live Settings Preview:
hostas a configurable card field in Cards settings (Fields), enabled by default in Standard and Full density presets.migrateCardHost) ensures existing user configs seamlessly derive their host visibility without flipping density to "Custom".Remote Action Routing & Permissions:
• <Host>badge in the card meta row.respondToPermission) on remote tasks routes directly to the remote daemon viagetPaseoClient(card.hostId). Local availability checks are cleanly bypassed for remote hosts to prevent falseagent_missing/"Task no longer exists"rejections.{ serverId: card.hostId, agentId: card.id }tonavigation.openAgent, cleanly switching Paseo to that host.Why this approach over daemon relays (PR #9)?
PR #9 attempted backend daemon-to-daemon connections, which stalled due to remote credential/relay token resolution. This implementation uses the app client-side SDK (
useHosts(),getPaseoClient(),navigation.openAgent({ serverId, agentId })), which the Paseo app already authenticates and maintains persistently. Zero daemon changes or relay tokens required.Test Plan
npm run typecheckpasses with 0 errors (tsc --noEmit).vitest run test/unit/tasks-multi-host.test.ts(7/7 passed).vitest runpasses across all 266 files (6,387 tests passed).