Cloudflare launched the cf CLI in open beta on September 28, 2026, extending command-line access across its API for human developers and agents. The most consequential change is the breadth of operations an agent can discover; broader access requires deliberate limits on what credentials and instructions permit.
Command discovery becomes part of the workflow
In its launch post, Cloudflare describes JSON-first output, natural-language command search, TypeScript configuration, and Vite as the default development foundation. The open-source repository is the maintained implementation reference.
Discoverability helps an agent select an operation without receiving thousands of commands in advance. It does not tell the agent whether executing that operation is appropriate. A request to inspect a DNS problem should not silently become permission to rewrite a zone or purchase a domain. Make the intended result and mutation boundary explicit before execution.
Use credentials as an enforceable boundary
For an initial trial, choose read-only credentials scoped to a test account or a narrow resource set. Inspect the commands and outputs the agent uses. When write access becomes necessary, add only the permissions required for a specific workflow and retain a human approval point for changes with wider consequences.
Do not rely on a prompt as the sole safeguard. A narrowly scoped credential can limit damage even when a model misinterprets a task or external content. Keep secrets out of agent-visible command output and logs, and use an identifiable service account so cloud audit records show which workflow performed the action.
Wrangler migration is a configuration change
Cloudflare provides a migration command and describes delegation to Wrangler for workloads that still need it. The announcement also describes continued Wrangler maintenance after the beta. That gives existing projects a migration period rather than a reason for an immediate unreviewed switch.
Review the generated configuration like any production change. Confirm environment selection, routes, bindings, secrets references, build commands, and deployment targets. A successful local run should be followed by a staged deployment and a rollback check before the new CLI becomes the team default.
Design an auditable cloud task
A useful agent task names the resource, the evidence it must collect, the allowable operation, and how success will be checked. Ask the agent to produce a proposed diff before applying broad configuration changes. Preserve error output and partial results so a failed operation is visible.
The beta is worth evaluating for organizations whose agents already operate Cloudflare infrastructure. Treat convenience and capability as separate from authorization: the right command can still be the wrong change for a production account.