Cairn
NousResearch/hermes-agent

Email read-only and inbound-only delivery handling

Cluster 99876 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items relate to adding a read-only or no-auto-reply mode to the email platform and ensuring inbound-only email delivery fails closed. They share a theme of restricting or controlling outbound email behavior.

Open issues1

  • Issue#99876[Feature]: Email platform - add read-only / no-auto-reply mode

Open PRs1

  • PR#99900feat(email): add read-only / no-auto-reply mode

1 PR closed without merging

From the close comments: done elsewhere 1

  • #101053 fix(email): fail closed for all inbound-only delivery (#99876) · done elsewhere
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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/99876.json
cluster/99876.md