Secrets Management for AI Agents on Small Teams
Your agent's tools need your production keys; the agent itself never should. The broker pattern, per-tool scoping, and what a five-person team can skip.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
All 154 posts, newest first. The latest are on page 1, and the topic directory groups them by subject.
Your agent's tools need your production keys; the agent itself never should. The broker pattern, per-tool scoping, and what a five-person team can skip.
Token-by-token LLM streaming in Phoenix LiveView without React: the 2026 async APIs, plus the production failure modes most tutorials skip.
One operating system runs a team whether the teammate is a person or an agent. My blueprint: trust, pods, outcomes over hours, managing agents like interns.
My team's $200 AI coding seats consume $1,800–$3,500 of API-priced tokens a month. The 10–17x arbitrage nobody prices in, and how to budget for it.
A scared employee hands over access to avoid a manager's wrath, the exact move social engineering exploits. Why psychological safety is a security control.
The cyber insurance application is a security audit in disguise. What underwriters check in 2026, the AI exclusions creeping in, and when coverage is real.
An MCP server lets Claude and other agents call your Phoenix app directly. How to ship one with Hermes: auth, transport, and safe tool boundaries.
I open-sourced the AI operating system I run daily: a git-versioned markdown vault, cross-repo wiring, and a nightly ingest loop. Fifteen minutes to set up.
Classic SRE postmortems can't explain agent incidents. The sections to add (decision-time context, autonomy rung, permissions delta), with a template.
Why auto-filling an enterprise security questionnaire backfires on an AI startup: the answers that kill deals, and the questions your SOC 2 won't cover.
Your accumulated agent memory is a bet on one vendor's format. Build a portable, git-versioned knowledge layer any agent can read instead.
The Claude Code plugins that earn a permanent slot in my stack, sorted by what they actually change: my process, my domain expertise, or just friction.