A Reddit thread asks how practitioners handle secrets and sensitive credentials when running agents. The poster notes ad hoc approaches like secrets.yaml files and SSO-based auth, and asks whether purpose-built, agent-friendly secrets management tools exist. The thread reflects a gap between agent adoption and established secrets-handling practice.
kdbx run is an open-source CLI tool that injects secrets from a KeePassXC vault into child processes without printing them, so AI agents with shell access can run commands needing credentials without exposing them in transcripts. It solves the problem of API keys leaking when agents read .env files, giving developers control over secret access.
kdbx run is an open-source CLI tool that injects secrets from a KeePassXC vault into child processes without printing them, so AI agents with shell access can run commands needing credentials without exposing them in transcripts. It solves the problem of API keys leaking when agents read .env files, giving developers control over secret access.
Developer asks how to manage API keys for AI agents calling multiple external services
Developer asks how to manage API keys for AI agents calling multiple external services
Argus is a security tool that monitors AI coding agent sessions to detect when secrets like API keys or passwords are exposed. It helps developers identify which sessions used a secret and how, enabling them to respond to potential leaks.
Argus is a security tool that monitors AI coding agent sessions to detect when secrets like API keys or passwords are exposed. It helps developers identify which sessions used a secret and how, enabling them to respond to potential leaks.
Developer launches MagicVault to hide credentials from AI agents while keeping them usable
Developer launches MagicVault to hide credentials from AI agents while keeping them usable
A Reddit discussion asks how teams constrain what coding agents can access and do inside projects. Agents often inherit broad permissions, including `.env` files with API keys and database credentials, and can install dependencies, call APIs, open PRs, or deploy. The poster asks whether teams use short-lived credentials, scoped service accounts, or proxies.
A Reddit discussion asks how teams constrain what coding agents can access and do inside projects. Agents often inherit broad permissions, including `.env` files with API keys and database credentials, and can install dependencies, call APIs, open PRs, or deploy. The poster asks whether teams use short-lived credentials, scoped service accounts, or proxies.