Bring your own agent
Anything that can edit a .tsx file can author a deck.
There is no SDK, no plugin API and no per-editor integration to install. A deck is a directory of React files, so the requirement on an agent is exactly that it can read and write files in a workspace.
That is not a marketing position so much as a consequence of the file format. Clients that people use with it today: Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Windsurf, Zed.
What an agent needs, in order
The contract. AGENTS.md at the workspace root, mirrored by CLAUDE.md.
Every listed client reads one or the other without being told to.
The guides. Run beem mcp install and beem login, and the agent can call
authoring_guide for the authoring material. See
Connect for which clients the installer writes config for,
and Overview for why this part is served rather than
shipped.
File access. That is the whole of it.
Why AGENTS.md is the canonical file
AGENTS.md is the cross-tool convention — Codex, Cursor, Gemini CLI, OpenCode,
Windsurf and Zed all look for it. Claude Code looks for CLAUDE.md, so the
scaffolder writes that as a link to the same file rather than a copy.
Edit AGENTS.md when you want to add house rules of your own: a palette every
deck should use, a naming scheme for deck ids, a page count you do not want
exceeded. Leave the link alone, and both conventions keep seeing one file.
Where the cloud tools fit
The same MCP registration that serves the guides also gives the agent the deck tools — create, check, preview, push, publish, share. An agent can take a deck from a sentence to a public link without you leaving the conversation. Those are covered in Connect.