CHANGELOG

What Shipped This Week: Chat That Actually Finishes

You ask your Research specialist for a competitor summary at 7:15am. The duty already ran — you just need the answer in chat. Before this week, that message could land as an empty bubble, a false "AI is down" banner, or nothing at all if we deployed while the turn was still open. Now the reply finishes, persists, and survives a deploy.

6–8 min read

Three things landed together: chat turns no longer die mid-stream or save as blank bubbles, helper work shows as a compact status line instead of flooding your thread, and Growth/Pro/Max list prices went live at $29/$59/$199 on 1 September.

Chat turns no longer vanish into blank bubbles or false "AI is down" errors

Before this week, three failure modes could make a specialist look broken when it was not. You would send a message, see the thinking indicator, and then get an empty assistant bubble — or a banner claiming the AI provider was down when the real problem was our side losing the draft. Worse: if we shipped a deploy while your turn was still streaming, the connection dropped and the partial answer never saved. You had to re-ask. On a phone between meetings, that is not a minor annoyance — it is the difference between trusting the agent and opening a laptop to check whether the duty actually ran.

We fixed the full chain. The parent draft now persists before helper work starts, pins to your user turn, and we never store an empty assistant bubble. OpenClaw no longer runs a second moderation pass on continuation blobs unless you explicitly opt in — that double-check was silently killing valid replies. When a deploy rolls out, a 30-second drain waits for in-flight chat turns to finish instead of cutting them off; if a turn cannot complete, we write an interrupt flag so you see what happened instead of silence.

Why this matters in the context of how CloudAxis works: specialists run on a persistent cloud computer with scheduled duties and multi-agent handoffs. Chat is how you steer them between runs — approve a report, redirect a scan, ask Cloudia to add a duty. If chat feels unreliable, the whole OS feels unreliable, even when the overnight duty wrote the file correctly to ~/files/. We wrote about agents that keep working while you sleep in our always-on agents guide; this week we made the check-in loop match that promise.

Edge case we closed: custom employees hired with an empty skills override now get search and files tools again, so a misconfigured hire does not look like a dead specialist. Summarizer calls on GPT-5.6 Luna use max_completion_tokens so long helper rounds do not truncate mid-sentence. If the model never starts talking, we silently re-kick the stream instead of leaving you staring at a frozen composer.

Also shipped

Smaller changes that landed in the same window:

What's next

We are watching chat completion rates and deploy-interrupt frequency this week. If you still see a blank bubble after a deploy, tell us which specialist and thread — the new interrupt flag should make those reports actionable.

Frequently asked questions

Do I need to refresh after a deploy?

No. In-flight turns now get a 30-second drain window. If your turn was interrupted, you will see an explicit message — not a blank bubble.

Did helper behavior change?

Yes. Helpers still run behind Cloudia, but their progress is a compact chip instead of flooding the thread. Stop works mid-helper and Send is available for your next message immediately after.

Related reading in this series
Hiring specialist agents · September 2026 pricing announcement · Scheduling agents 24/7