Memory provider egress missing secret redaction
Cluster 115104 · agent. Data as of
1 open item. Fix merged in #134429 on 7 Oct 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 #134429. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #134429. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items concern a bug where secrets are not scrubbed before turns are synced to external memory providers. The work involves applying the egress redactor to provider-synced content before it leaves the system.
Open issues0
Open PRs1
- PR#115109fix(memory): scrub provider-synced turns with the egress redactor
Fixes on record
-
#134429 fix(memory): scrub secrets on every memory-provider hand-off
files:
agent/memory_manager.py,agent/redact.py,tests/agent/test_memory_sync_redaction.py,tests/agent/test_redact.py,website/docs/user-guide/features/memory-providers.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#115694 fix(memory): scrub secrets before memory-provider egress · superseded by another PR →
#134429
Closed issues · 1
- Closed#115104Memory-provider sync bypasses secret redaction (secrets archived verbatim by external memory providers)
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
- Subsystem
- agent
- Merged PRs
- #134429
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Oct 2026