copy prompt to claude
The real work is everything that makes the conversation feel human. Why we're building ACI, and why we're doing it in the open source
The missing agent-user layer
ACI
Agent Communication Infrastructure
Defining the missing agent-to-user communication layer — and the best-practices that come with it. One layer between every app, every channel, and every smart agent.
Or to Claude
Notifications
For decades, products notifed users one way via notifications, that always lacked the correct context, and limited users' ability to perform meaningful interactions with them. Software has changed, now it needs to communicate via conversations.
Stop re-inventing the wheel
Instead of focusing on building the most capable and intelligent agent, teams spend months to wire and establish communication patterns that have nothing to do with their core value.
5+
channels to build
and maintain
0%
of this plumbing
makes your agent smarter
100%
undifferentiated heavy
lifting
NounInfrastructure/ˈe. si. a/
ACI — Agent Communication Infrastructure
The infrastructure layer between an autonomous agent and the channels where humans actually receive messages. The third leg of the agent triad, alongside MCP and A2A.
MCP:AgentTools
How the agent thinks with the world.
A2A:AgentAgent
How agents coordinate with each other.
ACI:AgentPeople
How the agent reaches the people who care.
How it works
You own the brain. ACI owns the communication.
Three columns, one seam. Channels feed ACI, ACI hands a single conversation to your agent, your agent replies on the thread of origin.
Communication providers — where humans actually are.
Slack, WhatsApp, Teams, Telegram, Email — and every long-tail channel behind a single adapter, normalized to one message shape.
Agent bridge (ACI) — the only piece we run.
Stateful, idempotent, traced end-to-end. One brain answering on Slack also answers on Teams, WhatsApp, and Email.
Agent Brain — stays on your side.
Bring your own — Agent SDK, LangChain, a managed Claude agent, or your own server. ACI never sees your prompts, memory, or model.
One command and connect your agent to your customers.
Run it in your terminal or hand the prompt to Claude and let it wire up the SDK for you. Either way, no plumbing to own.
npx novu connectOpinionated about communication infrastructure.
Unopinionated about intelligence.
We solve the delivery problem so you can own the capability problem.
ACI Handles:
- Webhook ingestion
- Cross-channel message normalization
- Exact thread delivery
- Conversation persistence & state
- Participants identity resolution
- Agent communication experience
You Keep:
- Your model
- Your prompts
- Your tools
- Your business logic
- Your keys
- Your runtime & your code
We've been the notification layer for half a decade.
Channels, identity, and delivery — we built the infrastructure so you don't have to. ACI brings it to agents. Hear from the founders.
- 39,8k
- Stars on GitHub
- 412B+
- Messages a month
- 12
- Channels
- 6
- Regions
Built in the open. Send a PR, file an issue, ship a channel.
ACI are open source. Contribute what missing, review the code, run it by yourself. The adapters, the identity resolver, the conversation store — all on GitHub. If there's a channel we don't speak yet, you can teach us.
For decades, software waited.It opened when you opened it.
Agents don't wait.
They reach out , they follow up , they live where you live .
MCP connects agents to tools.A2A connects agents to each other.
ACI connects agents to people.Novu Connect is the ACI layer.
Frequently asked questions
Give your agent a voice everywhere your users are
Build the agent once. ACI handles the rest.