Skip to main content
ZICQ

Wiki AI Concepts

Coding Agent

AI Concepts
Aliases: AI Coding Agent CLI Coding Agent Autonomous Software Agent ·2026-11-18

Coding Agent

A coding agent is an AI agent wired directly into a software development environment—capable of searching repositories, editing multiple files, running compilers and test suites, inspecting failures, and iterating until checks pass. Unlike single-turn autocomplete or chat snippets, coding agents (such as Claude Code, Codex CLI, and Cursor Agent) close the loop against deterministic build and test feedback.

The Edit-Test-Verify Loop

Task / Issue ──► [Locate: ripgrep / AST / symbol search]
                      │
                      ▼
                 [Plan & apply targeted file diffs]
                      │
                      ▼
                 [Run build / linter / tests in sandbox] ──(failure)──┐
                      │                                               │
                    (pass) ◄──────────────────────────────────────────┘
                      ▼
                 [Present minimal diff + verified check output]

What makes coding agents uniquely reliable compared to open-ended chat is verifiable environmental feedback: type errors, stack traces, and failing unit tests anchor the model in ground truth rather than unchecked guesses.

Core Engineering Components

  1. Targeted Code Search: Instead of stuffing entire repositories into context, agents query with rg, file trees, or symbol lookups and read specific line ranges under disciplined context engineering budgets.
  2. Structured Diff Editing: Line-anchored or search-and-replace edits modify targeted regions safely, avoiding whole-file rewrites that introduce accidental truncations.
  3. Sandboxed Command Execution: Agents run test runners, linters, and build tools inside isolated containers or git worktrees with restricted network and credential exposure.
  4. Composable Extensibility: Agent Skills (SKILL.md) package repeatable team playbooks, while MCP connects repositories, issue trackers, and observability systems.

Evaluation and Selection

  • SWE-bench & Real Repo Suites: Evaluates end-to-end patch synthesis on real issues; results depend heavily on both the underlying model and the agent harness (tools, context pruning, retry rules).
  • Diff Minimalism & Test Integrity: Inspect whether the agent modifies unrelated code or weakens test assertions simply to make checks pass.
  • Reviewability: Strong coding agents leave concise, coherent diffs and accurately report exact commands and scopes executed.

Security Boundaries and Limitations

  • Indirect Prompt Injection via Untrusted Repos: Issues, PR comments, or third-party dependencies can embed prompt injections. Never give an autonomous shell-capable agent unguarded access to secrets or production hosts when scanning untrusted code.
  • Error Spiral & Context Pollution: Dozens of raw failing logs can degrade reasoning; checkpoints, git worktrees, and subagent isolation help keep context clean.
  • Architectural Judgment: Coding agents accelerate implementation, refactoring, and test coverage, while system architecture, threat modeling, and irreversible migrations remain human engineering responsibilities.

Further Reading