An agent framework packages common infrastructure needed to build agent applications. It may manage model calls, tool definitions, message history, state transitions, retries, tracing and the loop that connects those pieces.
Frameworks reduce boilerplate, but they do not remove product responsibilities. Developers still need to define useful tools, permissions, domain instructions, evaluations and recovery behavior that match the consequences of the task.
ELI5
An agent framework is a box of reusable building parts for making agents. It supplies common plumbing so every project does not need to recreate the same loop and tool wiring.
For example, a framework can deliver a tool result back to the model and keep the session history. The developer still decides which tools are safe and what a successful outcome means.
Does an agent framework provide every application tool?
Usually not. It provides common structures, while developers or platform services supply the domain-specific capabilities and permissions.
Can an agent be built without a framework?
Yes, but the developer must implement or assemble the control loop, state, tool routing, error handling and observability directly.
