OpenClaw plugins return tool results in one of two shapes:
(a) AgentToolResult — { content: [{type:'text', text:'...'}] }
used when the plugin wraps via asContent() helper. Every
Dialectic.OpenclawPlugin tool follows this pattern.
(b) raw JSON-able object — { ok:true, ...domain fields }
used when the plugin returns data directly. Every
Fabric.OpenclawPlugin tool follows this pattern
(fabric-channel-list, fabric-guild-list, fabric-send-message,
fabric-channel-set-purpose, etc).
The bridge's /mcp/execute handler only handled shape (a). When a
contractor agent (developer / contractor-test) called any fabric
tool through Claude Code, the bridge ran the tool successfully but
fell back to the literal string '(no result)' because
toolResult.content was undefined. Claude Code then dutifully
rendered '(no result)' as the tool result.
Reproduced on prod:
openclaw agent --agent developer -m 'Call fabric-channel-list ...'
→ claude code session called mcp__openclaw__fabric-channel-list
→ bridge logged: mcp/execute tool=fabric-channel-list ...
→ bridge replied: { result: '(no result)' }
→ claude code rendered: ''
Fix: normalize the result in the bridge. If toolResult is null →
empty string; if it has a .content array → join the text segments
(shape a); if it's a string → use directly; else → JSON.stringify
the whole thing (shape b). Falls back to '(no result)' only when
all of those produce empty string.
Verified on prod after fix:
agent receives real {"ok":true,"count":1,"channels":[...]}
JSON payload (one real prod-push-test channel) in the response.
hzhang
037e92b421