Runway announced plugins for Claude Code, Codex and Cursor on November 2, connecting coding agents to its generative-media API platform. The official announcement describes a single installation that adds Runway's MCP connection and skills for working with the API.
Account context reaches the coding agent
The plugin lets an agent inspect the connected account's projects, accessible models, prices, limits and credit balance. Runway says the purpose is to build against what a project can actually use, rather than designing an integration around a model or allowance that is unavailable to it.
The documented tools include Model Routers, real-time avatar Characters, reusable Recipes and team Workflows exposed as API endpoints. The examples include generating product videos, adding an upscale action and building localization pipelines. These are described integration use cases, rather than independently tested outcomes from Franklin.
Building and debugging in the editor
Runway's skills provide guidance for its official SDKs and tool selection. When a task fails, the agent can inspect error details and why a Model Router chose a particular model. That information can help distinguish application mistakes from account limits or a routing decision.
The setup uses an initial Runway Dev account sign-in. Runway states that no API key is stored in the plugin. Teams should still understand which account and project the agent is operating against, especially when a workflow can consume paid generation credits.
What a useful first integration looks like
Start with a bounded media task and a defined quality check, such as generating one draft product clip for review. Confirm model availability, expected cost and handling of failed jobs before connecting the workflow to an entire catalog. The plugin reduces the distance between an editor and the media platform; it does not remove the need to evaluate generated assets or control production spending.