Output for scripts and agents: empty stdout with exit 0, `--version` not machine-readable, agent detection changes nothing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start by reproducing the listed cf commands and the CLAUDECODE=1 cf d1 list comparison, using the linked FINDINGS.md and findings/ as context. Trace the CLI entry points for list output, version output, and agent detection. Done means empty lists emit [], version output includes a bare semver, and agent detection produces compact JSON or the documented claim is removed.
Written by the indexing model from the issue text.
Description
cf version: 1.0.0-beta.5, macOS
Three things that break scripts and agents parsing cf's output:
- Empty stdout with exit 0.
cf zero-trust access applications cas listprints nothing (0 bytes) and exits 0. Other lists print JSON ([]when empty), socf ... | jqfails only on this one. cf --versionisn't machine-readable. It prints🍊☁️ cf · v1.0.0-beta.5plus a box rule. There's no bare semver, which scripts need to pin or compare versions (--version --quiet, orcf version --json).- Agent detection doesn't change the output.
CLAUDECODE=1 cf d1 list | wc -cgives 4,293 bytes, byte-identical to running without it, still pretty-printed. The launch post describes condensed output for agents.
Expected:
- every list prints JSON,
[]when empty; - a bare version output;
- compact JSON when an agent is detected, or remove the claim.
Found while evaluating cf for a dev workflow: https://github.com/joeblew999/cf-cli-test (FINDINGS.md, findings/).
- Dominant language
- TypeScript
- Stars
- 916
- Forks
- 53
- Avg merge
- 18h 31m
- Merged PRs (30d)
- 172
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudflare/cf
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/cf#344 ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#262 ·
Maintainers usually reply within 1 day
-
`cf dev` rejects `--port` and `--host` for Vite projects, including the `cf init` templatePossibly taken @jamesopstad claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#223 · 2 assignees ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cloudflare/cf#179 ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 4/5 3-5 days Newbie friendliness 58/100
cloudflare/cf#347 ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
mobile-next/mobile-mcp#526 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 73/100
redhat-developer/rhdh-plugin-export-overlays#4470 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anthropics/anthropic-sdk-typescript#1273 ·
Maintainers usually reply within 10 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CopilotKit/OpenBot#815 ·
Maintainers usually reply within 1 day