Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

On stock OpenClaw 2026.3.24, shared hook runs can still inject fallback Hook ... system events into the main session when the hook lane was intended to stay silent.

Steps to reproduce

1. Run stock OpenClaw 2026.3.24 with hooks enabled and a mapped shared agent hook.
2. Trigger hook traffic that the isolated hook lane handles as silent / no-change.
3. Observe the main session receives fallback hook text instead of staying silent.

Expected behavior

Silent or already-handled shared hook outcomes should not inject fallback Hook ... system events into the main session or trigger fallback wake behavior.

Actual behavior

The main session receives fallback hook/system-event text such as:

• Hook Hook: ok
• substantive hook summaries
• silent-path narration including NO_REPLY

OpenClaw version

2026.3.24 (cff6dc9)

Operating system

Ubuntu 24.04.4 LTS (Linux 6.8.0-106-generic x86_64)

Install method

pnpm global

Model

GLM-4.7 and gpt-5.4-mini were observed live; the issue appears to be in shared hook fallback logic rather than model-specific behavior.

Provider / routing chain

openclaw on Hetzner -> hook-triggered shared agent path -> GLM-4.7 / gpt-5.4-mini

Additional provider/model setup details

Observed on a Hetzner-hosted OpenClaw gateway with live hook traffic using GLM-4.7 and gpt-5.4-mini. Separate targeted hook-seam tests were also run in a local source clone and were model-independent.

Logs, screenshots, and evidence

Observed main-session events included:
- `System: [2026-03-26 03:50:05 EDT] Hook Hook: ok`
- `System: [2026-03-26 04:51:42 EDT] Hook Hook: I'll update the current-truth file for perl-lsp with this PR review status.`
- `System: [2026-03-26 04:59:29 EDT] Hook Hook: Updated current/projects.md for PR #2958 with Codex review notification. NO_REPLY`
- `System: [2026-03-26 09:21:16 EDT] Hook Hook: ... Skipping writeback ... NO_REPLY`

Impact and severity

Affected: hook-driven automations using the shared hook path, including silent Gmail-style triage
Severity: Low to medium (pollutes the main session and can surface internal hook work into the wrong surface)
Frequency: Observed repeatedly on live traffic in one session window
Consequence: silent/no-change hook work leaks into the main thread and can create noise or displace useful context

Additional information

Related:

• fix(hooks): duplicate delivery when hook agent turn uses announce flow #20196
• SILENT_REPLY_TOKEN path does not set delivered:true — NO_REPLY hooks pollute main agent session #21343
• fix(hooks): suppress main session events for silent/delivered hook turns #20678
• Hook deliver: false still injects system event into main session #36325

This appears broader than the already-open deliver:false slice in #36325: current shared-hook fallback is still inferred from !result.delivered.