Summary

Fixes a gateway / messaging working-directory bug where Telegram sessions ignored the configured profile cwd and kept starting in the gateway process launch directory
instead.

In affected setups, env/config values such as terminal.cwd, TERMINAL_CWD, and MESSAGING_CWD were present and correct, but commands like pwd still resolved to
~/.hermes/hermes-agent.

Fixes #7663

Root Cause

The config/env bridge in gateway/run.py was working correctly and did set TERMINAL_CWD.

The actual problem was lower in the terminal environment lifecycle:

• BaseEnvironment.init_session() creates the shell snapshot used by later terminal commands
• during that initialization, it captured the shell state and current directory
• but it did not first cd into the configured working directory
• so the snapshot locked in the gateway process startup directory instead of the configured terminal cwd

That made later commands inherit the wrong default directory even though the env vars were correct.

What Changed

• update BaseEnvironment.init_session() to cd into the configured cwd before capturing the shell snapshot
• reuse the same cwd quoting logic for both init-time and normal command execution
• add a regression test to verify init-session bootstrap honors configured cwd

Behavior Before

Configured profile/gateway cwd could be visible in env vars, but new messaging terminal sessions still started in the gateway launch directory:

• MESSAGING_CWD correct
• TERMINAL_CWD correct
• pwd wrong

Behavior After

When a terminal environment is initialized for messaging/gateway use, its initial shell snapshot now starts in the configured cwd, so subsequent commands like pwd reflect the
configured profile working directory.

Testing

Ran:

• .\venv\Scripts\python -m pytest tests\tools\test_base_environment.py tests\gateway\test_config_cwd_bridge.py -q