#Bug: unexpected property 'paperclip' still thrown in 4.22 gateway binary

1 messages · Page 1 of 1 (latest)

cyan rune
#

invalid agent params: at root: unexpected property 'paperclip'

The fix appears to be in the JS dist files but NOT compiled into the gateway binary. Every Paperclip heartbeat run fails instantly.

Steps to reproduce:

  1. Install Paperclip 2026.416.0
  2. Create an agent with OpenClaw gateway connection
  3. Trigger a heartbeat run
  4. See openclaw_gateway_request_failed in the run log

Is there a 4.23 with this fix compiled into the binary, or a workaround?

gritty novaBOT
nimble lanceBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

gritty novaBOT
vernal heraldBOT
#

Yeah, I checked this.

Short version:

  • No stable 2026.4.23 yet. npm latest is still 2026.4.22.
  • There is a beta: 2026.4.23-beta.3.
  • But I would not expect that beta to fix this exact error.

Why: the fix I found in OpenClaw is for WakeParams allowing unknown fields. Your error is:

  • invalid agent params: at root: unexpected property 'paperclip'

That comes from the agent path, and AgentParamsSchema is still strict in source, while only WakeParamsSchema was relaxed.

So this looks less like “fix exists but wasn’t compiled into the binary”, and more like Paperclip is hitting a different schema path during heartbeat runs.

Workaround right now

#

Best workaround is on the Paperclip side:

  • stop sending root-level paperclip inside agentParams
  • put that metadata into the message/wake text, or another supported field

Paperclip’s own issue says they fixed it that way in PR 626:

So if 2026.416.0 still fails for you, I’d try:

  1. a newer Paperclip build than that, if available
  2. or patch Paperclip locally to remove the root paperclip field for OpenClaw agent calls

If you want to test beta

You can try 2026.4.23-beta.3, but again, I’m skeptical it fixes the agent validation path specifically.

For general triage/update refs:

cyan rune
#

Here's the payload details. Should this paperclip metadata move into the message text string or another supported field?

{
"message": "Paperclip wake event...",
"sessionKey": "paperclip",
"idempotencyKey": "947e256c-0650-4458-807c-feafb90e089c",
"paperclip": {
"runId": "947e256c-0650-4458-807c-feafb90e089c",
"companyId": "2a137710-2f18-4cf7-9849-d32d18670d9a",
"agentId": "00b07df8-858a-4a93-af50-c6bf75a16acb",
"agentName": "Flux",
"taskId": null,
"issueId": null,
"workspace": { ... },
"timeout": 120000
}
}

cyan rune
#

@vernal herald any insight on this one by chance?