#
Agents - Guided tour

In this guided visit, you will learn how to build an agent, how to run it, and how to customize it to make it work better for your use-case.

##
Choosing an agent type: CodeAgent or ToolCallingAgent

`smolagents` comes with two agent classes: CodeAgent and ToolCallingAgent, which represent two different paradigms for how agents interact with tools. The key difference lies in how actions are specified and executed: code generation vs structured tool calling.

- CodeAgent generates tool calls as Python code snippets.

  - The code is executed either locally (potentially unsecure) or in a secure sandbox.
  - Tools are exposed as Python functions (via bindings).
  - Example of tool call:

        result = search_docs("What is the capital of France?")
        print(result)

  - Strengths:
    - Highly expressive: Allows for complex logic and control flow and can combine tools, loop, transform, reason.
    - Flexible: No need to predefine every possible action, can dynamically generate new actions/tools.
    - Emergent reasoning: Ideal for multi-step problems or dynamic logic.
  - Limitations
    - Risk of errors: Must handle syntax errors, exceptions.
    - Less predictable: More prone to unexpected or unsafe outputs.
    - Requires secure execution environment.

- ToolCallingAgent writes tool calls as structured JSON.

  - This is the common format used in many frameworks (OpenAI API), allowing for structured tool interactions without code execution.
  - Tools are defined with a JSON schema: name, description, parameter types, etc.
  - Example of tool call:

        {
          "tool_call": {
            "name": "search_docs",
            "arguments": {
              "query": "What is the capital of France?"
            }
          }
        }

  - Strengths:
    - Reliable: Less prone to hallucination, outputs are structured and validated.
    - Safe: Arguments are strictly validated, no risk of arbitrary code running.
    - Interoperable: Easy to map to external APIs or services.
  - Limitations:
    - Low expressivity: Can’t easily combine or transform results dynamically, or perform complex logic or control flow.
    - Inflexible: Must define all possible actions in advance, limited to predefined tools.
    - No code synthesis: Limited to tool capabilities.

When to use which agent type:

- Use CodeAgent when:

  - You need reasoning, chaining, or dynamic composition.
  - Tools are functions that can be combined (e.g., parsing + math + querying).
  - Your agent is a problem solver or programmer.

- Use ToolCallingAgent when:

  - You have simple, atomic tools (e.g., call an API, fetch a document).
  - You want high reliability and clear validation.
  - Your agent is like a dispatcher or controller.

##
CodeAgent

CodeAgent generates Python code snippets to perform actions and solve tasks.

By default, the Python code execution is done in your local environment. This should be safe because the only functions that can be called are the tools you provided (especially if it’s only tools by Hugging Face) and a set of predefined safe functions like `print` or functions from the `math` module, so you’re already limited in what can be executed.

The Python interpreter also doesn’t allow imports by default outside of a safe list, so all the most obvious attacks shouldn’t be an issue. You can authorize additional imports by passing the authorized modules as a list of strings in argument `additional_authorized_imports` upon initialization of your CodeAgent:

    model = InferenceClientModel()
    agent = CodeAgent(tools=[], model=model, additional_authorized_imports=['requests', 'bs4'])
    agent.run("Could you get me the title of the page at url 'https://huggingface.co/blog'?")

Additionally, as an extra security layer, access to submodule is forbidden by default, unless explicitly authorized within the import list. For instance, to access the `numpy.random` submodule, you need to add `'numpy.random'` to the `additional_authorized_imports` list. This could also be authorized by using `numpy.*`, which will allow `numpy` as well as any subpackage like `numpy.random` and its own subpackages.

The LLM can generate arbitrary code that will then be executed: do not add any unsafe imports!

The execution will stop at any code trying to perform an illegal operation or if there is a regular Python error with the code generated by the agent.

You can also use E2B code executor or Docker instead of a local Python interpreter. For E2B, first set the `E2B_API_KEY` environment variable and then pass `executor_type="e2b"` upon agent initialization. For Docker, pass `executor_type="docker"` during initialization.

Learn more about code execution in this tutorial.

###
ToolCallingAgent

ToolCallingAgent outputs JSON tool calls, which is the common format used in many frameworks (OpenAI API), allowing for structured tool interactions without code execution.

It works much in the same way like CodeAgent, of course without `additional_authorized_imports` since it doesn’t execute code:

    from smolagents import ToolCallingAgent

    agent = ToolCallingAgent(tools=[], model=model)
    agent.run("Could you get me the title of the page at url 'https://huggingface.co/blog'?")

