# NousResearch/hermes-agent · Auto-launching Chrome for browser connect feature

## Open now

- Nothing open on GitHub.

These issues and PRs concern a feature that auto-launches Chrome with a persistent profile when using /browser connect, along with related fixes for WSL path translation, port 9222 availability timing, and CDP port conflicts.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #5507: feat: /browser connect auto-launches Chrome with persistent profile

## Prior & competing PRs

- **#8484: feat: /browser connect auto-launches Chrome with persistent profile**. closed without merge · fix tier `suggested`
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `73f39a77614e1f72782f152803c547d168ee4420`, `6b437f7934e568b587f57c4731a6e93668f27343`
- **#5020: feat: /browser connect auto-launches Chrome with persistent Hermes profile**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `6b437f7934e568b587f57c4731a6e93668f27343`, `#6821`, `#5507`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`