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

OpenClaw Agent Cost Analysis: From $340 to $112 Monthly with Five Optimizations
A developer tracked 18,000 API calls across four OpenClaw agents for 30 days, finding 70% of tasks didn't need GPT-4.1. By implementing prompt caching, shortening system prompts, batching analytics, switching to cheaper models, and adding max token limits, costs dropped from $340 to $112 monthly.

Practical Claude Code Workflow for Development Teams
A Reddit user shares their internal presentation on Claude Code best practices, including model selection, structured workflows, and specific prompt techniques to improve output quality.

7 Ways New Engineers Can Flourish with AI: Master Fundamentals, Collaborate with AI, Build End-to-End Projects
IEEE Spectrum article by Lokesh Lagudu offers 7 practical tips for new engineers to thrive in an AI-driven world, emphasizing fundamentals, AI collaboration, and project-based learning.

ClaudeBusiness Repo: Patterns for Running Real Businesses with Claude Code
A GitHub repo collecting practical patterns, frameworks, and guardrails from 35+ Reddit threads of founders using Claude to run service agencies and solo SaaS businesses.