DotCraft SDK
DotCraft SDKs are for external clients, social channel adapters, and automation integrations. They connect to the same AppServer Wire Protocol and reuse DotCraft's thread, streaming event, approval, and delivery capabilities.
Quick Start
- Read the AppServer Mode Guide first and decide between stdio and WebSocket.
- Choose Python SDK for standalone adapters.
- Choose TypeScript SDK for social channel modules.
- Start from the closest platform example, then replace tokens, callback URLs, and permission allowlists.
Configuration
| Goal | Docs |
|---|---|
| Build external channel adapters in Python | Python SDK |
| Reference the Telegram Python adapter | Python Telegram Adapter |
| Build external channel modules in TypeScript | TypeScript SDK |
| Connect Feishu / Lark | Feishu Adapter |
| Connect Telegram | Telegram Adapter |
| Connect Weixin | Weixin Adapter |
| Connect QQ | QQ Adapter |
| Connect WeCom | WeCom Adapter |
Usage Examples
| Scenario | Recommended entry |
|---|---|
| Build a Python bot | Python SDK + Telegram Adapter |
| Build a TypeScript social channel | TypeScript SDK |
| Connect to an existing AppServer | Use WebSocket transport |
| Let DotCraft host the adapter subprocess | Use stdio / subprocess mode |
Advanced Topics
Troubleshooting
Adapter cannot connect to DotCraft
Confirm AppServer is running in WebSocket mode, the URL includes /ws, and the token matches the client config.
Messages arrive but results cannot be delivered
Check whether the adapter declares delivery capabilities and channel tools during initialization. Platform tokens, callback URLs, and permission allowlists must also match.
You are not sure whether to choose Python or TypeScript
Choose Python for quick standalone adapters. Choose TypeScript when reusing existing channel modules, interactive setup, or platform packages.