Connector Development

Design guidance for new platform bridges and client adapters.

A connector turns platform-specific events into DragonClaw messages.

It should stay thin. Let the gateway and agent loop handle the heavy lifting.

Connector responsibilities

• Receive messages from the source platform

• Map them into content, channelId, and userId

• Send them through the gateway or internal runtime interface

• Return final responses to the source platform

Design rules

• Keep secrets server-side

• Reuse gateway auth and rate limiting

• Preserve stable channel identity

• Do not duplicate memory logic in the connector

• Handle retries and platform errors gracefully