##
Building your agent

To initialize a minimal agent, you need at least these two arguments:

- `model`, a text-generation model to power your agent - because the agent is different from a simple LLM, it is a system that uses a LLM as its engine. You can use any of these options:

  - TransformersModel takes a pre-initialized `transformers` pipeline to run inference on your local machine using `transformers`.
  - InferenceClientModel leverages a `huggingface_hub.InferenceClient` under the hood and supports all Inference Providers on the Hub: Cerebras, Cohere, Fal, Fireworks, HF-Inference, Hyperbolic, Nebius, Novita, Replicate, SambaNova, Together, and more.
  - LiteLLMModel similarly lets you call 100+ different models and providers through LiteLLM!
  - AzureOpenAIServerModel allows you to use OpenAI models deployed in Azure.
  - AmazonBedrockServerModel allows you to use Amazon Bedrock in AWS.
  - MLXModel creates a mlx-lm pipeline to run inference on your local machine.

- `tools`, a list of `Tools` that the agent can use to solve the task. It can be an empty list. You can also add the default toolbox on top of your `tools` list by defining the optional argument `add_base_tools=True`.

Once you have these two arguments, `tools` and `model`, you can create an agent and run it. You can use any LLM you’d like, either through Inference Providers, transformers, ollama, LiteLLM, Azure OpenAI, Amazon Bedrock, or mlx-lm.

All model classes support passing additional keyword arguments (like `temperature`, `max_tokens`, `top_p`, etc.) directly at instantiation time. These parameters are automatically forwarded to the underlying model’s completion calls, allowing you to configure model behavior such as creativity, response length, and sampling strategies.

Inference Providers
Local Transformers Model
OpenAI or Anthropic API
Ollama
Azure OpenAI
Amazon Bedrock
mlx-lm

Inference Providers need a `HF_TOKEN` to authenticate, but a free HF account already comes with included credits. Upgrade to PRO to raise your included credits.

To access gated models or rise your rate limits with a PRO account, you need to set the environment variable `HF_TOKEN` or pass `token` variable upon initialization of `InferenceClientModel`. You can get your token from your settings page

    from smolagents import CodeAgent, InferenceClientModel

    model_id = "meta-llama/Llama-3.3-70B-Instruct"

    model = InferenceClientModel(model_id=model_id, token="<YOUR_HUGGINGFACEHUB_API_TOKEN>") # You can choose to not pass any model_id to InferenceClientModel to use a default model
    # you can also specify a particular provider e.g. provider="together" or provider="sambanova"
    agent = CodeAgent(tools=[], model=model, add_base_tools=True)

    agent.run(
        "Could you give me the 118th number in the Fibonacci sequence?",
    )

###
Model parameter management

When initializing models, you can pass keyword arguments that will be forwarded as completion parameters to the underlying model API during inference.

For fine-grained control over parameter handling, the `REMOVE_PARAMETER` sentinel value allows you to explicitly exclude parameters that might otherwise be set by default or passed through elsewhere:

    from smolagents import OpenAIServerModel, REMOVE_PARAMETER

    # Remove "stop" parameter
    model = OpenAIServerModel(
        model_id="gpt-5",
        stop=REMOVE_PARAMETER,  # Ensures "stop" is not included in API calls
        temperature=0.7
    )

    agent = CodeAgent(tools=[], model=model, add_base_tools=True)

This is particularly useful when:

- You want to override default parameters that might be applied automatically
- You need to ensure certain parameters are completely excluded from API calls
- You want to let the model provider use their own defaults for specific parameters

##
Advanced agent configuration

###
Customizing agent termination conditions

By default, an agent continues running until it calls the `final_answer` function or reaches the maximum number of steps. The `final_answer_checks` parameter gives you more control over when and how an agent terminates its execution:

    from smolagents import CodeAgent, InferenceClientModel

    # Define a custom final answer check function
    def is_integer(final_answer: str, agent_memory=None) -> bool:
        """Return True if final_answer is an integer."""
        try:
            int(final_answer)
            return True
        except ValueError:
            return False

    # Initialize agent with custom final answer check
    agent = CodeAgent(
        tools=[],
        model=InferenceClientModel(),
        final_answer_checks=[is_integer]
    )

    agent.run("Calculate the least common multiple of 3 and 7")

The `final_answer_checks` parameter accepts a list of functions that each:

- Take the agent’s final_answer string the agent’s memory as parameters
- Return a boolean indicating whether the final_answer is valid (True) or not (False)

