Likely duplicate of #10226 — same fix: preserve existing TERMINAL_CWD instead of overwriting from MESSAGING_CWD in load_cli_config().

Thanks for the contribution @EdderTalmor! This fix has already landed on main via a broader CWD refactor.

This is an automated hermes-sweeper review.

• Implementing commit: 3c42064ef — "fix: enforce config.yaml as sole CWD source + deprecate .env CWD vars + add hermes memory reset (fix: enforce config.yaml as sole CWD source + deprecate .env CWD vars + add hermes memory reset #11029)", merged Apr 16 2026 (the day after this PR was opened).
• Location: cli.py lines 520–540 — the _CWD_PLACEHOLDERS guard checks for an already-set absolute TERMINAL_CWD and preserves it, falling back to os.getcwd() only for the local backend when no valid path exists. This is exactly the logic this PR proposes.
• Related: @alt-glitch noted this may duplicate fix(cli): respect existing TERMINAL_CWD from MESSAGING_CWD in load_cli_config #10226, which covers the same root cause with additional gateway/run.py and tools/environments/base.py changes.

The fix shipped as part of a larger unification that made config.yaml terminal.cwd the single source of truth for working directory. Closing as implemented on main.