Components of a Coding Agent: How Tools, Memory, and Context Extend LLMs

Sebastian Raschka outlines the architecture of coding agents, which are systems that wrap LLMs in application layers to improve performance on coding tasks. He distinguishes between LLMs, reasoning models, and agents, explaining that much of the practical progress in LLM systems comes from the surrounding system components rather than just better models.
Key Components of Coding Agents
The article identifies six main building blocks that make coding agents effective:
- Repo context: Navigation and management of code repository information
- Tool design: Integration of external tools and functions
- Prompt-cache stability: Consistent prompt management across sessions
- Memory: State retention and session continuity
- Long-session continuity: Maintaining context over extended interactions
- Model choice: Selection of appropriate LLM or reasoning model
Architecture Layers
Raschka defines several key concepts in the agent ecosystem:
- LLM: The core next-token model
- Reasoning model: An LLM trained or prompted to spend more inference-time compute on intermediate reasoning, verification, or search over candidate answers
- Agent: A control loop around the model that decides what to inspect next, which tools to call, how to update its state, and when to stop
- Agent harness: The software scaffold around an agent that manages context, tool use, prompts, state, and control flow
- Coding harness: A special case of agent harness specifically for software engineering that manages code context, tools, execution, and iterative feedback
He notes that Claude Code and Codex CLI can be considered coding harnesses. The relationship is described as: the LLM is the engine, a reasoning model is a beefed-up engine, and an agent harness helps us use the model effectively.
Coding work involves more than just next-token generation—it requires repo navigation, search, function lookup, diff application, test execution, error inspection, and context management. Coding harnesses combine three layers: the model family, an agent loop, and runtime supports.
📖 Read the full source: HN AI Agents
👀 See Also

Practical Glossary for AI Agent Terminology (Harness, Scaffold, Agent, etc.)
A glossary from Hugging Face blog explaining common AI agent terms like Harness, Scaffold, and Agent with simple definitions and real examples.

OpenClaw Installation on MacBook Pro Using Local Homebrew and NVM
A user successfully installed OpenClaw on a MacBook Pro using a non-admin account with local Homebrew, NVM v0.40.4, Python 3.14.3 via pyenv, Node 24, and the Qwen3.5-122B-A10B-MLX-vision-4.7-bit LLM through oMLX.

Building API endpoints with Claude: Practical prompt engineering lessons from a 70+ endpoint project
A developer built 70+ LinkedIn automation API endpoints with Claude writing 80% of the code, discovering that treating prompts like contracts with explicit constraints works better than natural language instructions for action-taking agents.

Java Performance Optimization: Eight Anti-Patterns That Slow Down Your Code
A Java order-processing app improved from 1,198ms to 239ms elapsed time, 85,000 to 419,000 orders per second, and 1GB to 139MB heap usage by fixing eight common anti-patterns identified through Java Flight Recording profiling.