This was a major behavioral shift. Instead of treating every request for user input as a blocker inside the execution engine, Kindship now gives agents a dedicated way to reach out, keep moving, and pick the thread back up later.
Agents Can Reach Out Without Stalling Everything
The new user-messaging model is much closer to how real collaboration feels.
- Agents can send questions, choices, approvals, and reports through a dedicated async channel
- Those asks no longer have to freeze the whole execution flow
- Agents can keep working and come back for your answer on a later heartbeat
Web And Telegram Replies Became Real Interaction Surfaces
This is not just a backend concept. The user-facing reply paths became first-class too.
- Pending asks surface in the workspace as actionable inbox cards
- Telegram picked up inline buttons and stronger reply handling
- Responding feels more native to the channel you are already in, rather than like a workaround bolted onto a planning engine
Agents Became Better At Noticing Answers
A messaging system only matters if the agent actually pays attention when you reply.
- Heartbeat guidance now emphasizes checking answered messages early
- Answer handling is framed more clearly around the agent's own agencies and responsibilities
- The overall result is a more believable async loop, where agents ask, you answer, and the answer is less likely to vanish into silence