openaienmodel: gpt-5-mini-2025-08-07
Automatic provisioning for Flagship bindings
Key Points
- Wrangler auto-provisions Flagship apps
- app_id written back to config
- Supports wrangler.jsonc and wrangler.toml
Summary
Wrangler now supports automatic resource provisioning for Flagship bindings. You can declare a flagship binding without an app_id and, during deployment, Wrangler will either connect to an existing Flagship app or create a new one and then write the resulting app_id back into your wrangler configuration (wrangler.jsonc or wrangler.toml).
Key Points
- Add a flagship binding without specifying app_id in wrangler.jsonc or wrangler.toml.
- During deploy, Wrangler will connect to an existing Flagship app or create a new one and obtain an app_id.
- Wrangler updates your configuration file with the resolved app_id automatically.
- Works as part of Wrangler's automatic resource provisioning for Workers + Flagship bindings.
For implementation details and examples, see the automatic provisioning and Flagship bindings documentation.