One line. Asks where to install, builds a private Python
venv (nothing global), adds the skill to Claude Code or Codex
(auto-detected), and starts the bridge.
curl -fsSL …/install.sh | shmacOS / Linux. Needs python3, curl, unzip.
Named container with the WebRTC UDP port pinned + published. Works on native Linux Docker (UDP forwards). On Docker Desktop (Mac/Windows) UDP is unreliable — use “Docker (TURN)” instead.
docker run …Refresh / update (re-pull the server & skill, restart the bridge) — re-creates the named container:
docker rm -f …Use your host’s LAN IP instead of 127.0.0.1 if the browser
is on another machine; --network host works on Linux only.
For Docker Desktop (Mac/Windows): UDP isn't forwarded reliably, so
this runs a coturn relay in the container and pairs over TCP. Recreates the
named container; only :3478/tcp is published.
docker run …Verify — must show
3478/tcp -> 0.0.0.0:3478 and a TCP listener:
docker port sasha-slides-bridge
docker exec sasha-slides-bridge sh -c "grep -iE 'listener opened|relay endpoint|error|cannot' /tmp/coturn.log | head -20"Then in step 2 choose WebRTC and tick Relay through TURN. (Same machine? Local device is simpler than any Docker option.)
Set it up by hand — explicit steps, private venv, nothing global:
…Then copy the unzipped skill/ folder into
~/.claude/skills/ (or your Codex prompts dir).
Once connected, the slides your agent builds insert straight into this presentation.
② On the bridge machine, open localhost:8787 → Manual tab → paste the request → copy the answer it gives you.
Copy-pasted handshake (no network needed between this https panel and your http bridge), so it works across machines on the same network. Stuck on “connecting…” in Docker? Use the Docker install method in step 1.
Bridge running on this computer? Connect directly — no copy-paste. Best choice when the bridge is on the same Mac (incl. Docker Desktop), since it rides the reliable TCP port — WebRTC needs UDP, which Docker Desktop doesn't forward well.
If your browser blocks it (an https page reaching http://localhost),
switch to WebRTC above — that always works.
Edit drawio diagrams in this deck or doc and collaborate with your agent — it can add or update diagrams while you edit them here, and vice versa. Each diagram's editable source lives on Drive as drawio/<slide|doc>/<id>/<name>.drawio.svg, linked from the image; saving re-renders the PNG and updates the Drive file. Selecting a linked diagram image loads it here automatically.