I've got Hermes driving a Chrome profile over CDP for a handful of self-hosted tasks. All ~48 web logins sit in that single profile, and the agent just clicks through native autofill so passwords never enter the model's context. That part's working, but it's fragile in two ways.
Chrome's saved-password fill is identifier-independent: on an origin with multiple accounts it fills the most recently used one, and I can't programmatically summon the dropdown to pick a specific account. React forms whose inputs sit outside a
<form> element get nothing from autofill at all. I've kept API keys and tokens in Windows Credential Manager and only web credentials in Chrome, no Bitwarden or KeePass.On the navigation side, CDP Chrome is primary with Camofox, nodriver, TRAWL, and curlcffi as fallbacks. CDP Chrome clears Cloudflare Turnstile where Camofox fails server-side. curlcffi's TLS impersonation runs a couple Chrome generations behind the real browser. IP reputation looks like the first gate and I have no residential egress yet.
Two questions:
1. Should a single profile hold ~48 logins, or do you split credentials per task? How do you deal with autofill grabbing the wrong account?
2. Given IP reputation gates first, what's the cheapest residential egress worth setting up? Is a CDP-first order right, or would you reorder the fallbacks?
https://redd.it/1x8yujv
@r_SelfHosted
