Topic starter
06/07/2026 9:35 am
TL;DR: An AI coding agent can stay accountable when every action is tied to the human who triggered it, using short-lived user-scoped OAuth grants instead of shared bot credentials, according to Descope. That breaks the assumption that agent access can be governed like static service accounts and pushes identity teams toward delegation-first design.
Editorial analysis by NHI Mgmt Group, based on content published by Descope: “How We Built Accountable Identity for Shuni, Our AI Coding Agent”.
Key questions
Q: What breaks when AI agents are connected through personal accounts or shared credentials?
A: Shared or personal credentials break accountability, lifecycle control, and revocation.
Q: Why do user-scoped OAuth grants improve accountability for AI agents?
A: They keep the human principal inside the delegation chain, so every action can be traced to the person who authorised it.
Q: When should security teams choose delegation over long-lived service accounts for agents?
A: Choose delegation when the agent acts on behalf of a person, the required permissions vary by request, or immediate offboarding matters.
Practitioner guidance
- Adopt user-scoped delegation for agent runs Tie each agent action to the human who triggered it and fetch downstream credentials only at request time.
- Remove shared bot credentials from agent workflows Do not let the agent hold a reusable bot account, cached PAT, or other standing credential that outlives the invocation.
- Separate authentication from authorization checks Verify who invoked the agent before deciding what the agent is allowed to do in GitHub, MCP tools, or other third-party systems.
Bottom line: This article shows that accountable AI coding agents depend on delegation that keeps the human principal visible at every step.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/07/2026 9:50 am
Delegation-first identity is the right baseline for AI coding agents: The article shows that the agent is not the principal, the human is. That distinction matters because accountability collapses when the system treats an agent as a standalone account instead of a delegated executor. The practical conclusion is that identity architecture must preserve the human principal through every downstream action.
A few things that frame the scale:
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How should IAM teams govern AI coding agents across GitHub, MCP tools, and other systems?
A: Govern them as delegated executors, not as standalone users. That means proving the human at invocation, issuing only the scopes needed for that run, logging both the grant and the action, and revoking the connection when access should end. The control objective is accountability across the entire delegation chain.
👉 Read our full editorial: Accountable identity for AI coding agents depends on user-scoped delegation