API Changes Need Previews of the Tools They Generate

Summary

Cloudflare’s Forge moves API-generated tools into the review loop before merge. Its new cf CLI is an early consumer, showing how one API definition can shape the commands people and agents use. The practical change is what teams can inspect before shipping; generated output still needs a behavior check.

Key Updates

• Review the generated result before release. Cloudflare describes Forge as a pipeline that runs in each team’s API repository, lints changes and creates installable previews of generated tools. It supports OpenAPI input today and lets teams chain one generator’s output into another.
• cf provides a concrete first use. The new CLI uses Forge to generate commands from Cloudflare’s API schemas. It launches in open beta with JSON as the default output and command search for agents. Its typed configuration starts with Workers; broader product configuration remains planned, and some development and deployment paths still delegate to Wrangler.
• The wider rollout is unfinished. Forge is open source under Apache 2.0 and already powers cf. Cloudflare says its API documentation and other SDKs will move to the pipeline over the coming months. Support for additional input formats and a new API-versioning approach are future work.

Why It Matters

An API change reaches users through more than its server implementation. A changed parameter or response can alter the generated command, client library and documentation. Cloudflare describes teams previously finding generation failures at release time, after another team had merged the change.

Moving those outputs into the pull request gives reviewers something concrete to inspect. The operating assumption to revisit is that a valid API definition is enough to approve what consumers will receive. A successful generator run does not establish runtime compatibility, and these announcements provide no independent compatibility results.

Builder Takeaway

For one API change in a non-production environment, compare a generated CLI command before and after the change. Run the same harmless request with both versions and check the arguments and returned fields against one existing consumer test. Record any contract difference in the pull request before deciding whether the change is ready to merge.

Related Past Coverage

Our September 24 edition on isolated runtime previews examined running a branch before merge and the limits of that isolation. This edition extends the review question to generated tools. The earlier article is historical context, not evidence of Forge’s behavior.