Live streams, meetings and screen capture

Which path

1. VideoDB connector tools present (names such as connect_rtstream, index_rtstream_scenes, create_rtstream_alert, record_meeting): use them for cameras, streams and meetings. This is the path in Claude chat on web, desktop and mobile, and in Cowork. Do not install anything and do not ask for an API key.
2. No VideoDB tools, but you have a shell (Claude Code, Cowork, any agent that can run Python): ask for the VideoDB API key in one friendly line (free at https://console.videodb.io, $20 of credits, no card). When the user gives it, in chat or any other way, save it yourself to the project's .env as VIDEO_DB_API_KEY, never print it, and continue with the Python SDK path at the end of this file. In Claude Code, /mcp then authorizing videodb also works.
3. No VideoDB tools and no shell: you are in Claude chat. Reply with only this, adapted to the request: "VideoDB isn't connected yet. Open Settings → Connectors, find VideoDB, click Connect and log in (free, no card). Then send this request again and I'll take it from there." Do not mention API keys, .env, shells, Claude Code or /mcp here; none of them apply in chat, and a key pasted into chat cannot be used because nothing runs code there.
4. Desktop screen capture needs a local recorder, so it runs only with a shell (Claude Code, Cowork) through the Python SDK path, on macOS and Windows. In chat, say so in one line.

Talking to the user: never write "index", "indexed" or "indexing" in a reply; say "searchable". One line of status at a time, then the result.

With the connector tools

Connect a camera or stream. connect_rtstream(url="rtsp://...", name="Lobby cam") registers an RTSP, RTMP or HLS feed and starts ingesting. Note the rts- id. set_rtstream_status(rtstream_id, action="stop") stops it; streams bill while they run, so stop when the user is done.

Watch for an event and alert.