fix: stop killing goosed when a window closes

[DOsinga]

Summary

Closing a BrowserWindow killed its dedicated goosed process via goosedProcess.kill() in the mainWindow.on('closed') handler. This severed sessions for users who close one window while others are still open, causing the "session error" failures described in the issue.

The app.on('will-quit') handler already calls goosedResult.cleanup() for every spawned goosed process (with graceful SIGTERM + 5s SIGKILL fallback), so the per-window kill was redundant and harmful.

Changes

• Removed goosedProcess.kill() from the mainWindow.on('closed') handler in ui/desktop/src/main.ts
• Removed the now-unused process: goosedProcess destructuring from goosedResult

Testing

• pnpm lint passes clean
• All 347 desktop tests pass

Fixes #8711

[chatgpt-codex-connector]

💡 Codex Review

goose/ui/desktop/src/main.ts

Lines 1133 to 1135 in 756faf6

	mainWindow.on('closed', () => {
	windowMap.delete(windowId);

Clean up per-window goosed when chat window closes

Removing the goosedProcess.kill() path from the closed handler leaves each chat window's spawned backend alive until full app exit, but createChat() still starts a fresh backend for every new window. In environments where closing windows does not quit the app (e.g. macOS per window-all-closed logic in ui/desktop/src/main.ts), repeatedly closing/reopening chat windows accumulates orphaned goosed processes and listeners, which can degrade performance and eventually exhaust system resources.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".