If any function returns `False`, the agent will log the error message and continue the run. This validation mechanism enables:

- Enforcing output format requirements (e.g., ensuring numeric answers for math problems)
- Implementing domain-specific validation rules
- Creating more robust agents that validate their own outputs

##
Inspecting an agent run

Here are a few useful attributes to inspect what happened after a run:

- `agent.logs` stores the fine-grained logs of the agent. At every step of the agent’s run, everything gets stored in a dictionary that then is appended to `agent.logs`.
- Running `agent.write_memory_to_messages()` writes the agent’s memory as list of chat messages for the Model to view. This method goes over each step of the log and only stores what it’s interested in as a message: for instance, it will save the system prompt and task in separate messages, then for each step it will store the LLM output as a message, and the tool call output as another message. Use this if you want a higher-level view of what has happened - but not every log will be transcripted by this method.

##
Tools

A tool is an atomic function to be used by an agent. To be used by an LLM, it also needs a few attributes that constitute its API and will be used to describe to the LLM how to call this tool:

- A name
- A description
- Input types and descriptions
- An output type

You can for instance check the PythonInterpreterTool: it has a name, a description, input descriptions, an output type, and a `forward` method to perform the action.

When the agent is initialized, the tool attributes are used to generate a tool description which is baked into the agent’s system prompt. This lets the agent know which tools it can use and why.

Schema Information: For tools that have an `output_schema` defined (such as MCP tools with structured output), the `CodeAgent` system prompt automatically includes the JSON schema information. This helps the agent understand the expected structure of tool outputs and access the data appropriately.

###
Default toolbox

If you install `smolagents` with the “toolkit” extra, it comes with a default toolbox for empowering agents, that you can add to your agent upon initialization with argument `add_base_tools=True`:

- DuckDuckGo web search*: performs a web search using DuckDuckGo browser.
- Python code interpreter: runs your LLM generated Python code in a secure environment. This tool will only be added to ToolCallingAgent if you initialize it with `add_base_tools=True`, since code-based agent can already natively execute Python code
- Transcriber: a speech-to-text pipeline built on Whisper-Turbo that transcribes an audio to text.

You can manually use a tool by calling it with its arguments.

    # !pip install 'smolagents[toolkit]'
    from smolagents import WebSearchTool

    search_tool = WebSearchTool()
    print(search_tool("Who's the current president of Russia?"))

###
Create a new tool

You can create your own tool for use cases not covered by the default tools from Hugging Face. For example, let’s create a tool that returns the most downloaded model for a given task from the Hub.

You’ll start with the code below.

    from huggingface_hub import list_models

    task = "text-classification"

    most_downloaded_model = next(iter(list_models(filter=task, sort="downloads", direction=-1)))
    print(most_downloaded_model.id)

This code can quickly be converted into a tool, just by wrapping it in a function and adding the `tool` decorator: This is not the only way to build the tool: you can directly define it as a subclass of Tool, which gives you more flexibility, for instance the possibility to initialize heavy class attributes.

Let’s see how it works for both options:

Decorate a function with @tool
Subclass Tool

    from smolagents import tool

    @tool
    def model_download_tool(task: str) -> str:
        """
        This is a tool that returns the most downloaded model of a given task on the Hugging Face Hub.
        It returns the name of the checkpoint.

        Args:
            task: The task for which to get the download count.
        """
        most_downloaded_model = next(iter(list_models(filter=task, sort="downloads", direction=-1)))
        return most_downloaded_model.id

The function needs:

- A clear name. The name should be descriptive enough of what this tool does to help the LLM brain powering the agent. Since this tool returns the model with the most downloads for a task, let’s name it `model_download_tool`.
- Type hints on both inputs and output
- A description, that includes an ‘Args:’ part where each argument is described (without a type indication this time, it will be pulled from the type hint). Same as for the tool name, this description is an instruction manual for the LLM powering your agent, so do not neglect it.

All these elements will be automatically baked into the agent’s system prompt upon initialization: so strive to make them as clear as possible!

This definition format is the same as tool schemas used in `apply_chat_template`, the only difference is the added `tool` decorator: read more on our tool use API here.

Then you can directly initialize your agent:

    from smolagents import CodeAgent, InferenceClientModel
    agent = CodeAgent(tools=[model_download_tool], model=InferenceClientModel())
    agent.run(
        "Can you give me the name of the model that has the most downloads in the 'text-to-video' task on the Hugging Face Hub?"
    )

