Skip to content

Add WHATSAPP_GROUP_ALLOWED_USERS group allowlist support for WhatsApp gateway#8278

Open
RiptideV wants to merge 1 commit intoNousResearch:mainfrom
RiptideV:add-whatsapp-group-allowed-users
Open

Add WHATSAPP_GROUP_ALLOWED_USERS group allowlist support for WhatsApp gateway#8278
RiptideV wants to merge 1 commit intoNousResearch:mainfrom
RiptideV:add-whatsapp-group-allowed-users

Conversation

@RiptideV
Copy link
Copy Markdown

@RiptideV RiptideV commented Apr 12, 2026

What does this PR do?

Adds WHATSAPP_GROUP_ALLOWED_USERS group allowlist support like SIGNAL_GROUP_ALLOWED_USERS

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 🔒 Security fix
  • 📝 Documentation update
  • ✅ Tests (adding or improving test coverage)
  • ♻️ Refactor (no behavior change)
  • 🎯 New skill (bundled or hub)

How to Test

  1. Setup Whatsapp Gateway
  2. Add hermes to a group with unauthenticated users
  3. Add group to WHATSAPP_GROUP_ALLOWED_USERS
  4. Test if hermes responds to unauthenticated users in the group
  5. Test that unauthenticated users from the group cannot DM hermes

Checklist

Code

  • I've read the Contributing Guide
  • My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
  • I searched for existing PRs to make sure this isn't a duplicate
  • My PR contains only changes related to this fix/feature (no unrelated commits)
  • I've run pytest tests/ -q and all tests pass
  • I've added tests for my changes (required for bug fixes, strongly encouraged for features)
  • I've tested on my platform:

Documentation & Housekeeping

  • I've updated relevant documentation (README, docs/, docstrings) — or N/A
  • I've updated cli-config.yaml.example if I added/changed config keys — or N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
  • I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
  • I've updated tool descriptions/schemas if I changed tool behavior — or N/A

@RiptideV RiptideV force-pushed the add-whatsapp-group-allowed-users branch 2 times, most recently from 56ed914 to a6ebe4e Compare April 12, 2026 09:27
@RiptideV RiptideV force-pushed the add-whatsapp-group-allowed-users branch from a6ebe4e to aa4215f Compare April 12, 2026 22:02
@RiptideV RiptideV marked this pull request as ready for review April 12, 2026 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant