PR #49361: fix(googlechat): use agent identity.name in typing indicator fallback chain

• Repository: openclaw/openclaw
• Author: zhuowater
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/49361

Description (problem / solution / changelog)

Problem

Closes #49350

When a Google Chat agent has identity.name configured but no direct agent.name, the typing indicator was falling back to the hardcoded "OpenClaw is typing..." string instead of the configured identity name.

Root Cause

resolveBotDisplayName in extensions/googlechat/src/monitor.ts has a 3-step fallback chain:

1. Account config name (account.config.name)
2. Agent name (agent.name)
3. ❌ Hardcoded "OpenClaw"

It was missing a check for agent.identity?.name, which is the standard way users configure bot identity in OpenClaw (IdentityConfig.name).

Fix

Add agent.identity?.name as a third fallback before the hardcoded "OpenClaw" string.

Updated fallback chain:

1. Account config name (account.config.name)
2. Agent name (agent.name)
3. ✅ Agent identity name (agent.identity?.name) ← new
4. "OpenClaw" as last resort

Example

Config:

{
  "agents": {
    "list": [{
      "id": "main",
      "identity": { "name": "Alvin" }
    }]
  }
}

Before: Shows _OpenClaw is typing..._ After: Shows _Alvin is typing..._

Changes

• extensions/googlechat/src/monitor.ts: Added agent?.identity?.name check in resolveBotDisplayName (5 lines)
• Updated JSDoc comment to reflect the 4-step fallback chain

Changed files

• extensions/googlechat/src/monitor.ts (modified, +5/-1)

PR #49406: fix(googlechat): strip markdown before sending messages

• Repository: openclaw/openclaw
• Author: pracin
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/49406

Description (problem / solution / changelog)

Summary

Fixes #49350 - Google Chat messages were displaying markdown syntax literally instead of being rendered.

Problem

Google Chat does not support markdown formatting. Previously, messages containing markdown (bold, italic, headers, code blocks, etc.) were sent as raw text, displaying the markdown syntax literally to users.

Solution

Strip markdown formatting before sending messages to Google Chat:

• Export stripMarkdown function from plugin-sdk/googlechat
• Strip markdown in deliverGoogleChatReply (monitor.ts) for inbound replies
• Strip markdown in outbound sendText/sendMedia (channel.ts)
• Update test mocks to include stripMarkdown

Changes

Testing

• All 38 existing tests pass
• No new tests added (behavior change only, stripMarkdown is already tested elsewhere)

Note on Typing Indicator Name

Issue #49350 also mentioned the typing indicator showing "OpenClaw" instead of the configured name. This is a configuration issue, not a bug. Users can customize the display name by setting:

{
  "channels": {
    "googlechat": {
      "name": "YourBotName"
    }
  }
}

Or via agent configuration:

{
  "agents": {
    "list": [{ "id": "main", "name": "YourBotName" }]
  }
}

Changed files

• extensions/googlechat/runtime-api.ts (modified, +2/-0)
• extensions/googlechat/src/channel.ts (modified, +6/-2)
• extensions/googlechat/src/monitor.ts (modified, +10/-4)
• extensions/googlechat/src/resolve-target.test.ts (modified, +1/-0)
• src/line/markdown-to-line.ts (modified, +23/-3)
• src/plugin-sdk/googlechat.ts (modified, +1/-0)