Bug report
gstack version: 1.34.1.0 (upgrade to 1.58.5.0 available but not yet applied)
OS: macOS Darwin 25.5.0 (macOS 26 / Sequoia)
Running inside: Claude Code VSCode extension
What happens
Using $B connect (headed mode / connect-chrome skill), gstack reports a successful connection, but the visible Chromium window disappears within seconds of opening. There is no time to interact with it.
Reproduction steps
- Run
$B connect inside Claude Code (VSCode extension).
- gstack prints "Connected to real Chrome", shows a PID, reports status healthy.
- A Chromium window appears briefly on screen.
- The window closes on its own within a few seconds (no user interaction).
- On the next
$B disconnect attempt, gstack reports "server was unresponsive — force cleaned".
What works
$B connect returns success (PID shown, status healthy).$B goto <url> navigates successfully (returns HTTP 200).$B focus returns "Browser window activated".- Everything works at the API level; only the visible window disappears.
Additional context: Chrome profile mismatch
Regular Google Chrome is installed with multiple profiles, but none of them is the Default profile. The existing profiles are numbered: Profile 4, 9, 10, 11, 12, 13.
gstack appears to look for Default/Cookies (or similar), which does not exist. This may be contributing to the crash or early exit if gstack cannot find or load the expected profile directory and then abandons the process silently.
Expected behavior
The Chromium window should stay open and remain interactive for the duration of the session, consistent with the behavior documented for headed / connect-chrome mode.
Attempted workarounds
Reproduced multiple times with identical results. The window never stays open long enough to interact with.
Happy to provide any additional diagnostic output (e.g., gstack server logs, Chromium crash logs from ~/Library/Logs/DiagnosticReports/) if that would help narrow this down.
Bug report
gstack version: 1.34.1.0 (upgrade to 1.58.5.0 available but not yet applied)
OS: macOS Darwin 25.5.0 (macOS 26 / Sequoia)
Running inside: Claude Code VSCode extension
What happens
Using
$B connect(headed mode /connect-chromeskill), gstack reports a successful connection, but the visible Chromium window disappears within seconds of opening. There is no time to interact with it.Reproduction steps
$B connectinside Claude Code (VSCode extension).$B disconnectattempt, gstack reports "server was unresponsive — force cleaned".What works
$B connectreturns success (PID shown, status healthy).$B goto <url>navigates successfully (returns HTTP 200).$B focusreturns "Browser window activated".Additional context: Chrome profile mismatch
Regular Google Chrome is installed with multiple profiles, but none of them is the
Defaultprofile. The existing profiles are numbered: Profile 4, 9, 10, 11, 12, 13.gstack appears to look for
Default/Cookies(or similar), which does not exist. This may be contributing to the crash or early exit if gstack cannot find or load the expected profile directory and then abandons the process silently.Expected behavior
The Chromium window should stay open and remain interactive for the duration of the session, consistent with the behavior documented for headed /
connect-chromemode.Attempted workarounds
Reproduced multiple times with identical results. The window never stays open long enough to interact with.
Happy to provide any additional diagnostic output (e.g., gstack server logs, Chromium crash logs from
~/Library/Logs/DiagnosticReports/) if that would help narrow this down.