Zcf is live · free · last verified 8 Nov 2026 · viability monitor
Zcf
Zero-config CLI that wires Claude Code and Codex into your project and runs the AI-generated code you hand it
Pick ZCF if you use Claude Code or Codex daily and are tired of hand-editing provider configs, output styles and MCP entries in every new repo — `zcf init` plus `zcf config-switch` and the backup/multi-config management cover that, and the six-stage and BMad workflows give you structure the assistants don't ship themselves. It is not a substitute for a real CI runner or a sandboxed execution service: it's JavaScript/Node-flavoured workflow tooling for local use, and the seeded limitations around TypeScript-only codebases and missing audit trails still frame what it can't do. Compare against configuring Claude Code manually by hand before adopting — if you only ever use one assistant on one
Verdict generatedVerified 5d ago · liveness 63/100 · cite: rightaichoice.com/tools/zcf
- Developers who use Claude Code or Codex as their daily driver
- Small teams wanting repeatable, backed-up assistant configuration instead of per-machine dotfiles
- JavaScript/Node.js and frontend-oriented developers
- Users who want a pre-built multi-stage AI development workflow out of the box
- Non-developers who want a GUI or no-code interface
- Enterprise teams needing audit trails, compliance evidence or role-based access control
- Developers who only use a single assistant on a single machine and never re-configure
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip ZCF if you want a GUI-driven or cloud-hosted sandbox rather than a local CLI that configures Claude Code and Codex on your own machine.
ZCF is MIT licensed and free to use, so there is no seat cost to weigh against paid peers. The real cost is the time you spend learning its command surface and workflows; a solo developer on one assistant will get less from that investment than a team standardising Claude Code and Codex setups across machines.
In short
Zcf — Zero-config CLI that wires Claude Code and Codex into your project and runs the AI-generated code you hand it. Best for Developers who use Claude Code or Codex as their daily driver, Small teams wanting repeatable, backed-up assistant configuration instead of per-machine dotfiles, JavaScript/Node.js and frontend-oriented developers. Free to use.
What is Zcf?
Zcf — Zero-config CLI that wires Claude Code and Codex into your project and runs the AI-generated code you hand it. Best for Developers who use Claude Code or Codex as their daily driver, Small teams wanting repeatable, backed-up assistant configuration instead of per-machine dotfiles, JavaScript/Node.js and frontend-oriented developers. Free to use.
ZCF is a zero-config CLI that configures, bootstraps and drives AI coding assistants rather than just running snippets. It handles environment initialization for Claude Code and Codex — API provider setup, output styles, memory files, templates, MCP servers, workflow imports and a status bar — through the `zcf init` command, then keeps that configuration managed with incremental updates, backups and multiple named API profiles. A pre-configured six-stage workflow, a Feature Development (Feat) workflow, BMad agile process, Spec workflow extensions and Git smart commands ship in the box, so you can move from an idea to implemented code inside the assistant without writing your own orchestration. The integration ecosystem covers CCR proxy management, CCometixLine status bar, Context7, Open Web Search, DeepWiki, Playwright and Serena. Commands are aggregated in an interactive menu: `zcf init`, `zcf update`, `zcf ccr`, `zcf ccu`, `zcf uninstall` and `zcf config-switch`. It is a developer tool for people who already live in Claude Code or Codex and want repeatable configuration plus workflow structure, not a GUI, not a multi-language sandbox, and not an enterprise governance layer. Documentation and UI are available in English, Simplified Chinese and Japanese, and the project is MIT licensed.
Key features
- Zero-config environment initialization for Claude Code via `zcf init`
- Zero-config environment initialization for Codex
- API provider preset configuration
- AI output style configuration
- Memory file setup as part of initialization
- Template system with template language separate from AI output language
- MCP service integration
- Pre-configured six-stage workflow
- Feature Development (Feat) workflow
- BMad agile process workflow
- Spec workflow extension
- Git smart commands
- CCR (Claude Code Router) proxy management via `zcf ccr`
- CCometixLine status bar integration
- Usage analysis with `ccu` and ccusage
Behind the verdict
ZCF's real proposition is consolidation. The features page organises everything under four dimensions: environment initialization, configuration management, the workflow system, and the integration ecosystem. In practice that means one `zcf init` run sets up API credentials, output styles, memory, templates, MCP servers, workflows and the status bar for both Claude Code and Codex, instead of you copying JSON between dotfiles. The configuration layer goes further than most tools bother: incremental management, backup strategies, multiple API configurations and a deliberate separation between template language and AI output language — the last one matters if your team writes prompts in English but reads outputs in Chinese or Japanese, and the trilingual UI supports that. The workflow system is the most opinionated part. A six-stage workflow, a Feature Development workflow, BMad agile, Spec extensions and Git smart commands are pre-built and importable, which is where ZCF earns its keep over a shell alias collection. Integration breadth is decent for a small project: CCR for proxy management, CCometixLine for the status bar, plus Context7, Open Web Search, DeepWiki, Playwright and Serena. The command surface stays small and discoverable — init, update, ccr, ccu, uninstall, config-switch, all reachable from an interactive menu, with usage analysis via ccu and ccusage. The honest limits: it is local, it is JavaScript-flavoured, there is no GUI, and there are no enterprise controls such as audit trails or role-based access. Treat it as a well-structured personal and small-team harness for Claude Code and Codex, not as governed infrastructure.
Models under the hood
as of 2026-11-09
Limitations
- ZCF is a local, CLI-first tool aimed at Claude Code and Codex users; there is no GUI, which rules it out for non-developers.
- It is JavaScript/Node-oriented, so teams working primarily in other languages get little from the workflow templates.
- Enterprise concerns — audit trails, role-based access control and compliance reporting — are not part of what the features page describes, so it does not fit regulated environments.
- Because it configures local environments and stores multiple API configurations, you are responsible for securing those credentials yourself.
as of 2026-10-08
Researching Zcf? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Zcf still active?
Zcf is live · free · last verified 8 Nov 2026 · viability monitor.
Viability score
How well maintained and how widely used is Zcf? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What do users say about Zcf?
What people actually say about Zcf — is it worth it?
We scanned public community sources for Zcf on Nov 8, 2026 and could not establish that the discussion we found is about this tool rather than something else sharing its name. Only 1 of the posts we fetched could be positively tied to Zcf. Rather than publish a sentiment score built on the wrong subject, we publish nothing here and re-run the scan.
How we verified this
Every listed fact about Zcf — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 8 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified Zcf 14 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed link health
- — changed integrations, description, use cases, summary, features, limitations, who should skip it, who it suits, setup time, our verdict, pricing fit, switching out, switching in
- — changed SSL certificate
- — changed setup time, description, hidden costs, limitations, switching in, switching out, pricing fit, who should skip it, summary, our verdict, who it suits, features
- — changed domain expiry
- — changed features, summary, description, our verdict
Showing the 6 most recent of 14 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Zcf cost in 2026?
Zcf: Free to use. Pricing last verified 8 Nov 2026.
Where the pricing makes sense
The company stage and team size where Zcf's pricing actually pencils out — and where peers do it cheaper.
ZCF is MIT licensed and free to use, so there is no seat cost to weigh against paid peers. The real cost is the time you spend learning its command surface and workflows; a solo developer on one assistant will get less from that investment than a team standardising Claude Code and Codex setups across machines.
Has Zcf's pricing changed?
No plan price for Zcf has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Zcf?
Pick Zcf if you are Developers who use Claude Code or Codex as their daily driver, Small teams wanting repeatable, backed-up assistant configuration instead of per-machine dotfiles, JavaScript/Node.js and frontend-oriented developers, Users who want a pre-built multi-stage AI development workflow out of the box.
Look elsewhere if you are Non-developers who want a GUI or no-code interface, Enterprise teams needing audit trails, compliance evidence or role-based access control, Developers who only use a single assistant on a single machine and never re-configure, Teams looking for a sandboxed cloud execution service for untrusted code.
Skip it if Skip ZCF if you want a GUI-driven or cloud-hosted sandbox rather than a local CLI that configures Claude Code and Codex on your own machine.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Zcf actually fits — and what changes day-one when you adopt it.
Clones a fresh repo, runs `zcf init`, picks an API provider preset, and gets output styles, memory files, templates and MCP servers configured in one pass instead of pasting JSON by hand.
Outcome: The assistant starts the session already knowing your conventions, and no stray config files land in version control.
Stores two API configurations, then flips between them with `zcf config-switch` before a session and checks consumption afterwards with `ccu`.
Outcome: No more editing dotfiles mid-day, and usage per profile is visible rather than guessed.
Imports the BMad agile process or the six-stage workflow, then runs a feature through the Feat workflow with Git smart commands handling branch and commit hygiene.
Outcome: A repeatable path from spec to code that does not depend on each developer inventing their own prompt sequence.
Use cases
- Set up a fresh Claude Code environment in a new repository with one `zcf init` command
- Keep separate API provider profiles for work and personal projects and switch with `zcf config-switch`
- Run the pre-built six-stage workflow to take a feature from spec to implemented code inside the assistant
- Apply the BMad agile process templates when you want a heavier planning discipline around AI-assisted work
- Wire MCP servers, output styles and memory into Codex without hand-editing config files
- Use Git smart commands to keep commits and branches tidy while an assistant generates code
- Track token and usage patterns across sessions with ccu/ccusage before a heavy build
Setup time & first value
How long it actually takes to get something useful out of Zcf — broken out by persona, not the marketing-page minute.
Installation is a single CLI install; from there `zcf init` runs an interactive menu that walks you through provider, output style, memory, template, MCP and workflow choices, typically a few minutes for a first setup. A second machine is much faster because you can reuse a saved configuration and switch to it directly.
Switching to or from Zcf
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From hand-edited Claude Code config files: run `zcf init` and import your existing settings, then let ZCF manage backups and incremental changes.
- →From a Codex-only setup: run the Codex configuration step during `zcf init` so both assistants share the same environment conventions.
- ↗To plain Claude Code configuration: export your current settings and remove the ZCF-managed files, accepting the loss of backup and multi-config switching.
- ↗To another orchestrator: copy your API providers, templates and output styles across manually, since ZCF keeps them in local configuration you already own.
Integrations
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Zcf”, and we withheld 6: 6 could not be judged, because “Zcf” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Zcf.
Official links
What are the best Zcf alternatives?
The closest alternatives to Zcf we list are ADE, Codecompanion.Nvim and fanbox. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| ADE | Free | Free | — |
| Codecompanion.Nvim | Free | Free | — |
| fanbox | Free | Free | — |
Alternatives to Zcf
View all
ADE
ADE runs Claude Code, Codex, Cursor and other AI coding agents side by side in one synced agentic development environment
Codecompanion.Nvim
CodeCompanion.nvim brings LLM chat, inline edits and CLI agents like Claude Code and Codex into Neovim buffers.
Tools that pair well with Zcf
Common stack mates teams adopt alongside Zcf, with the specific reason each pairing earns its keep.
ADE
ADE runs Claude Code, Codex, Cursor and other AI coding agents side by side in one synced agentic development environment
Codecompanion.Nvim
CodeCompanion.nvim brings LLM chat, inline edits and CLI agents like Claude Code and Codex into Neovim buffers.
fanbox
FanBox is a free macOS terminal with a live diff viewer showing every file your Claude Code or Codex agent writes.
Zcf vs its closest rival
Zcf's closest head-to-head is with Spider Cloud.
Our Zcf vs Spider Cloud verdict written Jul 3, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Frequently asked questions
Categories
Best-of guides
Topics
For makers of Zcf
- Get a Verified Listing for Zcf ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used Zcf? Help shape our editorial sentiment research.