dsh-accounts

When an AI agent inside DSH must log into websites or run local CLIs that depend on API keys, any credential that enters the model context is exposed to leakage risk. dsh-accounts builds a secure bridge between the credentials store and tool invocations: values live only in the plugin process memory, while the model and conversation can never see more than account names and metadata.

Three capabilities cover the main use cases. account_fill injects stored credentials directly into the built-in browser to auto-complete login forms, guarded by domain whitelists, CAPTCHA detection, and a post-fill read-blocking window that prevents the model from reading back form contents. credential_run passes API keys or tokens to child processes as environment variables and scrubs all secrets from stdout and stderr before returning. A single-file web admin page, mirrored by a native settings panel, lets the user create, edit, and delete accounts with TOTP support, custom fields, and env-key whitelisting, eliminating the need to hand-edit YAML. Zero runtime dependencies; only Node built-in modules are used.

Built for DSH users whose agents must log into multiple sites or invoke key-gated local CLIs; teams whose security policy demands that secret values never leave process memory; and operators who prefer a visual interface for credential management over directly editing credential files.