Skip to content

Native hook relay intermittently becomes unavailable on 2026.5.26, blocking memory/filesystem tools #87395

Description

@OhBoyPrintshop

Summary

After updating to OpenClaw 2026.5.26 (10ad3aa) on macOS/darwin, the native hook relay intermittently becomes unavailable and blocks native tools before command execution. The symptom looks like a runtime/native hook relay failure rather than memory database corruption.

Environment

  • OpenClaw: 2026.5.26 (10ad3aa)
  • Platform: macOS / darwin
  • Affected area: native shell/filesystem tool execution, memory file read/write checks, gh/native command usage

Symptoms

  • Native shell/filesystem commands intermittently fail before execution with:
Native hook relay unavailable
  • When this happens, memory file read/write checks are blocked because the native filesystem path cannot execute.
  • gh/native command usage is also blocked by the same pre-execution failure.
  • Browser-based GitHub navigation was blocked by policy in the parent session, so the issue could not be filed through the GitHub UI from that path.

Recovery/diagnostics observed

  • Restarting the gateway alone did not recover the native relay.
  • A full OpenClaw hard restart temporarily recovered native shell/filesystem access.
  • After the hard restart, current workspace memory reads/writes succeeded.
  • The failure recurred minutes later after the temporary recovery.
  • The memory database itself appears healthy when native hook execution works: sqlite PRAGMA integrity_check returned ok.
  • This suggests the durable memory store/files are not the primary failure point; the failure appears to be in the runtime/native hook relay path.

Request

Could maintainers help distinguish this from memory corruption and confirm whether this is a runtime/native hook relay regression in 2026.5.26?

Useful guidance would include:

  • Recommended diagnostics to capture when Native hook relay unavailable recurs.
  • Whether gateway logs, hook registry state, session generation IDs, or app-server state are most relevant.
  • A supported recovery path short of a full OpenClaw hard restart.
  • Whether this is related to recently closed native hook relay issues, or a separate recurrence involving memory/filesystem tool access.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions