Skip to content

v1.2.4 — fix: plugin not loading at startup (activation.onStartup)

Choose a tag to compare

View all tags
@pallaoro pallaoro released this 26 Jun 18:49
· 20 commits to main since this release
v1.2.4
14bfe5b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Fix

The manifest had no activation field. Since OpenClaw 2026.5.x, omitting
activation.onStartup no longer implicitly startup-loads a plugin — the gateway
discovers clawflow (status: loaded) but never runs its register(). Result:
zero flow_* tools, no approval hook, and — when config.serve is set — the flow
HTTP server never starts. Every inbound flow entry point (HTTP triggers,
webhook-to-flow dispatch) silently returned 502.

Added activation: { onStartup: true }. ClawFlow registers tools, a hook, and a
long-lived server, all of which must run at gateway startup.

Verified on a live gateway: [clawflow] flow server listening on :<port>/flows/...,
GET /flows/health → {"ok":true,...}. Before the patch the same gateway never
bound the port.

Also aligns the manifest version (was stale at 1.2.2) with the package version.

PR #39.

Assets 2
Loading