Notifications
Clear all
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.
NHIMG editorial — based on content published by WorkOS: key takeaways from Boris Cherny on building Claude Code
By the numbers:
- Since adopting Claude Code internally, Anthropic has doubled its Engineering org, and per-engineer productivity (merges/engineer/day) has increased 200%.
Questions worth separating out
Q: How should teams govern AI-assisted development workflows that use coding agents?
A: Treat them as identity-governed execution paths, not just productivity tools.
Q: Why do AI coding agents increase the blast radius of developer access?
A: Because a single developer account can now trigger fast, iterative actions across repositories, build systems, and internal data sources.
Q: What do identity teams get wrong about AI coding tools and autonomy?
A: They often treat any AI-powered workflow as autonomous when many are still bounded automation.
Practitioner guidance
- Map AI-assisted development workflows as identity-bearing systems Document which prompts, tools, repositories, build systems, and data sources are touched when engineers use AI coding agents.
- Review developer entitlements for workflow blast radius Limit the permissions that AI-assisted workflows can reach through a developer account, especially access to source control, CI/CD, secrets, and production-adjacent data.
- Separate human review from machine generation in change management Require teams to distinguish between the person accountable for the change and the system that generated or transformed the code.
What's in the full article
WorkOS's full article covers the interview context and broader commentary this post intentionally leaves for the source:
- Direct quotes from Boris Cherny on how Claude Code changed engineering roles and workflows
- More detail on the productivity and ramp-up figures described in the interview
- The discussion of generalist teams, taste, and values in the context of AI-assisted software development
- The original Acquired Unplugged interview framing and commentary from WorkOS
👉 Read WorkOS’s summary of Boris Cherny’s Claude Code interview →
AI coding agents and engineering control: what teams need to know?
Explore further
22/06/2026 11:10 am
Agent-assisted engineering is becoming an identity governance problem before it becomes an autonomy problem. The article describes engineers moving from direct coding to writing loops that delegate work to Claude Code, which means the real control surface is now the workflow around the model. That changes access, approval, and accountability even if the system is not fully autonomous. Practitioners should treat these environments as governed NHI-enabled execution paths.
A few things that frame the scale:
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface, according to the Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which means most teams cannot confidently map the identities supporting AI-assisted workflows.
A question worth separating out:
Q: How should organisations adjust access reviews for AI-assisted engineering?
A: Access reviews should look beyond the human role title and inspect the effective permissions behind the workflow. That includes secrets, build permissions, data access, and any service accounts used by the tooling. Reviews should answer whether the combined human-plus-tool path still matches the task being performed.
👉 Read our full editorial: AI coding agents are changing engineering roles and identity control
