Bug Description
It is said that hermes would use current dir as working dir, but when I use docker as backend, there are nothing inside /workspace directory. I need to modify the ~/.hermes/config.yaml file each time. This is not convenient at all.
Steps to Reproduce
- cd xxx dir
- hermes
- send "check what is in /workspace"
- response "nothing"
Expected Behavior
response "xxx" dir
Actual Behavior
response "nothing"
Affected Component
CLI (interactive chat)
Messaging Platform (if gateway-related)
No response
Operating System
Ubuntu 22.04
Python Version
3.11.9
Hermes Version
v0.2.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
It is said that hermes would use current dir as working dir, but when I use docker as backend, there are nothing inside /workspace directory. I need to modify the ~/.hermes/config.yaml file each time. This is not convenient at all.
Steps to Reproduce
Expected Behavior
response "xxx" dir
Actual Behavior
response "nothing"
Affected Component
CLI (interactive chat)
Messaging Platform (if gateway-related)
No response
Operating System
Ubuntu 22.04
Python Version
3.11.9
Hermes Version
v0.2.0
Relevant Logs / Traceback
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?