aiqbench analysis
This study provides critical empirical data on the reliability of wholly AI-authored software, revealing that nearly 15% of generated code contains errors caught by self-written tests and that factual hallucinations occur in roughly one out of every four to five responses. By introducing new provenance tracing tools and taxonomies for instruction intent, the research offers essential frameworks for assessing risk and maintaining integrity in autonomous development pipelines. These findings are pivotal for engineers and researchers navigating the practical limitations of current large language models in production environments.
Between the Commits: Process, Error, and Claim Reliability in a Wholly AI-Authored Codebase
arXiv:2609.29744v1 Announce Type: cross Abstract: We present: (i) a new dataset consisting of the full development history of a 21,000-line Python tool built entirely by Claude AI, with no human-authored code or tests, (ii) two code-provenance tracing tools, (iii) three taxonomies for instruction intent, commit provenance, and response reliability, (iv) application of these to analyse the dataset. We find that: (i) user coding agent CLI instructions differ in kind from IDE-chat instructions, with a greater focus on comprehension, planning and consultation, (ii) code development is mainly proactive, (iii) 14.3% of AI code-generation events contain a real error later caught by the AI-authored test suite, (iv) roughly 1 in 4-5 of the AI's interactive responses contains one or more factual errors.
Abstract:We present: (i) a new dataset consisting of the full development history of a 21,000-line Python tool built entirely by Claude AI, with no human-authored code or tests, (ii) two code-provenance tracing tools, (iii) three taxonomies for instruction intent, commit provenance, and response reliability, (iv) application of these to analyse the dataset. We find that: (i) user coding agent CLI instructions differ in kind from IDE-chat instructions, with a greater focus on comprehension, planning and consultation, (ii) code development is mainly proactive, (iii) 14.3% of AI code-generation events contain a real error later caught by the AI-authored test suite, (iv) roughly 1 in 4-5 of the AI's interactive responses contains one or more factual errors.
Software Engineering (cs.SE); Artificial Intelligence (cs.AI)
arXiv:2609.29744 [cs.SE]
(or arXiv:2609.29744v1 [cs.SE] for this version)
https://doi.org/10.48550/arXiv.2609.29744 Focus to learn more arXiv-issued DOI via DataCite (pending registration)
arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.
Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.
Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.
Full text under the publisher's open licence · 212 words
Related coverage

LiveLaw Supreme Court Half-Yearly Digest: January - June 2026 [Part 2]
livelaw.in · Sep 13, 2026

Brief independent investigation of agents’ behavior, reasoning and collaboration in the OpenAI / Hugging Face hacking incident
METR · Aug 26, 2026

[AINews] not much happened today
Latent Space · Sep 18, 2026

Lattice-Based Cryptography Explained
Quantum Zeitgeist · Aug 15, 2026