Skip to main content
OpenClaw ships a bundled runway provider for hosted video generation, enabled by default, registered against the videoGenerationProviders contract.

Getting started

1

Set the API key

2

Set Runway as the default video provider

3

Generate a video

Ask the agent to generate a video. Runway will be used automatically.

Supported modes and models

The provider exposes seven Runway models split across three modes. The same model id can serve more than one mode (for example gen4.5 works for both text-to-video and image-to-video). Local image and video references are supported via data URIs.
Video-to-video currently requires runway/gen4_aleph. Other Runway model ids reject video reference inputs.
Picking a Runway model id from the wrong column produces an explicit error before the API request leaves OpenClaw. The provider validates model against the mode’s allowlist (TEXT_ONLY_MODELS, IMAGE_MODELS, VIDEO_MODELS) in extensions/runway/video-generation-provider.ts.

Configuration

Advanced configuration

OpenClaw recognizes both RUNWAYML_API_SECRET (canonical) and RUNWAY_API_KEY. Either variable authenticates the Runway provider.
Runway uses a task-based API. After submitting a generation request, OpenClaw polls GET /v1/tasks/{id} until the video is ready. No additional configuration is needed for the polling behavior.

Video generation

Shared tool parameters, provider selection, and async behavior.

Configuration reference

Agent default settings including video generation model.