google-chat-cdp

name	google-chat-cdp
description	Use Google Chat in the local Chrome session through chrome-cdp. Use when asked to open Google Chat, verify the active Google account, switch to an existing Google account manually if needed, find a DM or space, and send or inspect messages in the already logged-in browser.

Google Chat CDP

Use this skill together with chrome-cdp for Google Chat tasks in the user's live Chrome session.

Preconditions

• chrome-cdp is available in this repo at skills/chrome-cdp/.
• Chrome remote debugging is already enabled in chrome://inspect/#remote-debugging.
• The user has explicitly asked for a Google Chat action.

Approval Model

Chrome 146+ may still show approval prompts even with the daemon flow:

• once for a fresh browser debugging session
• once for the first attach to a new tab target
• again after login or account switching, because Google auth often replaces the target ID

Do not fight this with repeated retries. If Chat just went through auth or account switching, expect to re-run scripts/cdp list and attach to the new Chat target.

Workflow

1. Reuse an existing Chat tab

Prefer an existing Chat target from:

skills/chrome-cdp/scripts/cdp list

Pick https://chat.google.com/... if present. Reuse the same target for the whole task instead of opening fresh tabs.

If no Chat tab exists, navigate one approved tab with:

skills/chrome-cdp/scripts/cdp nav <target> https://chat.google.com

2. Verify the active account

Check the page accessibility tree first:

skills/chrome-cdp/scripts/cdp snap <target>

Look for:

• Google Account: ... (email@domain)

If the wrong account is active, let the user complete login or account switching manually. After that, re-run list; the Chat target may have changed.

3. Handle login interruptions

If Chat shows User session expired, click Log in only to resume the already intended manual auth flow. Do not try to guess passwords, OTPs, or SSO steps.

After the user finishes login:

• run scripts/cdp list again
• find the new Chat target
• re-verify the account label before sending anything

4. Open the conversation carefully

Prefer existing DM rows already visible in the left sidebar. For Google Chat, target the exact row element, not a broad container:

• inspect candidates with eval over [role=link]
• click the exact row whose text matches the full contact name
• verify the conversation opened by checking the page title or snap root title

For example, after clicking a DM, the root title should become the contact name, not just Chat.

5. Send the message

In an open conversation:

• focus the composer, usually the textbox with aria like History is on
• use scripts/cdp type <target> '<message>'
• click the button whose aria-label is Send message

Verify completion:

• the draft textbox should clear back to a blank newline
• the thread should show the new message
• it should not remain in Sending...

Practical Patterns

• Prefer snap when structure matters and eval when you need precise DOM targeting.
• Avoid index-based selectors across separate calls if the Chat list can change.
• If login/account switching just happened, assume the old target ID is stale until list proves otherwise.
• Keep the user informed before any action that sends a real message.