# NousResearch/hermes-agent · Fix PID requirement for driver-owned browser launch

## Open now

- 1 issue, 0 PRs open on GitHub.
- #93763: \[Bug\]: cua_browser_prepare incorrectly requires a PID for driver-owned isolated profiles

A bug was reported and fixes were made to remove the incorrect requirement for a PID when preparing driver-owned isolated browser profiles in computer use. The changes allow browser launch without a PID in that context.

## TL;DR

- 3 member(s): 1 open issue(s), 0 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.

## Open related issues

- #93763: \[Bug\]: cua_browser_prepare incorrectly requires a PID for driver-owned isolated profiles

## Prior & competing PRs

- **#93783: fix(computer_use): stop requiring a pid for driver-owned browser prepares**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `f780cb36d8`
- **#93831: fix(computer-use): allow pidless isolated browser launch**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`

## Fix status

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