hermes-agent

mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-05-04 17:57:28 +08:00

Files

Siddharth Balyan 9eaddfafa3 fix(cli): CLI/TUI on local backend always uses launch directory, ignores terminal.cwd (#19242 )

CLI/TUI sessions on the local backend now unconditionally use
os.getcwd() as the working directory. The terminal.cwd config value is
only consumed by gateway/cron/delegation modes (where there's no shell
to cd from).

Previously, 'hermes setup' would write an absolute path (e.g. $HOME)
into terminal.cwd which then pinned the CLI to that directory regardless
of where the user launched hermes from. This was a silent foot-gun —
the user's 'cd' was being ignored.

Changes:

1. cli.py: Restructured CWD resolution — if TERMINAL_CWD is not already
   set by the gateway, and the backend is local, always use os.getcwd().
   Config terminal.cwd is irrelevant for interactive CLI/TUI sessions.

2. setup.py: Moved the cwd prompt from setup_terminal_backend() to
   setup_gateway(). It now only appears when configuring messaging
   platforms and is labeled 'Gateway working directory'.

3. Tests: Rewrote test_cwd_env_respect.py to validate the new behavior:
   explicit config paths are ignored for CLI, gateway pre-set values are
   preserved, non-local backends keep their config paths.

4. Docs: Updated configuration.md, profiles.md, and
   environment-variables.md to clarify that terminal.cwd only affects
   gateway/cron mode on local backend.

Closes #19214

2026-05-04 00:14:36 +05:30

_category_.json

feat: add documentation website (Docusaurus)

2026-03-05 05:24:55 -08:00

cli-commands.md

fix(curator): defer first run and add --dry-run preview (#18373 ) (#18389 )

2026-05-01 09:49:59 -07:00

environment-variables.md

fix(cli): CLI/TUI on local backend always uses launch directory, ignores terminal.cwd (#19242 )

2026-05-04 00:14:36 +05:30

faq.md

docs(faq): Update docs on backups