Skip to main content

cf-cli

Cloudflare's official cf CLI (beta) for the public Cloudflare API and Workers projects. Use for finding and running Cloudflare commands from the terminal — sign-in and profiles, cf cli search, cf schema, cf deploy/dev/build, resource commands for DNS, zones, D1, KV, and R2 — and for choosing between cf and Wrangler in a project.

소스 정보

저장소
cloudflare/skills
최근 소스 활동
2026년 10월 12일 17:05
감지된 SKILL.md 언어
영어
스타
3,070
포크
315

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
cf-cli
description
Cloudflare's official cf CLI (beta) for the public Cloudflare API and Workers projects. Use for finding and running Cloudflare commands from the terminal — sign-in and profiles, cf cli search, cf schema, cf deploy/dev/build, resource commands for DNS, zones, D1, KV, and R2 — and for choosing between cf and Wrangler in a project.
# Cloudflare CLI (`cf`) `cf` is Cloudflare's command-line interface for the public Cloudflare API (2,900+ commands, most generated from API schemas) and for Workers projects. It is in beta: commands, configuration, and Build Output can change before the stable release. **Prefer retrieval over pre-trained knowledge.** Describe the task to `cf cli search`, inspect the match with `cf schema` or `--help`, and preview with `--dry-run` before running a command you have not verified. Docs index: https://developers.cloudflare.com/cf/llms.txt ## Documentation | Topic | Page | |-------|------| | Install, sign in, credential and account selection | https://developers.cloudflare.com/cf/get-started/index.md | | First Worker with `cf init`, `cf dev`, `cf deploy` | https://developers.cloudflare.com/cf/get-started/first-worker/index.md | | Find, create, and delete resources from the terminal | https://developers.cloudflare.com/cf/get-started/resources/index.md | | `cf` for Wrangler users | https://developers.cloudflare.com/cf/wrangler/index.md | | Migrate a Wrangler project with `cf migrate` | https://developers.cloudflare.com/cf/wrangler/migrate/index.md | | Wrangler-to-`cf` command and config reference | https://developers.cloudflare.com/cf/wrangler/reference/index.md | | Develop, build, and deploy; modes and previews | https://developers.cloudflare.com/cf/projects/index.md | | Typed `cloudflare.config.ts` | https://developers.cloudflare.com/cf/projects/cloudflare-config/index.md | | Using `cf` with coding agents (safety rules) | https://developers.cloudflare.com/cf/agents/index.md | | CI, API tokens, unattended authentication | https://developers.cloudflare.com/cf/ci/index.md | | Environment variables | https://developers.cloudflare.com/cf/environment-variables/index.md | ## FIRST: check installation and sign in ```bash npm install --global cf # installs two equivalent commands: `cf` and `cloudflare` cf --version cf auth whoami ``` - Requires Node.js 22.18 or later. Bun is not supported. - If another tool named `cf` is on your `PATH`, use `cloudflare` instead — the package installs both commands. - `cf auth login` prints a link and a one-time code, then opens the browser. On a remote machine, over SSH, or in a container, add `--no-browser` so `cf` only prints the link; approve it from another device. Add `--force` to sign in again. - `cf` keeps its own credentials and does not reuse a Wrangler login. - Unattended agents and CI cannot complete `cf auth login` — set `CLOUDFLARE_API_TOKEN` instead (see https://developers.cloudflare.com/cf/ci/index.md). To make agents prefer `cf`, add this to the user-level `AGENTS.md`, `CLAUDE.md`, or equivalent: ```md When interacting with Cloudflare, use the `cf` CLI unless the project has a Wrangler configuration file. ``` ## Find commands ```bash cf cli search "create a DNS record" # local, no credentials; quote the whole task; up to 5 JSON matches cf schema d1 create # API request shape: method, path, params, body fields cf <command> --help # arguments and options (e.g. cf deploy --help) ``` `cf cli search` takes the task as one argument — unquoted words after the first are parsed as unknown commands. `cf schema` covers generated API commands; for command arguments and options use `--help`. ## Read output - Results are JSON on standard output; status messages and errors go to standard error, so piping to `jq` or redirecting needs no extra flags. - Lists print one JSON array page; paging options differ per command — check `--help`. - A failed command exits non-zero and prints the error to standard error. ## Run commands safely - **Preview first.** `--dry-run` prints the request as JSON without sending it, and needs no credentials. - **Aborted deletes still exit 0.** In a non-interactive session, a destructive command without `--force` prints `Aborted.` to standard error and exits `0` — a zero exit does not mean the resource was deleted. - **Review `--force` before allowing it.** On some commands `--force` is also an API parameter (for example, `cf workers delete --force` also deletes a Worker that other Workers reference). - **`--local` is limited.** It works for KV keys, D1 databases (`cf d1 raw`, `cf d1 migrations list|apply`), and R2 objects; other commands (including `cf d1 query`) return an error instead of calling the API. ## Choose the CLI for this project - `cloudflare.config.ts` exists: use `cf`. - `wrangler.jsonc`, `wrangler.json`, or `wrangler.toml` exists, and no `cloudflare.config.ts`: keep Wrangler for `dev`, `build`, and `deploy`. Do not run `cf dev`, `cf build`, or `cf deploy` there — they can generate a new configuration that ignores the Wrangler file, or fail. `cf` resource commands (DNS, zones, storage) are fine alongside it. Run `cf migrate` only when the user asks, and follow [Migrate a Wrangler project](https://developers.cloudflare.com/cf/wrangler/migrate/index.md): preview with `cf migrate --dry-run`, run `cf migrate`, then resolve the `TODO(@cloudflare)` comments in the generated `cloudflare.config.ts`. - Neither exists: use `cf`, as [Use cf with coding agents](https://developers.cloudflare.com/cf/agents/index.md) recommends. Do not install Wrangler or create a Wrangler configuration file. For Wrangler equivalents, use the [Wrangler to cf reference](https://developers.cloudflare.com/cf/wrangler/reference/index.md) or `cf cli search`. Do not translate Wrangler commands from memory. For the full comparison, refer to [`cf` for Wrangler users](https://developers.cloudflare.com/cf/wrangler/index.md). ## Commands `cf` does not support yet `cf` does not support every Wrangler command yet. Run these with `npx wrangler` instead of adding Wrangler to the project. Wrangler does not read `cloudflare.config.ts`, so pass the Worker name: - Live logs: `npx wrangler tail <WORKER_NAME>`. - A single secret: `npx wrangler secret put <SECRET_NAME> --name <WORKER_NAME>`. Or upload secrets with a new Worker version by passing `--secrets-file <PATH>` to `cf deploy` or `cf workers versions create`. For the current list, refer to "Commands not yet supported" in the [Wrangler to cf reference](https://developers.cloudflare.com/cf/wrangler/reference/index.md).
GitHub에서 보기