Part of #1
Question
Drop the Browser entry from the actions array in apps/web/src/components/RightPanelTabs.tsx (~line 100), so it no longer appears in the "Open a surface" grid.
Scope is the card only. The + dropdown (RightPanelTabs.tsx:449), the six preview.* keybindings (packages/contracts/src/keybindings.ts:59-64), addBrowserSurface.ts, and the preview surface kind all stay. Rationale: this keeps divergence from pingdotgg/t3code near zero, and Browser costs nothing at runtime on web.
Explicitly not doing the general "hide unavailable cards" refactor. Showing a disabled card with a tooltip is intentional — it tells the user the feature exists and why they can't use it. Browser is a one-off removal, not a policy change.
Resolved when the card is gone from the grid, rightPanelStore.test.ts and any RightPanelTabs tests still pass, and nothing else about Browser has moved.
Part of #1
Question
Drop the Browser entry from the
actionsarray inapps/web/src/components/RightPanelTabs.tsx(~line 100), so it no longer appears in the "Open a surface" grid.Scope is the card only. The
+dropdown (RightPanelTabs.tsx:449), the sixpreview.*keybindings (packages/contracts/src/keybindings.ts:59-64),addBrowserSurface.ts, and thepreviewsurface kind all stay. Rationale: this keeps divergence frompingdotgg/t3codenear zero, and Browser costs nothing at runtime on web.Explicitly not doing the general "hide unavailable cards" refactor. Showing a disabled card with a tooltip is intentional — it tells the user the feature exists and why they can't use it. Browser is a one-off removal, not a policy change.
Resolved when the card is gone from the grid,
rightPanelStore.test.tsand anyRightPanelTabstests still pass, and nothing else about Browser has moved.