DevOps
Who Changed the AI Agent's Rules? Measuring How AI Coding Agents Escalate Authority in CI/CD Pipelines
arXiv cs.SE0 views
arXiv:2611.23251v1 Announce Type: new Abstract: AI coding agents can modify CI/CD control-plane structures, including workflows and permission settings, thereby extending their authority beyond routine code changes. Because such modifications can affect an entire development pipeline, this study examines the trade-off between execution cost and governance risk in agentic CI/CD. We introduce a joint penalty model, P(M), that combines these two dimensions and evaluate it on all 932,791 agent-authored pull requests in the AIDev dataset, covering five autonomous coding agents. Each pull request is automatically classified by authority scope - data-plane or control-plane - and assigned a penalty score. We found that control-plane actions have a 2.3x higher mean joint penalty than data-plane actions (0.498 vs. 0.218) and a 3.9x higher mean governance risk (0.530 vs. 0.135), which means that they indeed increase the risk. All 775 pull requests in the extreme-risk category, defined as P(M) > 0.8, modify the control plane. Policy-violation flags occur in 46.6% of all control-plane pull requests and in 63.6% of merged control-plane pull requests. We have also found an indication that governance risk differs substantially across agent implementations, ranging from 0.166 for Cursor to 0.328 for Copilot in mean joint penalty. These differences are not explained by execution cost or merge rate, suggesting that authority policies should be calibrated for individual agents. Manual assessment of 34 pull requests yielded a Cohen's kappa of 0.72 for the authority-scope classifier. The results show that a single compound metric can identify and measure changes to CI/CD governance structures at scale. The proposed framework supports detecting high-risk pull requests and comparing governance behavior across agent implementations, providing a basis for authority tuning and pipeline governance in agentic software development.
Source:https://arxiv.org/abs/2611.23251PreviousWhat Moves the Ceiling on Automated Audit: from General Code to Scientific Code, Results and DataNextFrom Data Quality to Data Trustworthiness in AI-Driven Software-Intensive Embedded Systems: A Systematic Review
Related posts
Idempotency Is Not Recovery: A Fault-Injection Study of Language-Model Agent Tool Actions
0arXiv cs.SE
EnvAgent: Multi-Agent Approach to Building Science Environments in the Clouds
0arXiv cs.SE
Fairstone Bank, N.A. is hiring a DevOps / Site Reliability Engineer — Remote (US) or Wilmington, DE
0dev.to DevOps
🚀 I Built My Own DevOps Platform Using Kubernetes — No More Tool Sprawl!
0dev.to Kubernetes

P4 - El cluster OKE y sus node pools: ARM, fault domains y un autoscaler que no es Karpenter
0dev.to Kubernetes

Proton’s Lumo AI chatbot is now available on Linux desktops
0OMG! Ubuntu