caspian-sdk

TryCaspian/caspian-sdk is ranked 12,291 among these 8 peers; banodoco/Steerable-Motion is ranked 12,293.

Most agent communication work is agent-to-human, not agent-to-agent. Protocols like A2A and ACP connect agents to each other; Caspian connects your agent to the people it works for, on the channels they already use. The public surface is (not the legacy from 0. Get started in 30 seconds **Building in a coding agent** (Claude Code, Codex, Cursor, Kimi, …)? **Or set it up by hand:** Get an API key from dashboard. CLI The rewrite CLI lives in

(TypeScript + Bun). Delete your adapter layer Without Caspian With Caspian **Using a coding agent? You own infrastructure you never wanted. ** Writing the Slack bot is a weekend; owning it is forever. Session/auth desync, reconnect loops, silent connection failures, payload changes on every platform version bump. The largest OSS agent frameworks each maintain 25+ channel adapters in-tree and still spend 8–15% of their issue trackers on channel plumbing. (We measured 42 open-source agent projects before writing a

line of this code. Communication isn't part of your agent's decision-making. ** With one-off, per-channel integrations, a developer decided at build time where and how the agent talks. Communication stays hardcoded plumbing instead of becoming a capability the model can actually decide with. You maintain N identities for every one person. ** The same human DMs your agent on Instagram today and emails it tomorrow. Every team rebuilds that continuity layer from scratch, per app, and it never stops

needing care. A single-channel agent is a competitive disadvantage. ** If a competing agent is reachable on five channels and yours on one, users go where they get answered. Caspian's answer **Channels are transports, not identities. ** The agent is one program ( is inspectable data); every channel binds through the same adapter interface, and your handler code works against a normalized / model. Messages arrive as kernel events regardless of transport, overlap policies ( / / / ) serialize concurrent chats, and / always answer in the right

place. runs adapters in your process with your platform tokens. Switch modes without rewriting handlers. Your bot is data: is inspectable and testable offline. **🔐 Webhook verification, always** Slack signing secret, Meta , Telegram secret header, X CRC, and signed email webhooks. **☁️ Hosted or self-host** Gateway polling with , or bring your own tokens and webhooks/sockets with . **⌨️ Typing, streaming, rich sends** , (post once, edit as it writes), , , reactions, pins, forwards, and cold DMs. **🔌 Per-channel packs (TypeScript)** Import , , , and the rest

for parse/plan/execute without pulling the whole facade. Channels Self-host adapters ship in the SDK for the channels below. Hosted mode covers any channel the gateway supports (including Bluesky, Instagram, and channels with no local adapter). **GSM modem SMS**: your own modem + SIM; carrier compliance (A2P rules) is on you. | | | One self-host example per adapter; for hosted Telegram. | Package READMEs have the full API surface: , . It remains published on PyPI/npm; its source is tagged in this

repository. **If Caspian saved you time, a star helps other agent builders find it.