Close the local browser when used as fallback for remote

[markijbema]

When we configure kilo to use the remote browser, but none is available, it falls back to a local browser. Administrate this in isUsingRemoteBrowser and use this to determine to close which browser when closing the browser.

Related GitHub Issue

Closes: #4822

Description

Instead of looking at what browser should have been used, look at what browser is actually used and close that

Test Procedure

Enable remote browser connection (checkbox)
(but do not actually start one)

Open the activity monitor (on macosx, or the equivalent on your OS)

Ask a simple browser request, for instance "give me the most important headline from cnn.com"

You can see chrome helpers starting
And when Roo says it closes the browser you can see them stopping/disappearing

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

N/A

Documentation Updates

Additional Notes

Get in Touch

---

Important

Fixes browser closing logic in BrowserSession by tracking actual browser usage with isUsingRemoteBrowser.

• Behavior:
  • Introduces isUsingRemoteBrowser in BrowserSession to track if a remote browser is used.
  • Updates closeBrowser() to use isUsingRemoteBrowser to determine whether to disconnect or close the browser.
• Misc:
  • Updates launchLocalBrowser() and connectWithChromeHostUrl() to set isUsingRemoteBrowser appropriately.

^{This description was created by for fd8cec8b4c786e7d2aabf043f36fafa05e82ad47. You can customize this summary. It will automatically update as commits are pushed.}

[daniel-lxs]

Hey @markijbema, thank you for contributing to fix the issue.

I left a couple of suggestions that might be worth taking a look at, let me know what you think!

[daniel-lxs]

Looks good!

Thank you @markijbema!