openclaw - 💡(How to fix) Fix Paperclip Gateway adapter sends unsupported 'paperclip' field in agent params [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62102Fetched 2026-04-08 03:08:59
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

Error Message

``` [openclaw-gateway] request failed: invalid agent params: at root: unexpected property 'paperclip' stderrExcerpt: [openclaw-gateway] request failed: invalid agent params: at root: unexpected property 'paperclip' errorCode: openclaw_gateway_request_failed ```

Root Cause

The OpenClaw Gateway's AgentParamsSchema has additionalProperties: false and does not include a paperclip field. Paperclip adapter sends this field with context about the run (runId, companyId, agentId, issueId, workspace, etc.).

Code Example

invalid agent params: at root: unexpected property 'paperclip'
RAW_BUFFERClick to expand / collapse

Bug Description

When using Paperclip's openclaw_gateway adapter to connect to OpenClaw Gateway, the agent execution fails with:

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

Root Cause

The OpenClaw Gateway's AgentParamsSchema has additionalProperties: false and does not include a paperclip field. Paperclip adapter sends this field with context about the run (runId, companyId, agentId, issueId, workspace, etc.).

Environment

  • OpenClaw Gateway: 2026.4.5
  • Paperclip: 2026.403.0 (latest)
  • Paperclip adapter type: openclaw_gateway

Paperclip Payload (truncated)

```json { "message": "Paperclip wake event...", "sessionKey": "paperclip:run:<runId>", "idempotencyKey": "<runId>", "paperclip": { "runId": "<runId>", "companyId": "<companyId>", "agentId": "<agentId>", "agentName": "CEO", "taskId": null, "issueId": null, "apiUrl": "http://127.0.0.1:3100", "workspace": { ... } }, "timeout": 120000 } ```

Expected

Either:

  1. OpenClaw accepts the paperclip field as an optional extra field, OR
  2. Paperclip sends this context differently (e.g., in metadata or runtimeConfig)

Impact

This prevents Paperclip agents from executing any tasks via OpenClaw Gateway. The adapter connects successfully via WebSocket but the request is rejected at the gateway layer.

Logs

``` [openclaw-gateway] request failed: invalid agent params: at root: unexpected property 'paperclip' stderrExcerpt: [openclaw-gateway] request failed: invalid agent params: at root: unexpected property 'paperclip' errorCode: openclaw_gateway_request_failed ```

extent analysis

TL;DR

Modify the Paperclip adapter to exclude the 'paperclip' field from the payload or update the OpenClaw Gateway's AgentParamsSchema to include the 'paperclip' field as an optional property.

Guidance

  • Verify the OpenClaw Gateway's AgentParamsSchema to confirm that it does not include a 'paperclip' field and that additionalProperties is set to false.
  • Consider modifying the Paperclip adapter to send the context information in a different field, such as metadata or runtimeConfig, if possible.
  • If updating the OpenClaw Gateway's schema is feasible, add the 'paperclip' field as an optional property to allow the gateway to accept the current payload.
  • Test the modified adapter or updated schema to ensure that the agent execution succeeds and the 'paperclip' field is properly handled.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a modification to the adapter or schema configuration.

Notes

The solution may require coordination between the Paperclip and OpenClaw Gateway teams to determine the best approach for modifying the adapter or updating the schema.

Recommendation

Apply a workaround by modifying the Paperclip adapter to exclude the 'paperclip' field from the payload, as this is likely a more feasible short-term solution than updating the OpenClaw Gateway's schema.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Paperclip Gateway adapter sends unsupported 'paperclip' field in agent params [1 participants]