Bug Description
Fresh install, no prior setup.
I installed hermes and directly created a profile:
hermes profile create fern
I had already installed the gateway earlier, and I use:
after every config/env change to make sure everything reloads.
I expected the profile directory:
/home/craftpip/.hermes/profiles/fern
to act as the working directory.
But running:
always returns:
/home/craftpip/.hermes/hermes-agent
what i tried
1. profile config
File:
/home/craftpip/.hermes/profiles/fern/config.yaml
Config:
terminal:
backend: local
cwd: /home/craftpip/.hermes/profiles/fern
Restarted gateway:
No change.
2. .env (both global + profile)
Set:
MESSAGING_CWD=/home/craftpip/.hermes/profiles/fern
TERMINAL_CWD=/home/craftpip/.hermes/profiles/fern
Restarted gateway again:
Inside session:
echo $MESSAGING_CWD
echo $TERMINAL_CWD
Output is correct:
/home/craftpip/.hermes/profiles/fern
But:
still shows:
/home/craftpip/.hermes/hermes-agent
3. reset / restart attempts
- /reset
- /new
- fern gateway restart after each change
- killed processes manually (pkill -f hermes)
No change.
current state
Env is clearly being picked up, but terminal execution ignores it:
MESSAGING_CWD = correct
TERMINAL_CWD = correct
pwd = wrong
question
- Is this expected behavior?
- Are profiles not meant to control working directory?
- Or is gateway/session overriding cwd internally?
Right now there is no way to make Telegram mode respect a specific working directory, even with explicit config + env.
Need clarification or correct way to control cwd.
Steps to Reproduce
.
Expected Behavior
.
Actual Behavior
.
Affected Component
Gateway (Telegram/Discord/Slack/WhatsApp)
Messaging Platform (if gateway-related)
Telegram
Operating System
Ubuntu 24
Python Version
3.11
Hermes Version
v0.8.0
Relevant Logs / Traceback
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?
Bug Description
Fresh install, no prior setup.
I installed hermes and directly created a profile:
I had already installed the gateway earlier, and I use:
after every config/env change to make sure everything reloads.
I expected the profile directory:
/home/craftpip/.hermes/profiles/fern
to act as the working directory.
But running:
pwdalways returns:
/home/craftpip/.hermes/hermes-agent
what i tried
1. profile config
File:
/home/craftpip/.hermes/profiles/fern/config.yaml
Config:
Restarted gateway:
No change.
2. .env (both global + profile)
Set:
Restarted gateway again:
Inside session:
Output is correct:
/home/craftpip/.hermes/profiles/fern
But:
pwdstill shows:
/home/craftpip/.hermes/hermes-agent
3. reset / restart attempts
No change.
current state
Env is clearly being picked up, but terminal execution ignores it:
MESSAGING_CWD = correct
TERMINAL_CWD = correct
pwd = wrong
question
Right now there is no way to make Telegram mode respect a specific working directory, even with explicit config + env.
Need clarification or correct way to control cwd.
Steps to Reproduce
.
Expected Behavior
.
Actual Behavior
.
Affected Component
Gateway (Telegram/Discord/Slack/WhatsApp)
Messaging Platform (if gateway-related)
Telegram
Operating System
Ubuntu 24
Python Version
3.11
Hermes Version
v0.8.0
Relevant Logs / Traceback
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?