← The reading
The bibliography
§8 · Coding Agents and Software Engineering
the-machine
CAPTURED
16 On the list1 Starred0 In the Atlas16 To read
Rungs
Where this section moves a number- Agentic AIRung 5
The pick
The source author's must-read for this sectionThe papers
16 papers- AI IDEs or Autonomous Agents? Measuring the Impact of Coding Agents on Software Development ↗
- CodeOCR: On the Effectiveness of Vision Language Models in Code Understanding ↗
- AutoHarness: Improving LLM Agents by Automatically Synthesizing a Code Harness ↗
- Evaluating AGENTS.md: Are Repository-Level Context Files Helpful for Coding Agents? ↗★
- LongCLI-Bench: A Preliminary Benchmark and Study for Long-Horizon Agentic Programming in Command-Line Interfaces ↗
- On Data Engineering for Scaling LLM Terminal Capabilities ↗
- SWE-rebench V2: Language-Agnostic SWE Task Collection at Scale ↗
- Qwen3-Coder-Next Technical Report ↗
- BeyondSWE: Can Current Code Agent Survive Beyond Single-Repo Bug Fixing? ↗
- Coding Agents Are Effective Long-Context Processors ↗
- Effective Strategies for Asynchronous Software Engineering Agents ↗
- Meta-Harness: End-to-End Optimization of Model Harnesses ↗
- Scaling Coding Agents via Atomic Skills ↗
- Frontier Coding Agents Can Now Implement an AlphaZero Self-Play ML Pipeline for Connect Four That Performs Comparably to an External Solver ↗
- Agentic Harness Engineering: Observability-Driven Automatic Evolution of Coding-Agent Harnesses ↗
- Code as Agent Harness ↗
What counts as read
A paper is on this list because someone worth reading put it there. That is a pointer, not a claim: it counts as read only once it has a close-read file in kb/<topic>/raw/, which is what a close-read link on a row means. There is deliberately nothing to tick off here — the study desk is the only writer of study state, and a second way to mark something done is a second version of the truth.