PR #14079: fix(cli): bridge terminal.cwd config to TERMINAL_CWD in TUI gateway

• Repository: NousResearch/hermes-agent
• Author: konsisumer
• State: closed | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/14079

Description (problem / solution / changelog)

When hermes chat launches the TUI, cli.py and its load_cli_config() are never imported, so terminal.cwd in config.yaml was never bridged to the TERMINAL_CWD environment variable. Everything in the TUI gateway then fell back to os.getcwd() (the directory where hermes chat was invoked), ignoring the configured path.

What changed and why

• tui_gateway/server.py startup: Added a config.yaml → env var bridge for all terminal.* settings, mirroring the equivalent bridge already present in gateway/run.py. Placeholder cwd values (".", "auto", "cwd") are skipped to avoid overwriting a pre-resolved TERMINAL_CWD.
• complete.path handler: Changed relative path resolution to use TERMINAL_CWD (falling back to os.getcwd()) as the base directory instead of the hardcoded process CWD (".")). Also fixed os.path.relpath() calls to be relative to TERMINAL_CWD, so completion texts are correct.
• Existing tests (test_complete_path_at_filter.py): Updated four tests to use monkeypatch.setenv("TERMINAL_CWD", ...) instead of monkeypatch.chdir(), matching the new resolution order and making them robust to any pre-set TERMINAL_CWD in the test environment.
• New tests (tests/tui_gateway/test_cwd_config_bridge.py): 14 tests covering the config bridge semantics (placeholder skipping, override behaviour) and complete.path resolution against TERMINAL_CWD.

How to test

• Set terminal.cwd: /some/absolute/path in ~/.hermes/config.yaml
• Run hermes chat (TUI mode)
• Ask the model to run pwd — it should report /some/absolute/path
• Type ./ in the chat input — file completions should list contents of /some/absolute/path, not the launch directory
• Run pytest tests/tui_gateway/test_cwd_config_bridge.py tests/gateway/test_complete_path_at_filter.py -v

What platforms tested on

• macOS on darwin-arm64 (local)

Fixes #14044

<!-- autocontrib:worker-id=issue-new-81f7c474 kind=pr-open -->

Changed files

• tests/gateway/test_complete_path_at_filter.py (modified, +4/-4)
• tests/tui_gateway/test_cwd_config_bridge.py (added, +212/-0)
• tui_gateway/server.py (modified, +66/-7)

---

PR #14136: fix(cli): respect terminal.cwd in chat sessions

• Repository: NousResearch/hermes-agent
• Author: LeonSGP43
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/14136

Description (problem / solution / changelog)

Fixes #14044.

Summary

• seed environment snapshots from the configured terminal cwd so chat sessions stop resetting to the launch directory
• resolve relative CLI path completions from TERMINAL_CWD instead of the process cwd
• add regressions covering both the local terminal session cwd and interactive path completion behavior

Testing

• pytest -o addopts= tests/hermes_cli/test_path_completion.py
• pytest -o addopts= tests/tools/test_local_shell_init.py

Changed files

• hermes_cli/commands.py (modified, +12/-4)
• tests/hermes_cli/test_path_completion.py (modified, +17/-0)
• tests/tools/test_local_shell_init.py (modified, +21/-0)
• tools/environments/base.py (modified, +7/-1)

---

PR #14264: fix(terminal): use TERMINAL_CWD for local backend default_cwd

• Repository: NousResearch/hermes-agent
• Author: ms-alan
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/14264

Description (problem / solution / changelog)

Previously, the 'local' backend always defaulted to os.getcwd() regardless of the terminal.cwd config / TERMINAL_CWD env var, because the local branch set default_cwd before the shared TERMINAL_CWD lookup. Now the local branch also respects TERMINAL_CWD when set.

Closes #14044

Changed files

• agent/error_classifier.py (modified, +8/-0)
• gateway/run.py (modified, +1/-1)
• plugins/memory/holographic/retrieval.py (modified, +15/-1)
• tools/terminal_tool.py (modified, +3/-1)