Zoom

Zoom

Zoom connects Codex to Zoom meeting context through the Zoom app connector and provides developer workflows for planning, building, debugging, and reviewing Zoom integrations across APIs, SDKs, webhooks, WebSockets, bots, and automation use cases.

Plugin Shape

This repository is packaged as a Codex plugin:

• plugin manifest: .codex-plugin/plugin.json
• Zoom app mapping: .app.json
• deterministic command workflows: commands/
• focused reviewer agents: agents/
• explicit-only developer workflows and references: skills/
• branding and screenshot assets: assets/

This plugin contains the Zoom app connector mapping, local developer guidance, commands, skills, reviewer agents, and branding assets.

Upstream Source

• Repo: zoom/zoom-plugin-codex
• Imported commit: 6f30034c94b4594daaf814cd9bf4cf972b90a323
• Local plugin id: zoom

What Zoom Does In Codex

Use Zoom when you want Codex to:

• search Zoom meetings by topic, attendee, or content
• retrieve summaries, transcripts, recordings, and related meeting assets
• pull meeting context into coding, documentation, or follow-up workflows
• choose the right Zoom product surface for an integration
• build Zoom REST API, SDK, webhook, WebSocket, bot, and automation workflows
• debug Zoom auth, event delivery, SDK, and API issues

Using In Codex

Codex can use this plugin through the Zoom app connector plus command, skill, and reviewer-agent surfaces:

• install the plugin from /plugins
• authenticate the Zoom app connector when Codex prompts for it
• mention the plugin as @Zoom if the UI exposes it
• use natural language requests that need live Zoom meeting context
• use slash commands for deterministic flows such as /setup-zoom-oauth, /debug-zoom-auth, /debug-zoom-webhook, and /zoom-integration-doctor
• invoke a bundled skill explicitly with $skill-name, for example $start or $setup-zoom-oauth

The Zoom app connector auth is managed by Codex. It is not exposed as a shell environment variable or raw bearer token.

The developer skills in this curated package are explicit-only: each bundled developer skill has an agents/openai.yaml file with policy.allow_implicit_invocation: false, so they are available when invoked directly but should not be selected implicitly from normal task wording.