Describe the UX Issue

When using GeminiClaw via Discord, the agent sends a "Thinking..." placeholder message and later edits it with the final response.

The problem is that Discord's API does not trigger push notifications for message edits. If a user asks the agent to perform a long-running task (e.g., deep research, scraping) and switches to another app after seeing "Thinking...", they will never be notified when the task is actually finished.

Even if the user explicitly instructs the agent via system prompt to "Always mention me (<@user>) when the task is done" as a workaround, the mention fails to trigger a notification because it is still delivered via an Edit rather than a new MessageCreate event.

Steps to reproduce

1. Ask the agent a question that takes time.
2. The agent replies with "Thinking...".
3. Read the message (channel becomes read) and background the Discord app.
4. The agent finishes the task and edits the message with the final answer.
5. Result: The user receives no notification and must manually check the channel to see if it's done.

Note:
Interestingly, if the final response is very long (exceeding Discord's 2000-character limit), the agent splits the output into multiple chunks. In this specific case, the second chunk is sent as a new MessageCreate event, which does trigger a notification. However, for shorter, single-chunk responses, it fails silently.

Suggested Solutions

To make GeminiClaw truly useful as an asynchronous copilot:

• Option A: Instead of editing the original placeholder, send the final response as a new reply message.
• Option B: Keep the edit behavior for cleanliness, but follow it up with a small new message (e.g., "Task completed.") to trigger the Discord notification.