Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Version: OpenClaw 2026.4.26 (be8c246), Paperclip latest (rev 3494e84)

Paperclip now injects a paperclip property into the root of the agent invocation payload when invoking agents via the openclaw_gateway adapter. The gateway rejects it with:

invalid agent params: at root: unexpected property 'paperclip'
AgentParamsSchema in protocol-Hjar_s3V.js has additionalProperties: false — any unknown field fails validation.

Temp workaround: Manually added paperclip: Type.Optional(Type.Unknown()) to AgentParamsSchema in the installed bundle.

Fix needed: Add paperclip: Type.Optional(Type.Unknown()) to AgentParamsSchema upstream, or switch to passing Paperclip run context via the existing extraSystemPrompt/inputProvenance fields.

Steps to reproduce

Self-host Paperclip (latest) — ghcr.io/paperclipai/paperclip:latest
2. Register an agent with adapterType: openclaw_gateway, pointing to an OpenClaw 2026.4.26 gateway
3. Approve the device pairing in OpenClaw
4. Assign a task to the agent in Paperclip so it triggers an invocation
5. Gateway rejects the connection — error in journalctl:

[ws] ⇄ res ✗ agent 0ms errorCode=INVALID_REQUEST errorMessage=invalid agent params: at root: unexpected property 'paperclip'

Expected behavior

Expected: Agent receives the task and processes it

Actual behavior

Actual: Gateway rejects payload, agent stays in error status, task never executes

OpenClaw version

2026.4.26 (be8c246)

Operating system

Docker

Install method

docker

Model

Claude Sonnet 4.6

Provider / routing chain

paperclip --> openclaw gateway

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response