openclaw - 💡(How to fix) Fix Google Chat message tool replies escape threads

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…

Google Chat replies sent through message(action=send) with [[reply_to_current]] can post as top-level space messages even when the inbound Google Chat event includes message.thread.name and the account has replyToMode: "all".

Root Cause

Google Chat replies sent through message(action=send) with [[reply_to_current]] can post as top-level space messages even when the inbound Google Chat event includes message.thread.name and the account has replyToMode: "all".

Fix Action

Fix / Workaround

  • Inbound debug showed replyToMode: "all".
  • Inbound debug showed threadName: "spaces/.../threads/...".
  • The agent used the message tool with [[reply_to_current]].
  • Before the fix, the message posted outside the original Google Chat thread.
  • A live patch that maps the Google Chat tool context current reply target to context.ReplyToId made replies stay in the original thread.
RAW_BUFFERClick to expand / collapse

Summary

Google Chat replies sent through message(action=send) with [[reply_to_current]] can post as top-level space messages even when the inbound Google Chat event includes message.thread.name and the account has replyToMode: "all".

Repro / Evidence

  • Inbound debug showed replyToMode: "all".
  • Inbound debug showed threadName: "spaces/.../threads/...".
  • The agent used the message tool with [[reply_to_current]].
  • Before the fix, the message posted outside the original Google Chat thread.
  • A live patch that maps the Google Chat tool context current reply target to context.ReplyToId made replies stay in the original thread.

Expected

When Google Chat inbound events provide message.thread.name, [[reply_to_current]] should target spaces/.../threads/....

Actual

Google Chat message tool replies can resolve without the thread resource and post outside the original thread.

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 Google Chat message tool replies escape threads