Agent Kourier is a Kubernetes-native broker that carries alerts and Slack messages to any A2A agent, including one that is suspended until it is called, and brings its findings back into the Slack thread where people can keep the session going.
-
Try it
Run Agent Kourier in a kind cluster against your own Slack workspace and a read-only kagent agent, and get your first answer in a thread.
-
Install
Install the Helm chart on a cluster you already run, connect Slack, and bind your first agent to a channel.
-
How it works
One broker between the chat, the alerts and your agents: a thread is a session, a restart loses no message, and two replicas on Postgres fail over without losing one.
A thread is a session¶
An alert lands in the channel. Agent Kourier opens a thread under it and hands it to the agent, which investigates and answers there. People reply in the same thread and the same agent session continues.
An illustration of one alert thread, not captured output. The answers come from your agent; Agent Kourier carries them.
A repeat of the same alert attaches to its thread, and its resolve posts a note there. Agent Kourier reads the alert your alerting tool already posts to Slack, so your alerts arrive as before, whether or not Agent Kourier is running. Alertmanager has a ready-made preset; another tool's bot needs a trigger of its own.
Chat
SlackAgents
A2A kagent Google AXAlerts
Alertmanager preset any bot's message