Repository navigation
vscode: migrate Team view from sidebar to Codev panel tab #814
Description
Activity
Held pending #1049, and to be rescoped rather than built as written (architect ruling, recorded on #813, #814 and #815 together).
This issue proposes a dedicated sibling tab in the Codev panel container. #1049 (contextual bottom panel) is built on the opposite premise: that one tab per feature makes the panel grow faster than anyone wants to navigate it, so a single
Codevtab morphs to pair with the active surface, and cross-cutting roll-ups — pending gates, blocked builders, queued review comments, recently-closed audit — live inside its Attention mode rather than as siblings. Shipping these three as separate tabs and then shipping #1049 would produce exactly the tab sprawl #1049 exists to prevent.The resolution is not to close these. #1049 is explicitly an umbrella that ships the panel surface, the mode resolver, the switcher and placeholder bodies, while the actual per-mode content is owned by participating-feature issues and lands in their own PRs against the render targets the umbrella exposes. Recently Closed, Team and Status are three of those participating features. So each of these issues survives as "render this view's content into its panel mode", and loses only the "as its own tab" framing.
Sequencing: hold until #1049's surface lands, then rescope against the render targets it publishes. They are not blocked on anything else — #812 shipped the container.
Related finding worth folding into #1049's plan phase rather than tracking separately: the
codev.placeholdersignpost these issues were meant to displace can never render at all.apps/vscode/src/extension.ts:555unconditionally setscodev.panelContainerEmptyto false, so the view is always hidden — while its body text still advertises #813/#814/#815 to a user who by construction cannot see it. #1049 repurposes that placeholder slot, so the fix rides it by construction.Verified against the current tree before ruling: all three views are still sidebar-only today, and the container from #812 is in place. Triage by the vscode architect; conflict analysis and ruling by main as #1049's owner.
- added a commit that references this issue
on Aug 24, 2026
Problem
The Team view (
packages/vscode/src/views/team.ts) lives in the Codev sidebar today as a vertical list of team members. The sidebar's narrow column wastes the horizontal room that a wider team-roster layout would use better, and Team is a low-frequency reference surface (compared to Builders / Backlog / PRs) so the bottom panel is a more appropriate dock.Proposed behavior
Migrate the existing
codev.teamview from thecodev(sidebar) container to the newcodevPanel(panel) container introduced in #812. No data, rendering, or interaction changes in v1 — same TreeDataProvider, same row shape, same context menu actions, samecodev.refreshTeamview-title action.Implementation
packages/vscode/package.json, move thecodev.teamview entry fromcontributes.views.codevtocontributes.views.codevPanel.codev.refreshTeamaction inview/titleis keyed by the view id (view == codev.team) — nowhen-clause change needed.Acceptance criteria
codev.teamregistered underviewsContainers.panel.codevPanel, not underactivitybar.codev.codev.refreshTeamview-title action still fires correctly.Depends on
Out of scope