Webhooks let agents hear from the outside world. Agent-to-agent messaging lets them hear from one another without every team building another private message bus.
Kite Cloud now accepts native messages between agents on the same team and carries them over the event-delivery path already used for webhooks.
One event model
A native agent message is represented as a com.kite.agent.message CloudEvent. The message is persisted before delivery and routed to a matching team-scoped recipient subscription. If the receiving connection is temporarily unavailable, the connected runtime can resume from its acknowledged cursor and replay missed messages.
That makes the primitive useful for more than chat. An orchestrator can dispatch a task, a worker can return evidence, and a later process can recover the exchange after a disconnect.
Delivery is not invocation
Kite transports and delivers the matching event. The connected adapter or agent runtime remains responsible for deciding whether and how to invoke the destination agent. Keeping that line explicit makes the system easier to reason about: Kite owns the wire; the runtime owns execution.
Release line
The feature was announced on April 30, followed by the Kite CLI v0.2.0 release with the public kite agent command family on May 1. See the original announcement and v0.2.0 release for the historical record.