You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Route Google Chat mentions and slash commands to separate handlers #1
The Google Chat webhook (GH-2) only handles @mentions (chat.messagePayload). Slash commands arrive as chat.appCommandPayload (captured in tests/fixtures/google-slash-command.json) and are dropped at the endpoint. We want both event kinds to reach the worker and be handled separately, as groundwork for ingesting /add-knowledge content later.
Decisions
handle_event only decides the event kind and delegates.
Private _handle_mention and _handle_command in app/services/google_chat.py each do their own logging (no ingestion yet).
Model appCommandPayload in app/schemas/google_chat.py (shares space/message shape with messagePayload, adds appCommandMetadata).
The endpoint dispatches and acks slash commands too; only events with neither payload still get {}.
Shipped: Google Chat @mentions and slash commands now reach the worker and are handled by separate private handlers (_handle_mention, _handle_command), with the slash-command payload modelled and tested. Details are in the "Google Chat webhook" wiki section and docs/wiki/google-bot.md.
Activity
feat: handle google chat slash commands in worker and endpoint (GH-1)
test: cover google chat slash command flow (GH-1)
docs: document google chat mention and slash command flow (GH-1)
amitavroy commentedon Oct 18, 2026
Shipped: Google Chat @mentions and slash commands now reach the worker and are handled by separate private handlers (
_handle_mention,_handle_command), with the slash-command payload modelled and tested. Details are in the "Google Chat webhook" wiki section anddocs/wiki/google-bot.md.docs: archive plan 006 and update google chat wiki entry (GH-1)