# NousResearch/hermes-agent · WeCom AES key formats and message parsing fixes

## Open now

- 2 issues, 2 PRs open on GitHub.
- #11447: fix(wecom): aibot image decryption fails + group @mention not stripped
- #11890: WeCom inbound file decryption fails for urlsafe unpadded \`aeskey\` values
- PR #11750: fix(wecom): accept aibot hex keys and strip group mentions
- PR #11899: fix(wecom): accept urlsafe unpadded inbound aeskey

Multiple fixes addressing WeCom inbound message decryption failures caused by non-standard AES key formats (hex, urlsafe, unpadded), plus handling of aibot image URLs and group mention stripping.

## TL;DR

- 6 member(s): 2 open issue(s), 0 closed issue(s), 2 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.29`: the share of member 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.

## Open related issues

- #11447: fix(wecom): aibot image decryption fails + group @mention not stripped
- #11890: WeCom inbound file decryption fails for urlsafe unpadded \`aeskey\` values

## Prior & competing PRs

- **#11750: fix(wecom): accept aibot hex keys and strip group mentions**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `8b1ff55f5382052a5d98246659136e632af13697`, `46f2cc2844c1448f9bc35166c46b97c30af53dd0`, `8f4c0bf0882c3c7258a65e3adade12d5b08068ea`
  - files: `cli-config.yaml.example`, `gateway/config.py`, `gateway/platforms/wecom.py`, `tests/gateway/test_wecom.py`
- **#11899: fix(wecom): accept urlsafe unpadded inbound aeskey**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `3134e7da5303c7e9fb82be417aa59d67925b7c90`, `5600105478ffde29d7566b45421b100eaa29c4ef`
  - files: `gateway/platforms/wecom.py`, `tests/gateway/test_wecom.py`
- **#14580: Fix WeCom media decryption for unpadded aeskey**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `8f4c0bf0882c3c7258a65e3adade12d5b08068ea`, `5600105478ffde29d7566b45421b100eaa29c4ef`, `#11899`
- **#17375: fix(wecom): support aibot image pic_url and multiple AES key formats**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#11750`, `#12390`, `#11447`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`