Sup HN! Dipanshu and Rushant here from Caspian. One is a functional programmer and the other has been deploying AI employees. Together we realized how agents have communication bottleneck.Given the coming agentic economy, we had a thought experiment on what can be the key infrastructure for agents as they get better. Our inspiration for solving for communications infra came from our own time spent just setting up comms while we were deploying open claw for companies plus we noticed about 15%+ of issues in openclaw and hermes were that of comms.So we abstracted the headache of reliable communication web-hooks, handling of queues, provision and identity management behind an single SDK integration / tool call. Think of it like rather than rolling your own auth, you can use better auth sdk, same thesis here.Technically, we designed the SDK from the ground up as a DSL for communications (heavy inspiration from functional programming ) and then add on our own run time environment which auto provisions ( this is how we plan on monetizing ) else the user can always bring his own tokens. We targeted right now for python and typescript.We noticed that the current space is fragmented into single identity provisioning ( like agent mail ), tool calling like composio and non agentic support provisioning like twillo. We believe all these are under the same issue of solving communication which we do in a open source SDK first manner.A few things we d like the community s take on: How drastic does working with agents change for you, depending on what channel you interact with it on ? What features would make you use caspian for your agents ?