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

72-Step Claude Setup Checklist: From Default to Power User
A detailed medium article outlines a 72-step checklist for configuring Claude, moving from default settings to advanced power-user features. Shared on HN with 10 points and 1 comment.

Practical OpenClaw Setup Insights from Docker/Windows Experience
A developer shares specific lessons from running OpenClaw on Docker with Windows 11/WSL2, covering persistence issues, Discord bot configuration, memory management approaches, and browser automation workarounds.

iOS Shortcut Workaround for Sending iPhone Photos to Cowork via iCloud Sync
A developer created an iOS Shortcut called "PhoPo" that converts iPhone photos to JPEG, resizes them, and saves them to an iCloud-synced folder that Cowork can access, enabling Claude to analyze screenshots and photos from mobile devices.

Trellis 2 Successfully Running on ROCm 7.11 with AMD RX 9070 XT
A developer got Trellis 2 working on Linux Mint 22.3 with an AMD RX 9070 XT using ROCm 7.11, fixing two key issues: ROCm instability with high N tensors and a broken hipMemcpy2D in CuMesh.