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.
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 includesmessage.thread.nameand the account hasreplyToMode: "all".Repro / Evidence
replyToMode: "all".threadName: "spaces/.../threads/...".[[reply_to_current]].context.ReplyToIdmade replies stay in the original thread.Expected
When Google Chat inbound events provide
message.thread.name,[[reply_to_current]]should targetspaces/.../threads/....Actual
Google Chat message tool replies can resolve without the thread resource and post outside the original thread.