Cairn

Fix relative/missing AGENT_BROWSER_PROFILE path handling

NousResearch/hermes-agent · cluster 132755 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These issues and PRs address a bug where AGENT_BROWSER_PROFILE is not correctly looked up or set on the host browser launch path, risking automation running against the user's real Chrome profile instead of an isolated one.

Open issues1

  • Issue#132755Host browser path never sets AGENT_BROWSER_PROFILE → automation drives the user's real Chrome profile

Open PRs2

  • PR#132764fix(browser): pin an isolated AGENT_BROWSER_PROFILE on the host launch path
  • PR#132769fix(browser): resolve a relative AGENT_BROWSER_PROFILE before it reaches the browser

1 PR closed without merging

From the close comments: closed without comment 1

  • #132768 fix(browser): resolve a relative AGENT_BROWSER_PROFILE before it reaches the browser · closed without comment
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.50: 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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/132755.json
cluster/132755.md