You get the following logs:

    ╭──────────────────────────────────────── New run ─────────────────────────────────────────╮
    │                                                                                          │
    │ Can you give me the name of the model that has the most downloads in the 'text-to-video' │
    │ task on the Hugging Face Hub?                                                            │
    │                                                                                          │
    ╰─ InferenceClientModel - Qwen/Qwen2.5-Coder-32B-Instruct ───────────────────────────────────────────╯
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Step 0 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    ╭─ Executing this code: ───────────────────────────────────────────────────────────────────╮
    │   1 model_name = model_download_tool(task="text-to-video")                               │
    │   2 print(model_name)                                                                    │
    ╰──────────────────────────────────────────────────────────────────────────────────────────╯
    Execution logs:
    ByteDance/AnimateDiff-Lightning

    Out: None
    [Step 0: Duration 0.27 seconds| Input tokens: 2,069 | Output tokens: 60]
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Step 1 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    ╭─ Executing this code: ───────────────────────────────────────────────────────────────────╮
    │   1 final_answer("ByteDance/AnimateDiff-Lightning")                                      │
    ╰──────────────────────────────────────────────────────────────────────────────────────────╯
    Out - Final answer: ByteDance/AnimateDiff-Lightning
    [Step 1: Duration 0.10 seconds| Input tokens: 4,288 | Output tokens: 148]
    Out[20]: 'ByteDance/AnimateDiff-Lightning'

Read more on tools in the dedicated tutorial.

##
Multi-agents

Multi-agent systems have been introduced with Microsoft’s framework Autogen.

In this type of framework, you have several agents working together to solve your task instead of only one. It empirically yields better performance on most benchmarks. The reason for this better performance is conceptually simple: for many tasks, rather than using a do-it-all system, you would prefer to specialize units on sub-tasks. Here, having agents with separate tool sets and memories allows to achieve efficient specialization. For instance, why fill the memory of the code generating agent with all the content of webpages visited by the web search agent? It’s better to keep them separate.

You can easily build hierarchical multi-agent systems with `smolagents`.

To do so, just ensure your agent has `name` and`description` attributes, which will then be embedded in the manager agent’s system prompt to let it know how to call this managed agent, as we also do for tools. Then you can pass this managed agent in the parameter managed_agents upon initialization of the manager agent.

Here’s an example of making an agent that managed a specific web search agent using our native WebSearchTool:

    from smolagents import CodeAgent, InferenceClientModel, WebSearchTool

    model = InferenceClientModel()

    web_agent = CodeAgent(
        tools=[WebSearchTool()],
        model=model,
        name="web_search_agent",
        description="Runs web searches for you. Give it your query as an argument."
    )

    manager_agent = CodeAgent(
        tools=[], model=model, managed_agents=[web_agent]
    )

    manager_agent.run("Who is the CEO of Hugging Face?")

For an in-depth example of an efficient multi-agent implementation, see how we pushed our multi-agent system to the top of the GAIA leaderboard.

##
Talk with your agent and visualize its thoughts in a cool Gradio interface

You can use `GradioUI` to interactively submit tasks to your agent and observe its thought and execution process, here is an example:

    from smolagents import (
        load_tool,
        CodeAgent,
        InferenceClientModel,
        GradioUI
    )

    # Import tool from Hub
    image_generation_tool = load_tool("m-ric/text-to-image", trust_remote_code=True)

    model = InferenceClientModel(model_id=model_id)

    # Initialize the agent with the image generation tool
    agent = CodeAgent(tools=[image_generation_tool], model=model)

    GradioUI(agent).launch()

Under the hood, when the user types a new answer, the agent is launched with `agent.run(user_request, reset=False)`. The `reset=False` flag means the agent’s memory is not flushed before launching this new task, which lets the conversation go on.

You can also use this `reset=False` argument to keep the conversation going in any other agentic application.

In gradio UIs, if you want to allow users to interrupt a running agent, you could do this with a button that triggers method `agent.interrupt()`. This will stop the agent at the end of its current step, then raise an error.

##
Next steps

Finally, when you’ve configured your agent to your needs, you can share it to the Hub!

    agent.push_to_hub("m-ric/my_agent")

Similarly, to load an agent that has been pushed to hub, if you trust the code from its tools, use:

    agent.from_hub("m-ric/my_agent", trust_remote_code=True)

For more in-depth usage, you will then want to check out our tutorials:

- the explanation of how our code agents work
- this guide on how to build good agents.
- the in-depth guide for tool usage.

< > Update on GitHub