openclaw - 💡(How to fix) Fix [Feature Request] Typing Indicator for Nextcloud Talk Channel [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70032Fetched 2026-04-23 07:30:09
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×1subscribed ×1

Add support for the Nextcloud Talk "typing indicator" (Schreibindikator) API endpoint to improve UX when OpenClaw is processing messages.

Root Cause

Add support for the Nextcloud Talk "typing indicator" (Schreibindikator) API endpoint to improve UX when OpenClaw is processing messages.

Fix Action

Fix / Workaround

  1. Trigger typing=true when:
    • Message is received and validated
    • BEFORE any tool calls or processing begins
    • Immediately after dispatchInboundReplyWithBase is called
  2. Trigger typing=false when:
    • Reply is sent successfully
    • OR after a timeout (e.g., 30 seconds) as fallback
    • OR if processing fails/errors out

Code Example

POST /ocs/v2.php/apps/spreed/api/v1/chat/{token}/typing

---

{
  "typing": true
}

---

{
  "typing": false
}

---

User sends message
[Show typing indicator]
OpenClaw processes (thinking, tools, etc.)
[Hide typing indicator]
Reply delivered to chat

---

{
  "channels": {
    "nextcloud-talk": {
      "typingIndicator": true  // default: false for backward compatibility
    }
  }
}
RAW_BUFFERClick to expand / collapse

Summary

Summary

Add support for the Nextcloud Talk "typing indicator" (Schreibindikator) API endpoint to improve UX when OpenClaw is processing messages.

Problem to solve

Motivation / Use Case

When OpenClaw receives a message in Nextcloud Talk and needs time to process (e.g., searching logs, analyzing files, or with Thinking Level > 0), users currently see no visual feedback. They don't know if:

  • The message was received
  • Processing is happening
  • Something went wrong

A typing indicator (showing "R2 is typing...") would provide immediate visual feedback and improve the perceived responsiveness.

Proposed solution

Technical Details

Nextcloud Talk API Endpoint

POST /ocs/v2.php/apps/spreed/api/v1/chat/{token}/typing

Request Body:

{
  "typing": true
}

To stop typing:

{
  "typing": false
}

Headers required:

  • OCS-APIRequest: true
  • Authorization: Basic <base64(username:password)> or Bearer token
  • Content-Type: application/json

Proposed Implementation

  1. Trigger typing=true when:
    • Message is received and validated
    • BEFORE any tool calls or processing begins
    • Immediately after dispatchInboundReplyWithBase is called
  2. Trigger typing=false when:
    • Reply is sent successfully
    • OR after a timeout (e.g., 30 seconds) as fallback
    • OR if processing fails/errors out

Example Flow

User sends message
[Show typing indicator]
OpenClaw processes (thinking, tools, etc.)
[Hide typing indicator]
Reply delivered to chat

Configuration Options (Optional)

Could be configurable in openclaw.json:

{
  "channels": {
    "nextcloud-talk": {
      "typingIndicator": true  // default: false for backward compatibility
    }
  }
}

Alternatives considered

No response

Impact

Benefits

  • ✅ Better UX - users see immediately that processing started
  • ✅ Matches behavior of other chat platforms (WhatsApp, Signal, etc.)
  • ✅ Aligns with Nextcloud Talk WebUI experience
  • ✅ No breaking changes - purely additive feature

Reference

  • Nextcloud Talk API Documentation: POST /ocs/v2.php/apps/spreed/api/v1/chat/{token}/typing
  • Similar implementations exist for Discord, Slack, and other channel plugins

Evidence/examples

No response

Additional information

No response

extent analysis

TL;DR

Implement the Nextcloud Talk "typing indicator" API endpoint to improve user experience by sending a typing=true request when OpenClaw starts processing a message and typing=false when the reply is sent or a timeout occurs.

Guidance

  • To implement the typing indicator, send a POST request to the Nextcloud Talk API endpoint /ocs/v2.php/apps/spreed/api/v1/chat/{token}/typing with the request body {"typing": true} when OpenClaw receives a message and starts processing.
  • When the reply is sent successfully or a timeout occurs, send another POST request with the request body {"typing": false} to stop the typing indicator.
  • Consider adding a configuration option in openclaw.json to enable or disable the typing indicator feature, with a default value of false for backward compatibility.
  • Verify the implementation by checking the Nextcloud Talk UI for the typing indicator when OpenClaw is processing a message.

Example

// Example request to start typing indicator
{
  "typing": true
}

// Example request to stop typing indicator
{
  "typing": false
}

Notes

The implementation details and API endpoint are specific to Nextcloud Talk, and the proposed solution assumes that the OpenClaw system has the necessary authentication and authorization to send requests to the Nextcloud Talk API.

Recommendation

Apply the workaround by implementing the typing indicator API endpoint, as it provides a better user experience and aligns with the behavior of other chat platforms.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Feature Request] Typing Indicator for Nextcloud Talk Channel [1 participants]