Files

glifocat 9633788a1b fix(skills): bump @chat-adapter/* cohort to 4.27.0

@chat-adapter/discord@4.27.0 includes vercel/chat#256, which fixes the
Discord adapter unconditionally setting payload.content alongside
payload.embeds when posting a card. In 4.26.0 every Discord card
appeared twice (text content above the embed, identical content inside
the embed) — every new install reproduced this on the welcome tour and
on every approval card.

The other 7 skills bump in lockstep because @chat-adapter/discord@4.27.0
depends on chat@4.27.0 while @chat-adapter/<other>@4.26.0 depend on
chat@4.26.0. Mixing the cohort produces a TypeScript dual-version
conflict between the bridge and adapter ChatInstance types.

Files updated (one line per file in each pnpm install command):
- add-discord (the user-visible bug fix)
- add-gchat, add-github, add-linear, add-slack, add-teams, add-telegram,
  add-whatsapp-cloud (cohort consistency)

Out of scope: add-imessage, add-matrix, add-webex, add-resend use
third-party packages with independent versioning.

Closes #2264

2026-05-05 00:28:25 +02:00

2.6 KiB

Raw Blame History

name, description

name	description
add-gchat	Add Google Chat channel integration via Chat SDK.

Add Google Chat Channel

Adds Google Chat support via the Chat SDK bridge.

Install

NanoClaw doesn't ship channels in trunk. This skill copies the Google Chat adapter in from the channels branch.

Pre-flight (idempotent)

Skip to Credentials if all of these are already in place:

src/channels/gchat.ts exists
src/channels/index.ts contains import './gchat.js';
@chat-adapter/gchat is listed in package.json dependencies

Otherwise continue. Every step below is safe to re-run.

1. Fetch the channels branch

git fetch origin channels

2. Copy the adapter

git show origin/channels:src/channels/gchat.ts > src/channels/gchat.ts

3. Append the self-registration import

Append to src/channels/index.ts (skip if the line is already present):

import './gchat.js';

4. Install the adapter package (pinned)

pnpm install @chat-adapter/gchat@4.27.0

5. Build

pnpm run build

Credentials

Go to Google Cloud Console

Create or select a project

Enable the Google Chat API

Go to Google Chat API > Configuration:

App name and description

Connection settings: select HTTP endpoint URL and set to https://your-domain/webhook/gchat

Create a Service Account:

Go to IAM & Admin > Service Accounts > Create Service Account

Grant the Chat Bot role

Create a JSON key and download it

Configure environment

Add the service account JSON as a single-line string to .env:

GCHAT_CREDENTIALS={"type":"service_account","project_id":"...","private_key":"...","client_email":"..."}

Sync to container: mkdir -p data/env && cp .env data/env/env

Next Steps

If you're in the middle of /setup, return to the setup flow now.

Otherwise, run /manage-channels to wire this channel to an agent group.

Channel Info

type: gchat
terminology: Google Chat has "spaces." A space can be a group conversation or a direct message with the bot.
how-to-find-id: Open the space in Google Chat, look at the URL — the space ID is the segment after /space/ (e.g. spaces/AAAA...). Or use the Google Chat API to list spaces.
supports-threads: yes
typical-use: Interactive chat — team spaces or direct messages
default-isolation: Same agent group for spaces where you're the primary user. Separate agent group for spaces with different teams or sensitive contexts.

2.6 KiB Raw Blame History