I counted our credentials before hiring my first agent. 285 of them, 5 with a known owner.
Summary
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.
Similar Articles
Should every agent get its own identity and credentials?
A discussion on whether AI agents should each receive their own identity and short-lived, scoped credentials instead of sharing a single API key, including how MCP servers fit into this model. The author invites real-world setups and lessons on when per-agent identities become overkill.
We built a 54-agent ecosystem where some of the agents are persistent fictional characters — the hardest part has been controlling what they’re allowed to learn
The author describes building a 54-agent ecosystem for a project called Trading Hearts, focusing on challenges in controlling agent learning and maintaining persistent identities and rules.
How are you handling agent identity and auth without handing over primary accounts?
A developer promotes Decoy (decoys.me), a product that gives AI agents scoped, revocable task-specific identities instead of direct access to primary accounts, featuring client-side encryption and a user-owned knowledge graph for cross-agent context sharing.
20 agents in, we finally admitted we had no idea how many agents existed in our own company
A company shares their struggle with tracking AI agents across their organization, leading to the development of an agent registry that addresses discoverability, access control, logs, and usage metrics, eventually adopting TrueFoundry's solution.
Most multi-agent setups are a room full of people wearing headphones. Here's what I changed.
The author shares insights from building a multi-agent infrastructure, identifying 'identity drift' as a key challenge solved by implementing strict agent passports and file-access controls.