Unused Developer Tokens Expose Code to AI Agents
BlueFlag's survey-based report measures how permissions outlive their tasks as autonomous agents gain access to repositories.
Updated on Nov. 6, 2026 in Software

BlueFlag Security published The State of Developer Risk 2026, a report on how developer accounts, tokens and AI agents expose code repositories to access risk. The findings are survey-style measurements across organizations, not a shipped product, and describe current exposure rather than a new technology.
Why it matters
As coding assistants and autonomous agents write, review and merge code under developer or service identities, permissions that outlive their original purpose create a growing attack surface. The report suggests this exposure is already widespread in organizations using AI development tools.
BlueFlag's pooled dataset measures access rights rather than incidents, reporting that 84% of measured repository-access tokens allowed code changes and 47% had gone unused for more than 90 days without being revoked. The report's figures describe permission exposure at the level of identities and tokens, and the stub does not provide sample size or sampling method.
The players
BlueFlag Security
A security firm that publishes research on developer identity and repository access risk, and which authored The State of Developer Risk 2026.
The details
Coding assistants typically operate under a developer's own identity and inherit that developer's permissions, so anything the developer can reach, the tool can reach. Autonomous agents go further by running as separate identities that can write, review and merge code without a human approving each action. When those identities keep broad permissions long after a task ends, a single compromised or misbehaving agent can touch many repositories.
Timeline
November 6, 2026: Help Net Security published an article on the BlueFlag report.
The Tech Race
The report positions developer identity governance as a growing concern alongside the rapid adoption of AI coding tools across organizations. It documents where permission sprawl is already occurring rather than projecting a future threshold, so the race is between adoption of autonomous agents and the controls that govern them.
Developers and security teams whose organizations use AI coding assistants may find existing tokens and inherited permissions worth auditing against the report's findings. The stub does not state any product, pricing or timeline changes.
The takeaway
Organizations adopting autonomous coding agents face a permissions question that existing identity controls were not built for. Watch for follow-up measurements from BlueFlag or other security researchers that show whether token expiration and agent monitoring improve in future reporting cycles.
Further reading
Explore more on Software developments covering how these tools are built and secured.
Source note: This article includes information reported by Help Net Security.


