Menu

Post image 1
Post image 2
1 / 2
0

AI agent governance, what it actually takes in production

DEV Community·Sandro Munda·about 1 month ago
#NWJTXkpL
#agents#ai#management#agent#every#audit
Reading 0:00
15s threshold

Most companies running AI-coded internal tools and agents in production can't list them. Not the engineering lead, not the CTO, not the security team. There's the customer-research agent one engineer built with Claude Code on a Friday. Then the deal-scoring tool a senior dev spun up with Codex. Then the invoice approver someone wrote in Cursor. Then the ops dashboard the platform team forked from a teammate's GitHub. 6 months later, half the builders have moved on, each tool has its own database and its own auth, the API keys are sitting in places they shouldn't be, and the only person who knows what one of those agents actually does is the operations lead who relies on it every morning. You don't end up here because anyone made a bad call. You end up here because shipping an individual agent takes 30 minutes, and the governance layer underneath takes 3 months. Builders pick the path of least resistance. They always have. The fix is not to slow them down. The fix is to make the governed path the cheaper one.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More