Academy → Using HermesOfficial documentation · clear explanation

Code Execution

Code Execution

Intermediate13 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Code Execution as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect How It Works, When the Agent Uses This, Practical Examples, then verify failure modes and version compatibility.

What do you need first?

Complete installation and one successful task before adding new capabilities.

What will you know?

A clear outcome before you read.

  • Understand Code Execution without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

Tool
A structured action the agent can call to read or change something.
Official page description

Programmatic Python execution with RPC tool access — collapse multi-step workflows into a single turn

Topic map

What does the source say, and in what order?

  1. 01
    How It Works

    Start here to understand the core idea or structure.

  2. 02
    When the Agent Uses This

    Read this after the foundation, then connect it to the previous step.

  3. 03
    Practical Examples

    Read this after the foundation, then connect it to the previous step.

  4. 04
    Data Processing Pipeline

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Multi-Step Web Research

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Bulk File Refactoring

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Build and Test Pipeline

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Execution Mode

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Resource Limits

    Read this after the foundation, then connect it to the previous step.

  10. 10
    How Tool Calls Work Inside Scripts

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

**Available tools inside scripts:** `web_search`, `web_extract`, `read_file`, `write_file`, `search_files`, `patch`, `terminal` (foreground only). ## When the Agent Uses This The agent uses `execute_code` when there are: - **3+ tool calls** with processing logic between them - Bulk data filtering or conditional branching - Loops over results The key benefit: intermediate tool results never enter the context window — only the final `print()` output comes back, dramatically reducing token usage. ## Practical Examples ### Data Processing Pipeline
### Multi-Step Web Research
### Bulk File Refactoring
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Code Execution” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?