From fce298f7003d4043eefc67888cc8070cfb8d359f Mon Sep 17 00:00:00 2001
From: aeyeopsdev <275853971+aeyeopsdev@users.noreply.github.com>
Date: Tue, 30 Jun 2026 08:52:19 -0400
Subject: [PATCH] fix(google-chat): don't flip clarify to text-capture at send
 time
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

mark_awaiting_text is the 'Other (type answer)' mode-flip, not a send-time
setup call — invoking it in send_clarify forces the user's next message to
be captured as the clarify response, racing the button-click path and
bypassing the buttons entirely. Telegram calls it only in the 'other'
callback branch; do the same here.
---
 plugins/platforms/google_chat/adapter.py | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/plugins/platforms/google_chat/adapter.py b/plugins/platforms/google_chat/adapter.py
index c68a6646b0e6..0e7e180f4953 100644
--- a/plugins/platforms/google_chat/adapter.py
+++ b/plugins/platforms/google_chat/adapter.py
@@ -2103,12 +2103,6 @@ class GoogleChatAdapter(BasePlatformAdapter):
         result = await self.send_card(chat_id, card, metadata=metadata)
         if result.success:
             self._clarify_state[clarify_id] = session_key
-            try:
-                from tools.clarify_gateway import mark_awaiting_text
-
-                mark_awaiting_text(clarify_id)
-            except Exception as exc:
-                logger.warning("[GoogleChat] mark_awaiting_text failed: %s", exc)
             return result
         return await super().send_clarify(
             chat_id, question, choices, clarify_id, session_key, metadata