Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Google Chat Space/Group messages are received (HTTP 200) but silently ignored; DMs work correctly. Tested with both Add-on and standard Chat API apps.

Steps to reproduce

1. Configure Google Chat webhook with groupPolicy: "open" and audienceType: "app-url"
2. Add the Chat app to a Space (group chat)
3. Send a message mentioning @AppName in the Space
4. Observe: HTTP 200 returned but no session created, no agent response
5. Send a DM to the same app
6. Observe: DM works correctly, session created as agent:X:googlechat:direct:spaces/Y

Expected behavior

Space messages should create sessions as agent:X:googlechat:group:spaces/Y and be processed by the agent, similar to how DMs create agent:X:googlechat:direct:spaces/Y sessions.

Actual behavior

Space messages return HTTP 200 but no session is created. No errors logged. The message is silently dropped. Caddy logs show the request was received and forwarded to gateway. OpenClaw logs show no googlechat:group session creation. Only googlechat:direct sessions appear (for DMs).

OpenClaw version

2026.3.28

Operating system

Ubuntu 24.04

Install method

npm global

Model

anthropic/claude-sonnet-4-6

Provider / routing chain

openclaw -> anthropic (direct)

Additional provider/model setup details

This is a Google Chat channel issue, not model-related. Config:

• audienceType: "app-url"
• groupPolicy: "open"
• appPrincipal: configured
• Tested with both Workspace Add-on format and standard Chat API app

Logs, screenshots, and evidence

Caddy access log (Space message received):
1774979423.83 200 /googlechat-raa-v2

OpenClaw sessions created (only DMs, no groups):
agent:raa:googlechat:direct:spaces/mlopdsaaaae  ← DM works
agent:raa:googlechat:direct:spaces/4ipcesaaaae  ← DM works

No agent:raa:googlechat:group:* sessions ever created for Space messages.

Impact and severity

Affected: Google Chat users trying to use Spaces (group chats) Severity: High (completely blocks group chat functionality) Frequency: 100% - all Space messages are ignored Consequence: Cannot use OpenClaw with Google Chat Spaces; only DMs work. Team collaboration via Spaces is blocked.

Additional information

Tested with two separate Google Cloud projects:

1. App configured as Workspace Add-on (gcp-sa-gsuiteaddons service account)
2. App configured as standard Chat API (unchecked "Create as Workspace Add-on")

Both have identical behavior: DMs work, Spaces don't.

Related issue #13856 describes similar symptoms but was attributed to Add-on format. This testing confirms the bug exists regardless of app configuration method.

Workaround: Use DMs only (works perfectly).