Credential write guards anchored to real home directory
Cluster 113628. Data as of
Nothing open on GitHub. Fix merged in #114859 on 18 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 #114859. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114859. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a security gap where file write guards for credentials were anchored only to the process HOME, leaving the real home directory unguarded in profile-home deployment scenarios. The work extends the guards to cover every home directory a write could land in.
Open issues0
Open PRs0
Fixes on record
-
#114859 fix(file-safety): credential write guards cover the real home under profile-home deployments (#113628, salvage #113629)
files:
agent/file_safety.py,tests/agent/test_file_safety_write_credentials.py,website/docs/user-guide/security.md
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
Closed issues · 1
- Closed#113628security: file write guards anchor on process HOME — real-home credentials unguarded under profile-home deployments
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 LabAt a glance
- Merged PRs
- #114859
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 18 Sep 2026