Skip to content

[Bug]: terminal.cwd is not respected by terminal tool #14044

@qpilotwave

Description

@qpilotwave

Bug Description

I have terminal.cwd in config.yaml set to absolute path e.g. /home/username/projects. The path shows up in TUI/CLI, but the actual calls to terminal tool (e.g. pwd) show that the working dir is the one I have run hermes command in. File & path completions in the TUI's input field resolve relative to the directory where I invoked "hermes chat" command.

Steps to Reproduce

  1. set terminal.cwd to anything other than '.' in config.yaml
  2. run "hermes chat"
  3. ask model to run pwd (or anything else with terminal tool, local backend)
  4. type ./ in the chat window to elicit file completions

Expected Behavior

terminal and chat TUI completions pick up path from terminal.cwd as the current working directory

Actual Behavior

terminal commands and completions work as if '.' (where "hermes chat" was started) is the current directory

Affected Component

CLI (interactive chat)

Messaging Platform (if gateway-related)

No response

Debug Report

Debug report uploaded:
  Report     https://paste.rs/KJqq8
  agent.log  https://paste.rs/EUd0D

Operating System

Arch

Python Version

3.14.4

Hermes Version

0.10.0

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

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

    P1High — major feature broken, no workaroundarea/configConfig system, migrations, profilescomp/cliCLI entry point, hermes_cli/, setup wizardtool/terminalTerminal execution and process managementtype/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