Google Meet Overview
Invite Cygent to a Google Meet call. It transcribes, answers security questions live, and summarizes the meeting after.
Overview
Cygent can join a Google Meet call as a participant — not a recording bot, a teammate. It listens, transcribes, answers questions out loud when addressed by name, drops supplementary links and code into the Meet chat, and sends a summary to your team channel (plus per-participant DM follow-ups) after the call ends.
The killer use case isn't meeting notes. It's having a senior security engineer in the room during architecture discussions — one with full context on your protocol, your past decisions, and the current finding backlog.
Example — WBTC as collateral
A GhostLend team is on a Google Meet call debating collateral expansion. Cygent is in the call. Someone asks out loud:
"Hey Cygent — what do you think of adding wrapped Bitcoin as collateral?"
Cygent replies over voice, in real time, with a specific and protocol-aware answer:
A few things to flag. First, custodial trust — WBTC relies on a centralized custodian holding native BTC. If the custodian becomes compromised or regulated, the backing is at risk, which has no analog for WETH.
Second, a concrete technical issue: WBTC uses 8 decimals, not 18. Your existing collateral math assumes 18. You'll need to normalize in
getCollateralValueor you'll mis-price WBTC positions by 10 orders of magnitude and anyone can borrow against effectively free collateral.Third, volatility — BTC's historical volatility differs from ETH's. You'll want a more conservative liquidation threshold than your current WETH-only math uses. I'd recommend modeling around 70% LTV for WBTC vs the 80% you use for WETH.
I can open an issue with these three items if you want.
That's the difference between a meeting bot and a security engineer. Cygent knew the protocol used 18 decimals because it has audited the codebase. It raised the 8-decimal mismatch before anyone wrote a line of code. The team walks out of the meeting with three concrete action items, not a vague "we should think about risks."
How to invite Cygent
The simplest path: paste the Meet link into the Slack channel where Cygent lives.
@cygent join https://meet.google.com/xyz-abcd-efg
Cygent confirms, joins the meeting as a participant (you'll see "Cygent" in the participant list), and posts a one-line acknowledgement back in the Slack thread.
You can also invite from Discord, Telegram, or the dashboard — wherever the Cygent agent is connected. The Meet URL is the only thing Cygent needs.
Cygent requires the Google Meet integration to be enabled on the agent. Go to Settings → Connected Apps → Experimental → Google Meet and toggle it on if you don't see Cygent responding to Meet URLs.
During the call
Once Cygent joins, four things are happening in parallel:
| Channel | What Cygent does |
|---|---|
| Live transcription | Every participant's speech is transcribed in real time. Used for context and for the post-meeting summary. |
| Voice activity detection | Listens for its name. When someone says "Cygent, ..." it treats that as an addressed question and responds. |
| Voice responses | Uses text-to-speech so you hear it over the call like any other participant. Responses kept to 20–60 seconds. |
| Supplementary chat | For code snippets, links, file references — Cygent posts in the Meet chat alongside the voice response. |
See How It Works for the full mechanics.
When to bring Cygent in
Not every meeting needs it. The ones where it adds real value:
| Meeting type | Why it helps |
|---|---|
| Architecture discussions | Design decisions with security implications — new collateral, oracle, access-control model, upgrade mechanism |
| Audit debriefs | Going over findings with the full team — "Cygent, remind us what M-4 was about" |
| Post-mortem reviews | Debriefing after an incident — Cygent has the finding history and decision log |
| Customer / partner technical calls | Security questions might come up; having a bot that answers on the spot beats "let me get back to you" |
Situations where it's less useful: standups, 1:1s, non-technical meetings.
After the call
When the meeting ends — either all humans leave or the host ends it — Cygent kicks off a post-meeting workflow:
- Meeting summary. Structured summary with key topics, decisions made, and action items. Posted to the channel that originally triggered the join.
- Per-participant DMs. Each participant gets a DM with the summary, action items assigned to them, and any relevant follow-ups.
- Extracted context. Anything heard that matters for future audits — a design decision, an accepted risk, a protocol invariant — gets added to persistent memory. That context flows into future audits and PR reviews automatically.
Put the Meet URL in a thread rather than the main channel if you want the summary to land in that thread. The routing follows the trigger location.
Limits and etiquette
| Limit | Value |
|---|---|
| Concurrent meetings | Up to 3 per instance |
| Duration | Meetings cap at 4 hours |
| Silence | Won't chime in unless addressed by name |
| Dismissal | Kick from Meet UI, say "Cygent, please leave the call," or Slack: @cygent leave the meet |
Cygent transcribes everything said on the call. If a call has content that should not be transcribed — HR discussions, legal privilege, private negotiation — don't invite Cygent. Its presence is a disclosure.