Tools
Agentic coding tools are the CLIs, editors and autonomous agents that run a model against your codebase, plus the protocols and models underneath them. They converge with every model generation, so the lasting investment is the harness you build around a tool, not the tool you license.
Written by
-
Benedikt Stemmildt Founder & Co-CEO
Updated:
Tools 4
Our position. Tool fatigue is a missing context layer, not a tool count: once a team writes down its skills, commands and conventions, the tool list collapses on its own (opens in a new tab).
The stack has four layers: the agent surface you work in, the extensions that configure it, the protocol that connects it to other systems, and the model that does the reasoning. Pick the layer you are deciding about.
Which layer are you deciding about?
- AI Coding Tools — terminal CLIs, editors and IDEs, autonomous agents, and enterprise platforms, and why the wrapper stopped being the differentiator.
- Claude Code Ecosystem — configuration, plugins, skills, hooks, GUIs, trackers, and routing built around Claude Code.
- Claude Code techniques — the deep, practitioner-level reference: architecture internals, context engineering, hooks, multi-agent patterns, the SDK, and prompt engineering.
- AI Models & Inference — the model layer: providers, local inference, pricing economics, and reading coding benchmarks.
Related
- Agentic Engineering: what good practice with these tools looks like, whichever vendor ships them.
- Software Factories: how to run the tools as a production system.
- Software Factories and Harness Engineering: why the harness around a tool outlasts the tool.
- Memory and Context Engineering: how to build the context layer that lets the next tool slot in.
- Getting Started: where a team new to agentic tools begins.
Resources
Posts
- The tool list collapses on its own (opens in a new tab) - LinkedIn post arguing that tool fatigue is a missing context layer, which disappears once a team writes down its skills and conventions.
In this section
- AI Coding Tools
AI coding tools come in four form factors: terminal CLIs, AI-native editors, autonomous agents and enterprise platforms. The brand matters less than which generation of tool you adopt, what the evidence says about its productivity effect, and how its pricing behaves under agentic workloads.
- AI Models and Inference
Which model runs an agent, where it runs and what each token costs determine whether an agentic workflow pays off. Outcomes depend more on the harness around the model, its context management, tool selection and validation, than on which frontier model sits underneath.
- Claude Code
Claude Code is a coding agent built as one simple loop over a small set of tools. That design leaves most of the leverage with the user: how you manage its context, how you prompt it, and how you extend it with hooks, skills, sub-agents and MCP.
- Claude Code Ecosystem
Claude Code ships as a thin harness over the model, so most of its practical leverage sits in the ecosystem around its extension points: plugins, skills, hooks, MCP servers, usage trackers, routing proxies and token optimizers. The same openness makes that ecosystem large and noisy.