# NousResearch/hermes-agent · TUI session cwd looked up from wrong profile

## Open now

- Nothing open on GitHub.

A bug caused TUI/dashboard sessions to open in another profile's working directory, because session creation sent no \`cwd\` and the fallback read from the wrong profile scope. The accompanying fixes correct where the launch-profile \`cwd\` is read from.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #116764. Verify it addresses your case.
- **Recommended:** read PR #116764 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-116764`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #115981: \[Bug\]: Dashboard/TUI session opens in ANOTHER profile's terminal.cwd (session.create sends no cwd; fallback reads the request-scoped profile config)

## Prior & competing PRs

- **#116764: fix(tui-gateway): launch-profile cwd is read from the launch home, not the active scope**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/tui_gateway/test_config_profile_scope.py`, `tests/tui_gateway/test_tui_gateway_server.py`, `tui_gateway/methods_config_set.py`, `tui_gateway/server.py`
- **#115996: fix(tui-gateway): prevent sessions from opening in another profile's workspace**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `ebe3fcb2f8`, `#116764`

## Fix status

- Merged to main in PR #116764 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.