Docker backend Windows host path remapping fixes
Cluster 90679 · environments. Data as of
Nothing open on GitHub. Fix merged in #121477 on 26 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #121477. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #121477. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where Windows host paths (e.g. D:\.hermes) are incorrectly used inside Docker containers, causing terminal commands and file tools to fail. The work involves remapping host session working directories and normalizing Windows paths to valid container paths like /workspace.
Open issues0
Open PRs0
Fixes on record
-
#114833 fix(tools): file tools keep working outside /workspace when terminal.cwd is a host path on the docker backend (#113894, #98723, salvage #113946, #113931)
files:
tests/tools/test_file_operations_edge_cases.py,tests/tools/test_file_ops_cwd_tracking.py,tests/tools/test_live_env_cwd_override_sanitize.py,tools/environments/docker.py,tools/file_operations.py,tools/file_operations_common.py,tools/file_operations_search.py,tools/terminal_tool.py,tools/terminal_tool_backends.py,website/docs/user-guide/configuration.md -
#121477 fix(docker): remap a mounted host session cwd to /workspace
files:
tests/tools/test_docker_mounted_host_session_cwd.py,tools/file_tools.py,tools/terminal_tool.py,tools/terminal_tool_background.py,tools/terminal_tool_config.py,tools/terminal_tool_guards.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#90805 fix(tui): normalize Windows host paths to container paths for Docker backend · done elsewhere →
b911b97,#90679,#114833
Closed issues · 1
- Closed#90679[Bug]: Terminal (Docker backend): every command in a new desktop session fails with `cd: D:\.hermes: No such file or directory` (exit 126)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab