Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Nicell
Copy link

@Nicell Nicell commented Jan 22, 2026

Summary

Fixes typing indicators not being stopped when:

  • Agent goes idle after processing
  • Agent replies with NO_REPLY

Background

The typing stop was previously disabled because BlueBubbles Server had a bug where the DELETE /typing endpoint called startTyping() instead of stopTyping(). That bug has been fixed (PR pending in BlueBubbles Server), so we can now properly stop typing indicators.

Changes

  • onIdle: now calls sendBlueBubblesTyping(false) to stop typing
  • finally block: stops typing when no message was sent (NO_REPLY case)

Related

@Nicell
Copy link
Author

Nicell commented Jan 22, 2026

Upstream PR was merged to blue bubbles. Doesn't hurt to merge this now, will start working once the new bb server is released/adopted. Without the new server these calls do the opposite of what they're supposed to do, but they don't hurt.

Clawd and others added 2 commits January 22, 2026 21:20
Previously, typing stop was intentionally skipped because the
BlueBubbles Server DELETE endpoint was bugged (called startTyping
instead of stopTyping). Now that the server bug is fixed, we can
properly stop typing indicators.

- onIdle: now calls sendBlueBubblesTyping(false) to stop typing
- finally block: stops typing when no message sent (NO_REPLY case)
@steipete steipete force-pushed the fix/bluebubbles-typing-stop branch from 095e3fc to 3993c9a Compare January 22, 2026 21:33
@steipete steipete merged commit 534f28a into openclaw:main Jan 22, 2026
@steipete
Copy link
Contributor

Landed via temp rebase onto main.

  • Gate: pnpm lint && pnpm build && pnpm test
  • Land commit: 3993c9a
  • Merge commit: 534f28a

Thanks @Nicell!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants