Hi
I just spent an entire day getting this wo work. Here is a hack that may help:

Issue
Paperclip was running correctly and OpenClaw was running correctly, but in the Paperclip UI the OpenClaw Gateway adapter appeared in Create your first agent under More Agent Adapter Types and was disabled/greyed out.

Environment

• macOS on Mac Studio
• Paperclip launched via:
  /opt/homebrew/bin/pnpm dlx [email protected] run
• OpenClaw version:
  2026.4.8
• Paperclip health endpoint working:
  http://127.0.0.1:3100

What was confirmed first

• openclaw_gateway was present in the Paperclip backend constants list.
• openclaw_gateway was present in the adapter registry.
• The OpenClaw adapter object existed in the compiled backend code.
• So this was not a missing backend adapter problem.

What turned out to be wrong

The disable was coming from the front-end bundle, not from the Paperclip backend.

In the served browser JavaScript bundle, the OpenClaw card was hard-coded like this:

• value:"openclaw_gateway"
• label:"OpenClaw Gateway"
• comingSoon:!0

The button logic also used:

• disabled:!!Ye.comingSoon

So the UI was intentionally marking the OpenClaw Gateway card as “coming soon”, which is why it was greyed out, even though the backend adapter already existed.

How the cause was found

1. Checked the backend compiled file and confirmed:

   • AGENT_ADAPTER_TYPES included openclaw_gateway
   • adaptersByType included openclawGatewayCLIAdapter

2. Checked the front-end JavaScript served by Paperclip:

   • http://127.0.0.1:3100/assets/index-brmnj7-N.js

3. Located the onboarding UI code for Create your first agent and found the OpenClaw entry marked as:

   • comingSoon:!0

Important detail

The actual front-end bundle was not in the main paperclipai/dist/assets folder.

The real file being served was here:

/Users/automation/Library/Caches/pnpm/dlx/67494a8ef36edecf53092ae9654e85a221cd3a41eadc4478bdbac3950c0410bb/19d6dc3b8bf-c66/node_modules/.pnpm/@paperclipai+server@2026.325.0_@noble[email protected][email protected][email protected][email protected]/node_modules/@paperclipai/server/ui-dist/assets/index-brmnj7-N.js

Fix applied

Patched the front-end bundle to remove the comingSoon flag from the OpenClaw Gateway card.

Original fragment:

{value:"openclaw_gateway",label:"OpenClaw Gateway",icon:oo,desc:"Invoke OpenClaw via gateway protocol",comingSoon:!0,disabledLabel:"Configure OpenClaw within the App"}

Replaced with:

{value:"openclaw_gateway",label:"OpenClaw Gateway",icon:oo,desc:"Invoke OpenClaw via gateway protocol"}

Patch method

• Took a backup of the served UI bundle
• Replaced the exact OpenClaw card object in the served front-end JavaScript
• Restarted Paperclip

Restart command

launchctl kickstart -k gui/$(id -u)/com.automation.paperclip

Result

After restarting Paperclip and refreshing the browser, the OpenClaw Gateway option was no longer disabled in the UI.

Root cause summary

This was a front-end gating issue:

• Backend adapter existed
• Front-end card was hard-coded as “coming soon”
• Removing that front-end flag made the option selectable

Caution

This is a local patch to the served Paperclip UI bundle inside the pnpm dlx cache. It may be overwritten by:

• a Paperclip update
• a fresh pnpm dlx cache rebuild
• reinstalling Paperclip

So this is a workaround, not a permanent upstream fix.

It seems that some things have changed, at least on the version v0.3.1.

To enable the Openclaw Gateway option, you have to modify the file paperclip/ui/src/adapters/adapter-display-registry.ts:

  openclaw_gateway: {
    label: "OpenClaw Gateway",
    description: "Invoke OpenClaw via gateway protocol",
    icon: Bot,
    // comingSoon: true,
    // disabledLabel: "Configure OpenClaw within the App",
  },

This enables that option but it seems that paperclip has a problem to show the fields of this adapter as well any other external adapter, with these files with issues:

• ui/src/adapters/schema-config-fields.tsx
• ui/src/components/AgentConfigForm.tsx