Files
hermes-agent/plugins/google_meet
Teknium 2776813df3 compat(plugins): temporary import-path shims for external plugins — ONE commit, revert on schedule
The Sep 2026 decomposition (PR #102117) makes internal import paths a non-API: names now live in
the focused modules that define them. This commit is the ONLY thing keeping the old paths alive,
so external plugins have time to update. It is deliberately a single, unsquashed commit:

    git revert <this sha>

removes every shim, stub and manifest at once on the announced date. Nothing in-tree may depend on
these pointers: scripts/check_compat_pointers.py (wired into lint.yml) fails CI if it does.

What it adds (see COMPAT_MANIFEST.md, compat_manifest.json):
- 332 facade modules get one delimited `PLUGIN-COMPAT` block appended at the end of the file
- 1,172 moved names resolved lazily via a module `__getattr__` (PEP 562) — never a top-level import,
  so no import cycles; facades that already had `__getattr__` get a chained one
- 592 third-party/stdlib names the old modules used to expose, with their original import statements
- 266 public definitions that had been deleted as unused, restored byte-for-byte from the pre-decomposition
  tree (+40 private helpers and 16 imports pulled in only because a restored definition needs them)
- 3 deleted modules recreated as re-export stubs (gateway/startup_watchdog, hermes_cli/observability/
  relay_runtime, tools/environments/modal_utils)
- private names (`_x`) get no pointer: they were never API (3,792 skipped)

Verified: all 335 touched modules import under a fresh HERMES_HOME and every manifest name resolves;
the lint reports zero in-tree uses; ruff clean; targeted suites unchanged.
2026-09-03 17:13:22 -07:00
..
…
…

google_meet plugin

Let the hermes agent join a Google Meet call, transcribe it, optionally speak in it, and do the followup work afterwards.

What ships

Version What Status
v1 Transcribe-only: Playwright joins Meet, scrapes captions to transcript file ✓ ships by default
v2 Realtime duplex audio: bot speaks in-call via OpenAI Realtime + BlackHole/PulseAudio null-sink ✓ opt in with mode='realtime'
v3 Remote node host: run the bot on a different machine than the gateway ✓ opt in with node='<name>'

Architecture

┌─ gateway (Linux box, where hermes runs) ────────────────────────────┐
│                                                                      │
│   agent → meet_join(url, mode='realtime', node='my-mac')             │
│         │                                                            │
│         └─ NodeClient ─── ws ────┐                                   │
│                                  │                                   │
└──────────────────────────────────┼───────────────────────────────────┘
                                   │ wss (token auth)
                                   ▼
┌─ node host (user's Mac, signed-in Chrome lives here) ───────────────┐
│                                                                      │
│   NodeServer (from `hermes meet node run`)                           │
│     │                                                                │
│     ├─ start_bot → process_manager.start() → spawns meet_bot         │
│     │                                                                │
│     └─ meet_bot (Playwright)                                         │
│        ├─ Chromium → meet.google.com                                 │
│        ├─ caption scraper → transcript.txt                           │
│        └─ (realtime mode only) RealtimeSpeaker thread                │
│             ↓                                                        │
│           OpenAI Realtime WS → speaker.pcm                           │
│             ↓                                                        │
│           paplay → null-sink ← Chrome fake mic                       │
│                                                                      │
└──────────────────────────────────────────────────────────────────────┘

Without v3: the whole right column runs on the gateway machine. Without v2: the "realtime" path is skipped; transcribe runs alone.

Files

Path Purpose
plugin.yaml manifest
__init__.py register(ctx) — registers 5 tools + on_session_end hook + hermes meet CLI
meet_bot.py Playwright bot subprocess (standalone, python -m plugins.google_meet.meet_bot)
process_manager.py local bot lifecycle + enqueue_say
tools.py agent-facing tools + node-routing helper
cli.py hermes meet setup / auth / join / status / transcript / say / stop / node ...
audio_bridge.py v2: PulseAudio null-sink (Linux) + BlackHole probe (macOS)
realtime/openai_client.py v2: RealtimeSession + RealtimeSpeaker (file-queue → OpenAI Realtime WS → PCM)
node/protocol.py v3: message envelope + validation
node/registry.py v3: $HERMES_HOME/workspace/meetings/nodes.json
node/server.py v3: NodeServer (runs on host machine)
node/client.py v3: NodeClient (used by tool handlers + CLI on gateway)
node/cli.py v3: hermes meet node {run,list,approve,remove,status,ping}
SKILL.md agent usage guide

Local quick start

hermes plugins enable google_meet
hermes meet install                                      # pip + Chromium
hermes meet setup                                        # preflight
hermes meet auth                                         # optional
hermes meet join https://meet.google.com/abc-defg-hij    # transcribe

Realtime mode

Linux (preferred, most automated):

hermes meet install --realtime                     # installs pulseaudio-utils
echo 'OPENAI_API_KEY=sk-...' >> ~/.hermes/.env
hermes meet join https://meet.google.com/abc-defg-hij --mode realtime
# then from the agent or CLI:
hermes meet say "Good morning everyone, I'm the note-taker bot."

macOS:

hermes meet install --realtime     # runs: brew install blackhole-2ch ffmpeg
# then — manually! — open System Settings → Sound → Input → BlackHole 2ch
echo 'OPENAI_API_KEY=sk-...' >> ~/.hermes/.env
hermes meet join https://meet.google.com/abc-defg-hij --mode realtime

On macOS, hermes will not switch your system audio input automatically — the user has to do it. This is deliberate: switching default input on a whim would be a surprising side effect.

Remote node host

On the node machine (e.g. user's Mac with a signed-in Chrome):

pip install playwright websockets
python -m playwright install chromium
hermes plugins enable google_meet
hermes meet node run --display-name my-mac --host 0.0.0.0 --port 18789
# prints the bearer token on first run; copy it

On the gateway:

hermes meet node approve my-mac ws://<mac-ip>:18789 <token>
hermes meet node ping my-mac
# now any meet_* tool call accepts node='my-mac' (or 'auto')

Safety

  • URL gate: only https://meet.google.com/abc-defg-hij, /new, /lookup/<id>.
  • No calendar scanning, no auto-dial, no auto-consent announcement.
  • Node server uses bearer-token auth; no key exchange, no TLS termination built in — run it on a LAN or behind a reverse proxy you trust.
  • One active meeting per (gateway, node) pair. A second meet_join leaves the first.
  • meet_say refuses unless the active meeting was started with mode='realtime'.

Out of scope

  • Calendar scanning — deliberately not implemented. Join URLs must be explicit.
  • Multi-tenant node sharing — a node serves one gateway at a time.
  • Windows — audio bridging isn't tested; register() no-ops on Windows.
  • System audio input switching on macOS — user responsibility, not the bot's.