Tag
A practitioner reflects on how the 'blast radius' of an internal AI agent — its over-broad database roles, trusted internal API tokens, and environment-stored secrets — matters more than defending against prompt injection itself, and asks the community how they scope agent tool access and secrets without crippling usefulness.
Once 是一个用 Go 编写的 CLI 工具，通过后台守护进程缓存命令输出，避免重复执行昂贵或需要生物识别验证的命令（如 1Password 的 op read），支持 TTL、租户键和目录无关缓存等选项。
OpenHands Enterprise adds new features for organizational management of coding agents, including secrets sharing, usage tracking, OAuth for MCP servers, and automation oversight.
Kody is a software platform that enables AI agents to share memory, secrets, and packages for durable automation and triggering without repeated inference.
The author, building a company run by AI agents, details the security challenges of managing 285 credentials and seeks advice on configuring secret access for agents in a self-hosted Phase instance.
Kent C. Dodds announces that Kody now supports custom secret providers, enabling integration with password managers like 1Password for secure secrets management in AI agents.
SecretSpec has released dotenv-ng, a modern Rust fork of dotenvy, to fix parsing issues with secrets like bcrypt fragments and address maintenance gaps in .env file handling.
A discussion on how developers handle credentials for coding agents, exploring an approach where agents use APIs without receiving raw secrets, with injection at request time and destination restrictions. The author is building this as part of Stashbase and invites others to share their practices.
The author expresses concern about granting coding agents shell access, noting they can read sensitive files like .env and credentials, and asks the community for practical secret-handling patterns before letting agents touch real repositories.
A technical analysis of why .env files became a de facto configuration standard despite lacking schema, spec, and security semantics, and why teams should replace them with more durable declarations.
An exploration of whether AI agents should ever directly see API credentials, inspired by the open-source OneCLI project which uses a gateway to swap placeholders for real keys, sparking a discussion on trust and security in AI tooling.
A developer built Hamza, a tool that inspects outbound requests from AI coding agents like Claude Code and Codex to mask secrets and PII before they leave your machine.
Infisical is an open-source security platform that centralizes secrets, certificates, and privileged access management, with special support for AI agents. The review rates it 4.7/5 stars, highlighting its developer-friendly design and unified platform.
This article argues that secrets should not be stored in configuration files, using an audit of NixOS modules to show that a quarter of them require workarounds to separate secrets from config. It advocates for dedicated runtime channels for secrets.
Infisical is an open-source secret management platform that centralizes API keys, scans for leaks, and protects AI agents, addressing common credential exposure issues like the Toyota data breach.
A short announcement about an article discussing the principle of keeping secrets away from LLMs to prevent them from being leaked by AI agents.
A blog post explaining how to combine SOPS with Age for encrypting secrets outside the cluster and Bitnami Sealed Secrets for in-cluster decryption, enabling a GitOps workflow for Kubernetes.
A thread sharing a structured install order for agentic projects: using direnv with a secrets manager for credential safety, litellm or portkey as a model proxy for cost and fallback management, uv+git commits on passing evals for reproducibility, and mitmproxy for full observability of LLM calls. Highlights common failure modes and security gaps.
A tutorial explaining secrets management options for NixOS, comparing tools like sops-nix, agenix, and ragenix, with practical examples of using sops-nix for encrypted secrets management.
Blog post proposes offloading API-key injection to an internal HTTP proxy so apps and agents never see secrets, easing rotation and reducing exfiltration risk.