Skip to content

[Bug]: Terminal tool description is misleading for Windows users #7672

@jiakeboge

Description

@jiakeboge

Bug Description

The terminal tool description contains misleading wording that implies all users are running on a Linux environment in the cloud, even when they are actually running locally on their own machine (including Windows users).

Steps to Reproduce

  1. Set up Hermes Agent on a Windows machine with TERMINAL_ENV=local (default)
  2. Start a conversation with the agent
  3. Observe the system prompt/tool description sent to the LLM for the terminal tool
  4. The description reads: "Execute shell commands on a Linux environment..."
  5. Later it mentions: "Important: cloud sandboxes may be cleaned up..."

Expected Behavior

Expected Behavior

The tool description should accurately reflect the configurable nature of the execution environment:

  • For local users: indicate commands run on the local machine
  • For Docker users: indicate commands run in a container
  • For cloud backend users: indicate commands run in cloud sandboxes

Suggested wording:

Execute shell commands in the configured environment
(local machine, Docker container, or cloud sandbox depending on setup).

And for the sandbox warning:

Important: Sandboxes (when configured) may be cleaned up...

Actual Behavior

The current description (line 516 in tools/terminal_tool.py) says:

Execute shell commands on a Linux environment. Filesystem usually persists between calls.
...
Important: cloud sandboxes may be cleaned up, idled out, or recreated between turns.

This causes confusion because:

  • Windows users running in local mode see "Linux environment" and think the agent is remote
  • The mention of "cloud sandboxes" suggests cloud execution even when using local backend
  • Users don't realize the terminal environment depends on their TERMINAL_ENV configuration

Affected Component

Tools (terminal, file ops, web, code execution, etc.)

Messaging Platform (if gateway-related)

No response

Operating System

Windows 11

Python Version

3.14.3

Hermes Version

0.8.0

Relevant Logs / Traceback

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

Metadata

Metadata

Assignees

No one assigned

    Labels

    type/bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions