Cairn
NousResearch/hermes-agent

E.164 phone number redaction classification and control

Cluster 68911 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These members address how E.164 phone numbers are categorized (PII vs. secrets) and whether they are redacted by default, including a bug report about unwanted redaction and a config opt-in to preserve them in responses.

Open issues1

  • Issue#68911[Bug]: Gateway force-redacts standalone E.164 phone numbers with no trusted-profile opt-in

Open PRs2

  • PR#68916gateway: add preserve_e164_chat_responses config opt-in for E.164 phone numbers (#68911)
  • PR#69890fix(redact): reclassify E.164 phone numbers as PII, not secrets
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.67: the share of item 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.

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

At a glance

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/68911.json
cluster/68911.md