Cairn
NousResearch/hermes-agent

Auto-launching Chrome for browser connect feature

Cluster 5507 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #5020 feat: /browser connect auto-launches Chrome with persistent Hermes profile · done elsewhere → 6b437f7, #6821, #5507
  • #8484 feat: /browser connect auto-launches Chrome with persistent profile · done elsewhere → 73f39a7, 6b437f7
Closed issues · 1
  • Closed#5507feat: /browser connect auto-launches Chrome with persistent profile
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/5507.json
cluster/5507.md