Browser Sessions

Session Model

• • Browser sessions are configured at project level and copied into workspace settings.
• • Each session entry has an optional name plus a URL prefix.
• • Sessions can use named port variables like `$FRONTEND_PORT` or `$API_PORT`.
• • Multiple session URLs can be attached to one workspace.

Launch Behavior

• • On workspace launch, Muxy ensures session URLs are open in Chrome.
• • Existing matching tabs are reused when possible.
• • Matching is based on URL prefix, not window title.
• • Matching browser tabs are attached to workspace window navigation.

Focus and Cleanup Rules

• • Focus actions target matching tabs using URL information.
• • If a tab matches multiple session URLs, it appears once in workspace navigation.
• • Browser cleanup closes matching tabs only.
• • Muxy does not close full Chrome windows during workspace cleanup.

Ordering and Multi-Workspace Safety

• • Browser rows are ordered by browser session definition order, then URL.
• • Workspace window listings rescan Chrome tabs to keep navigation current.
• • This avoids routing global next/previous shortcuts to the wrong workspace.

Example Browser Session Config

browser_sessions:
  - name: frontend
    url: http://localhost:$FRONTEND_PORT
  - name: admin
    url: http://localhost:$FRONTEND_PORT/admin
  - name: pr-review
    url: https://github.com/org/repo/pull/912
  - url: https://docs.example.com/runbook/checkout