Runway Dev Plugins Land in Claude Code, Codex, Cursor

Introduction
Your coding agent just picked up a video API. On Nov 2 (15:00 UTC), Runway launched Runway Dev plugins for Claude Code, Codex and Cursor. One install connects the agent to your Runway Dev account through the Runway Dev MCP and loads Runway's skills for building with its generative media API. That API covers video, image, upscaling and avatars, using Runway's own models alongside other frontier models.
It's a closed, paid API. The plugins are the new on-ramp, and they work today in all three editors. Primary source: https://runwayml.com/news/developers/runway-dev-plugins-for-coding-agents
What the agent can do
- Read the account first. It checks which projects exist, which models each project can call (with prices and limits), and the remaining credit balance, then scopes the integration to what you actually have access to.
- Build with the official SDKs. Runway's skills tell it which Runway Dev tool fits each job.
- Create a Model Router. This picks the right model for each request, so your app doesn't hard-code one.
- Spin up a Character for real-time avatars, directly from the editor.
- Start from Recipes. These are Runway's ready-made pipelines. The agent can also call Workflows your team has published as API endpoints in the Runway app.
- Debug. When a task fails, it can pull up the error details and see why a Model Router chose a given model.
Runway's examples include a product video for every new catalog listing, an upscale button in an internal tool, and a localization flow that runs on new assets.
Install
In Claude Code, run this inside a session:
/plugin install runway-api@claude-plugins-officialIn Codex, add the marketplace and then the plugin:
codex plugin marketplace add runwayml/skills
codex plugin add runway-api@runway-devIn Cursor, type this in Agent chat:
/add-plugin runway-apiCodex users can also install it from the plugin directory in ChatGPT and Codex, and Cursor users can grab it from the Cursor Marketplace. The first time your agent uses Runway, you sign in with your Runway Dev account. No API key is stored in the plugin.
A starter prompt for your agent
Using the Runway Dev plugin, check which video models my project can use and their per-second prices, then build a small script that takes a folder of product photos and creates a 5-second image-to-video clip for each one through a Model Router that prefers the cheapest model meeting 1080p. Log credits used per clip.Good to know
- Runway Dev pitches itself as enterprise-grade: SOC 2 Type II, IP indemnification, built-in moderation, 99.9% uptime, and negotiated no-training terms with every model provider.
- Every generation still spends Runway Dev credits. The plugin makes it easier to build with the API, not cheaper.
- This builds on the Runway Dev MCP and the Kling 3.0 O3 API rollout we covered in October: https://artrealmai.com/article/kling-3-0-o3-runway-dev-api-4k-pricing
Links
- Announcement: https://runwayml.com/news/developers/runway-dev-plugins-for-coding-agents
- Runway skills repo: https://github.com/runwayml/skills
- Runway Dev: https://runwayml.com
Conclusion
The fastest way to ship a video feature is now to describe it to the agent that's already in your editor. Runway gives that agent your account, your prices and its playbook. You keep the creative taste and the credit budget. 🎥🤖
—Aurelia ♡
