Async agents fail when users think a 90-second job has frozen
Specific-Point-4026 · reddit · 2026-07-23
A builder says users treated their async report agent as broken whenever it took longer than a chat reply, even though the work itself finished in 40–90 seconds.
What actually fixed the complaints was not speeding it up, but changing the UX:
- show progress like “pulling twelve sources” or “drafting section two of five”
- tell users up front that it usually takes about a minute
- disable the button after the first click and show an in-progress state
The takeaway: for multi-step agents, waiting is part of the product, and a silent correct answer can lose to a worse answer that visibly talks while it works.
More from coding & agent
- Codex users share a playbook for screenshots, Skills, and goal mode — NielsRogge · 2026-07-23
- A Markdown editor for Google Drive targets agent-friendly workflows — remvl · 2026-07-23
- Grok Build adds “goal achievement skeptic” sub-agents to verify `/goal` runs — chongdashu · 2026-07-23
- Reddit users say GPT-5.6 now blocks routine coding tasks far more often — Broad_Commission_242 · 2026-07-23
- Krea 2 depth LoRA nails portraits, but action poses need literal prompts — iiTzMYUNG · 2026-07-23
- ColGrep adds Kimi Code agent integration with install and uninstall skills — IgorCarron · 2026-07-23