Recover the shared Linux browser

Scope

Shared Shipyard Chromium, display, noVNC and Playwright MCP. Coordinate with the human and other agents before restarting.

Diagnose

Run ~/dev-environment/scripts/browser-session.sh status on Shipyard. Check local listeners with ss -ltn for 5901, 6080, 8931 and 9222; they should bind to loopback. Do not publish browser tab listings or traces that may expose private URLs/data.

If Chromium and viewer respond but Orca shows a connection failure, reload the existing viewer tab and confirm Browsing through shipyard. If using Mac Chrome, check the SSH forward and Mac port ownership. If only MCP fails, use http://localhost:8931/mcp exactly and reconnect the agent client.

Repair

If stopped, browser-session.sh start uses the persistent profile. If a component has failed, inspect its private log and, after coordination, stop/start the supervisor. Do not delete cookies/profile data or start a second browser using the same profile.

For sandbox failures after an upgrade, compare the pinned executable in the session and AppArmor scripts. The owner may need sudo bash ~/dev-environment/scripts/browser-sandbox.sh after the correct browser is installed. Never disable Chromium sandboxing or system-wide namespace restrictions.

Verify and escalate

Confirm the viewer and MCP reach the same existing session, then perform a benign navigation. Saved password login was retained in earlier tests, but consent/session expiry can still require the user. Do not attempt to bypass authentication. Video/audio/GPU behavior has not been validated.