A password store your agents can use but not read. Your browser encrypts every login with keys that live only in the open tab; the database keeps ciphertext, public keys and metadata.
A root-owned broker on your host fills a login or a one-time code into the pane's browser, and the agent gets back a status and an audit id, not the value. After a fill the page stays protected until it is gone: the agent can click, type and press keys but cannot read the field. One switch turns agent access on or off, and logins import from a Chrome password export.
It also keeps server passwords and API keys: an agent asks for one by its id, and the value is written straight into the file that needs it, not into the agent's context. Logins that agents create, and passwords that reach them in a mail, are saved to the Vault rather than to memory or notes.