Developer Tools & Code Intelligence · core
Coding Agent Systems
Repository context, planning, file edits, tools, tests, sandboxes, review loops, and patch delivery.
Mental model
A coding agent is a repository-aware control loop. It needs scoped context, reversible edits, executable verification, and a clear handoff boundary.
How to study Coding Agent Systems
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use SWE-agent, SWE-bench: Can Language Models Resolve Real-World GitHub Issues?, OpenHands: An Open Platform for AI Software Developers to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Coding Agent Systems with IDE & CLI Tooling, Software Supply-chain Health. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Design exercise: Coding Agent Systems and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
Practice and explain it back
Design exercise: Coding Agent Systems
Repository context, planning, file edits, tools, tests, sandboxes, review loops, and patch delivery. Implement designOutline() returning non-empty values for: repoContext, editLoop, verification. Each value must name a concrete mechanism or decision.
Expected evidence: A design outline with repoContext, editLoop, verification plus an explicit failure mode or trade-off.
Open the interactive drill →Review prompts
- What makes an edit reversible in a coding agent, and why does that matter more than edit quality?
Build evidence
Synthesize: Developer Tools & Code Intelligence
Build repository-aware tools that analyze, test, review, debug, and safely remediate code. Produce one working system, benchmark, or evidence-backed design that integrates the path.
- Implements or precisely models the core mechanisms from all three milestones
- Includes at least one injected failure or adversarial case and demonstrates recovery
- Reports quality, latency, resource, reliability, or usability measurements relevant to the domain
- Ships a concise architecture note explaining decisions, trade-offs, and remaining risks