f33dc13af4
Root cause: PluginHookAgentContext in before_model_resolve only has agentId, sessionKey, sessionId, workspaceDir, messageProvider. senderId, channelId, input are NOT available in this hook phase. The plugin was reading ctx.senderId (undefined) -> inHumanList=false for ALL Discord sessions -> shouldUseNoReply=true -> all silenced. Fix: use event.prompt which contains the full user message including the 'Conversation info (untrusted metadata)' JSON block, and extract sender_id from there. Same fix applied to before_prompt_build.
WhisperGate
Rule-based no-reply gate for OpenClaw.
What it does
WhisperGate adds a deterministic gate before model selection:
- If message is not from Discord → skip gate
- If sender is in bypass user list → skip gate
- If message ends with configured end-symbol → skip gate
- Otherwise switch this turn to a no-reply model/provider
The no-reply provider returns NO_REPLY for any input.
Repo layout
plugin/— OpenClaw plugin (before_model_resolve hook)no-reply-api/— OpenAI-compatible minimal API that always returnsNO_REPLYdiscord-control-api/— Discord 管理扩展 API（私密频道 + 成员列表）docs/— rollout, integration, run-mode notesscripts/— smoke/dev/helper checksMakefile— common dev commands (make check,make check-rules,make test-api,make smoke-discord-control,make up)CHANGELOG.md— milestone summary
Quick start (no Docker)
cd no-reply-api
node server.mjs
Then render config snippet:
node scripts/render-openclaw-config.mjs
See docs/RUN_MODES.md for Docker mode.
Discord 扩展能力见：docs/DISCORD_CONTROL.md。
Development plan (incremental commits)
- Task 1: project docs + structure
- Task 2: no-reply API MVP
- Task 3: plugin MVP with rule chain
- Task 4: sample config + quick verification scripts
- Task 5: plugin rule extraction + hardening
- Task 6: containerization + compose
- Task 7: plugin usage notes
- Task 8: sender normalization + TTL + one-shot decision
- Task 9: auth-aware no-reply API
- Task 10: smoke test helpers
- Task 11: plugin structure checker
- Task 12: rollout checklist