[Juliusolsson05]

Problem

The Selected projects scope in Switch Agents (bulk provider switch) and Close Old Agents grouped agents by working directory, keyed by the full path and labelled by the folder name. An agent in .worktrees/grok-package-wiring therefore showed up as a project called "grok-package-wiring", and a project tab with agents in several worktrees was shredded into one entry per directory. There was no way to say "every agent in this project" in one click, which is the whole point of the bulk switch when a provider's window is exhausted.

This was never a product decision. Both modals were written in June, before Grid Dispatch rows had project bindings, when the tab title was the only project label and was not unique.

Implemented behavior

• Both modals list projects the way the Dispatch index does: one entry per project tab, labelled with the tab letter and title (A · agent-code, E · agent-code), in tab order.
• Each entry shows the distinct working directories it contains as its secondary line, so worktrees stay visible as directories inside the project rather than as projects.
• Membership is by tab: selecting a project selects its worktree agents too. Close Old Agents keeps its matching/total count per tab.
• The agent rows' secondary line uses the same letter vocabulary (E · agent-code · /path) instead of tab 5.
• The project filter matches the label, the title and the directory names, so typing a worktree name still finds the project that holds it.

Design decisions

• One shared derivation (features/workspace/lib/projectScope.ts) owns grouping, labelling, filtering and membership for both modals, replacing two copy-pasted ProjectRow implementations. Labels come from the same tabIndexLabel the Dispatch row filter uses, so no third vocabulary is introduced.
• Ordering follows tab order rather than the previous count-first sort, because the list is meant to read like the Dispatch index.

Linked issues

Fixes #908

Tests and verification

• projectScope.test.ts (new): two agents in one tab across different worktrees produce one entry with both directories; same-titled tabs get distinct letters and keep tab order regardless of counts; matching counts only the eligible rows; the filter finds a project by its worktree name; membership filters by tab.
• Existing CloseOldAgentsModal.rows, BulkProviderSwitchModal.policy and closedModalDerivations renderer suites pass unchanged.
• tsc -b clean on both projects under Node 24; npm run test:contract satisfied.

Known limitations

• Not exercised in the running app; verified from source and tests.

🤖 Generated with Claude Code

https://claude.ai/code/session_016vtjk6o4nukQp7Vfbt5TDc

[Juliusolsson05]

Review pass (one orchestrated Claude Code reviewer, read-only, from the fix worktree): APPROVE WITH COMMENTS, no blocking findings. It verified selection consistency in both modals, the per-kill revalidation in Close Old Agents, the Dispatch label vocabulary, the sort-change consumers, and ran tsc -b, the unit and renderer suites and the test contract.

Its six non-blocking comments are all taken in the follow-up commit: stale cwd parameter name in the bulk toggle; N selected now counts only tabs that still exist; redundant title clause dropped from the filter; cwdBasename imported from its owner instead of through the provider registry; the ordering test now has a later tab with the most agents so it cannot pass on a tie; and a new renderer test (BulkProviderSwitchModal.scope.renderer.test.tsx) drives "Selected projects" through the real modal: two entries named A · agent-code and B · startup, ticking the tab brings its detached worktree agent into the preview.