
What impressed me most about smolagents was how little framework overhead there is. Defining a tool can be as simple as decorating a Python function and writing a useful docstring, while CodeAgent gives the model much more freedom to work with actual Python instead of getting stuck in repeated structured tool calls. I also liked that I could change the underlying model without having to redesign the agent, which made experimenting with different providers much easier. Review collected by and hosted on G2.com.
The biggest issue for me is the lack of control and visibility around agent execution. It’s difficult to tell how many tokens a run is consuming, and there aren’t built-in limits or warnings to prevent an unexpectedly expensive run. I also ran into a broken built-in tool because of an API change, which the agent managed to work around but shouldn’t have had to. Multi-agent workflows were another concern: one test ran for more than 15 minutes without producing anything, with no straightforward safeguards to stop it. For production use, I’d want much stronger monitoring and execution limits out of the box. Review collected by and hosted on G2.com.