Topic starter
22/06/2026 10:19 am
TL;DR: Claude Code has moved from writing 10% to over 90% of code for its team, while new-hire ramp-up fell from weeks to about two days, according to WorkOS’s summary of Boris Cherny’s Acquired Unplugged interview. The shift matters because engineering work is moving from direct authoring to orchestrating agent loops, which changes how identity, access, and accountability need to be governed.
Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “Key takeaways from Boris Cherny on building Claude Code”.
By the numbers:
- Per-engineer productivity increased 200% after adopting Claude Code internally.
Key questions
Q: What breaks when AI coding agents inherit a developer’s identity?
A: The main failure is that the agent is no longer operating as a separate principal.
Q: Why do AI agents change infrastructure identity governance?
A: AI agents change the model because they can take actions, call tools, and operate without a human approving each step.
Q: How should security teams set access boundaries for AI agents?
A: Security teams should define agent boundaries around data sources, tools, and allowed actions before any production rollout.
Practitioner guidance
- Define agent-specific access boundaries Separate the permissions needed for prompt execution, repository access, build actions, and release-related tooling so the agent does not inherit a human developer’s full operating range.
- Record prompt-to-change accountability Capture which human requested the work, which agent executed it, which tools were used, and what review occurred before merge or deployment.
- Review identity assumptions in onboarding and offboarding Ensure AI coding agents have explicit lifecycle ownership, disabled credentials, and revocation paths rather than being left as invisible standing collaborators.
Bottom line: AI coding agents shift engineering from direct authoring to orchestrated execution, which changes where identity controls need to sit.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
22/06/2026 11:10 am
AI coding agents turn development access into a delegated execution model: The important governance shift is not that developers are writing faster, but that an identity can now request, modify, and assemble work through a repeated agent loop. That breaks the old assumption that access is exercised directly and visibly by a human in a single interaction. Practitioners should now treat the coding environment as a governed delegation chain, not a person-only workstation.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What should teams do when code is generated by an AI agent rather than a person?
A: Require traceability from prompt to merge. Teams should know who initiated the task, what context the agent used, which tools it touched, and what human review happened before the change was accepted. That evidence becomes essential when the same workflow can generate large amounts of code quickly and repeatedly.
👉 Read our full editorial: AI coding agents are changing engineering roles and identity control