AIToday
Large Language ModelsZenn AI/MLPublished: Oct 20, 2026, 10:00 JST

HACH developer: slow AI agents need instant ack, not silence

HACH developer: slow AI agents need instant ack, not silence

3 Key Points

  1. What happened

    The developer of HACH, an AI agent resident in Slack, Teams, Chatwork and LINE WORKS, laid out three patterns for handling requests that take tens of seconds to minutes. The first is a fixed, non-LLM acknowledgement sent the moment a request arrives.

  2. Why it matters

    Without that signal, users who see a read receipt but no reply resend the same request on another channel, which the developer says can double the work or produce two conflicting answers. Progress updates should follow time thresholds, not fixed intervals.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The piece is written from the operator's side of the desk rather than the model's. Its starting observation is that a colleague who needs time says "let me check" before going quiet, while an agent that processes silently leaves the user staring at a read receipt. That gap, the developer argues, is what triggers the familiar behaviour of asking the same question again by email five minutes later.

The three patterns build on each other. The immediate acknowledgement exists to close that gap, but it is deliberately kept free of any promise about the outcome, so a later "actually, I can't do this" does not contradict it. The threshold table then replaces a fixed-interval heartbeat, on the reasoning that repeated identical "working on it" messages look as careless as silence. The final pattern, ranged estimates, is framed as a trust issue: a single missed "done in 30 seconds" calls the agent's credibility into question, so a range — or no number at all when there is no basis for one — is the safer choice.

The developer places this alongside notification design and confidence-based behaviour switching as operational concerns for HACH, which collects chat, email, calendar and meeting notes and delivers a morning report. The implication, hedged, is that for agents doing multi-step work, how the wait is narrated may matter as much as the answer itself.

FAQ
Why not just have the AI write the acknowledgement message?
Because generating it through the LLM adds inference time to the very moment that is supposed to be instant. The developer recommends fixed wording or a fixed reaction, handled as a fixed process rather than generated.
How often should an agent post progress updates?
Not on a fixed interval. The developer proposes thresholds — nothing for up to 5 seconds, a reaction from 5 to 30 seconds, a "a little more time" message with current activity from 30 seconds to 2 minutes, and an overrun notice beyond 2 minutes — and only when the update carries new information.
What should an agent say when it blows past its estimate?
Say so once instead of continuing silently. Even without explaining the cause, "it's taking longer than expected" is enough, according to the developer.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleScience editor's "Slower, worse" AI piece used ChatGPT, essay says