zcf
AgentFreeZero-Config Code Flow for Claude code & Codex
Capabilities14 decomposed
unified dual-tool configuration abstraction
Medium confidenceProvides a single CLI interface that abstracts configuration complexity for two distinct AI coding tools (Claude Code VS Code extension and Codex terminal CLI) through tool-specific adapter pattern. Uses TOML-based configuration files with tool-specific managers that translate unified settings into tool-native formats, eliminating the need for users to manually configure each tool separately. Implements automatic platform detection and intelligent defaults to minimize required user input.
Implements a dual-tool adapter architecture where a unified configuration schema is translated into tool-specific formats via separate manager classes (Claude Code Configuration Manager and Codex Configuration Manager), rather than requiring users to maintain separate configs or learn each tool's native configuration system
Eliminates configuration duplication and context-switching overhead that developers face when managing Claude Code and Codex independently, providing single-source-of-truth configuration management
multi-profile api provider switching with presets
Medium confidenceManages multiple API provider configurations (OpenAI, Anthropic Claude, etc.) with instant switching capability through a preset system stored in TOML files. Users define named profiles containing API keys, model selections, and provider-specific settings, then switch between them via CLI commands without reconfiguring. The system validates API credentials and maintains provider-specific defaults for each tool adapter.
Implements a preset system with named profiles that persist across sessions, allowing instant provider switching via `config-switch` command without re-entering credentials, combined with provider-specific validation and model mapping for each tool adapter
Faster than manually editing environment variables or configuration files for each provider switch, and more secure than hardcoding credentials in shell profiles
non-interactive configuration mode for ci/cd automation
Medium confidenceSupports fully automated configuration via environment variables and command-line flags without interactive prompts, enabling ZCF integration into CI/CD pipelines and automated deployment scripts. The system reads configuration from environment variables (e.g., `ZCF_API_KEY`, `ZCF_PROVIDER`, `ZCF_LANGUAGE`) and applies them without user interaction. Non-interactive mode validates all required parameters before proceeding and fails fast with clear error messages if configuration is incomplete.
Implements environment variable-driven configuration with explicit `--non-interactive` flag that disables all prompts and validates all parameters before execution, enabling reliable CI/CD integration
Provides explicit non-interactive mode with environment variable support, making ZCF suitable for CI/CD automation versus tools that default to interactive mode and require workarounds
uninstall and cleanup system
Medium confidenceProvides complete uninstallation capability that removes ZCF package, configuration files, and backup history with optional preservation of user data. The `uninstall` command removes npm package, deletes configuration directories, and cleans up any created symlinks or PATH modifications. Users can choose to preserve configurations for later restoration or completely remove all traces of ZCF from their system.
Implements comprehensive uninstall with optional configuration preservation, removing not just npm package but also configuration directories, backups, and PATH modifications in single command
Provides clean uninstall with optional data preservation, eliminating manual file cleanup that other tools require
toml-based configuration file management with schema validation
Medium confidenceUses TOML format for all configuration files with structured schema defining valid keys, types, and constraints. The system validates configuration files against schema on load, providing clear error messages for invalid configurations. Configuration is organized hierarchically (global ZCF config, tool-specific configs, workflow configs) with inheritance and override mechanisms. The system supports configuration comments and provides default values for optional keys.
Implements TOML-based configuration with schema validation on load, providing both human-readable format and programmatic validation, combined with hierarchical organization supporting tool-specific and workflow-specific overrides
TOML format is more readable than JSON and supports comments, while schema validation catches configuration errors earlier than runtime discovery
language and model configuration per tool
Medium confidenceAllows per-tool configuration of programming language support and AI model selection, with language-specific defaults and model-specific parameters. Users can specify which programming languages each tool should support, set default models for different task types, and configure language-specific prompts and output formatting. The system maintains language-to-model mappings and validates that selected models are available from configured API providers.
Implements per-tool language and model configuration with language-to-model mappings and language-specific prompt/output formatting, enabling specialized tool behavior per programming language
Provides language-aware model selection and formatting, versus generic tools that apply same model and formatting to all languages
zero-configuration initialization with platform detection
Medium confidenceAutomatically detects the user's operating system (Windows, macOS, Linux, Termux, WSL) and installs ZCF with platform-appropriate defaults and paths. The `init` command performs one-time setup including dependency validation, configuration directory creation, and interactive prompts for essential settings (API keys, preferred language, default models). Uses environment variable detection and file system checks to infer user preferences and minimize required input.
Combines OS-level platform detection (via Node.js `os` module) with environment variable inspection and file system probing to infer user context, then generates platform-specific configuration paths and defaults without requiring manual intervention
Eliminates manual path configuration and OS-specific setup steps that plague multi-platform CLI tools, providing true zero-configuration experience on Windows, macOS, Linux, Termux, and WSL
workflow template system with customizable output styles
Medium confidenceProvides pre-built workflow templates (SixStep Workflow, Git Workflow, BMad Enterprise Workflow) that define multi-step AI coding processes with customizable output styles and AI personalities. Templates are stored as configuration files that specify prompt sequences, tool invocations, and output formatting rules. Users can create custom workflows by extending template structure, and output styles control how AI responses are formatted (tone, detail level, structure). The system uses i18next for internationalization of workflow prompts and output styles.
Implements a template-based workflow system where each workflow is a TOML configuration defining step sequences, output styles, and AI personalities, combined with i18next-based internationalization allowing workflows to be localized across English, Chinese, and Japanese without code changes
Provides pre-built enterprise workflows (BMad, SixStep, Git) that encode best practices, eliminating the need for users to manually orchestrate complex multi-step AI coding processes like other tools require
mcp service one-click configuration and integration
Medium confidenceProvides automated setup for Model Context Protocol (MCP) services through a configuration interface that handles service discovery, credential management, and tool-specific integration. Users select desired MCP services from a menu, and ZCF automatically configures them for both Claude Code and Codex with minimal manual intervention. The system manages MCP service credentials, validates service connectivity, and exposes MCP capabilities to the underlying AI tools through standardized integration points.
Implements a service discovery and auto-configuration system for MCP that abstracts provider-specific setup details, automatically translating a single MCP service configuration into tool-specific formats for both Claude Code and Codex adapters
Eliminates manual MCP configuration for each tool separately, providing single-command setup that works across both Claude Code and Codex versus requiring separate MCP configuration per tool
version management and automatic update detection
Medium confidenceMonitors ZCF package version against npm registry and notifies users of available updates through the `check-updates` command. Implements semantic versioning validation and provides `update` command for in-place package upgrades with automatic configuration migration. The system maintains version compatibility checks for dependent tools (Claude Code, Codex) and validates configuration file compatibility across versions.
Implements version checking against npm registry with semantic versioning validation, combined with automatic configuration schema migration that preserves user settings across version upgrades
Provides proactive update notifications and automatic configuration migration, reducing friction compared to manual npm update and manual configuration file repairs
multi-language internationalization with i18next
Medium confidenceProvides full internationalization support for English, Chinese (Simplified), and Japanese through i18next framework integration. All CLI prompts, error messages, workflow templates, and output styles are translatable via JSON translation files organized by language code. The system auto-detects user locale from OS settings or allows explicit language selection via configuration, then loads appropriate translation files at runtime for all user-facing text.
Uses i18next framework with separate translation files per language, enabling complete UI localization including workflow templates and output styles without code duplication, with automatic OS locale detection for seamless user experience
Provides true multi-language support with translated workflows and output styles, not just UI strings, making ZCF genuinely usable for non-English speakers versus tools with English-only workflows
backup and recovery system for configurations
Medium confidenceAutomatically creates timestamped backups of configuration files before modifications and provides recovery mechanism to restore previous configurations. The system maintains a backup history in a dedicated directory with metadata about each backup (timestamp, change description, version). Users can list available backups and restore to any previous state via CLI commands, with validation to ensure restored configurations are compatible with current ZCF version.
Implements automatic pre-modification backups with timestamped files and metadata, combined with version-aware restoration that validates compatibility before restoring, providing point-in-time recovery without manual intervention
Eliminates manual configuration backups and provides version-aware restoration, reducing risk of configuration corruption compared to manual file management
cli command routing and interactive menu system
Medium confidenceImplements a command-based CLI interface with both direct command invocation and interactive menu navigation. The router dispatches commands to appropriate handlers based on command name, with support for both interactive prompts and non-interactive flag-based invocation. The menu system provides hierarchical navigation through available commands with descriptions, enabling discoverability for users unfamiliar with CLI options. Commands include `init`, `update`, `menu`, `config-switch`, `check-updates`, `uninstall`, `ccr`, and `ccu`.
Implements dual-mode command interface supporting both direct CLI invocation and interactive menu navigation through same command handlers, with automatic TTY detection to choose appropriate mode
Provides both power-user CLI efficiency and novice-friendly interactive menus in single tool, versus tools that force choice between one or the other
external tool integration (ccr, cometix, ccusage)
Medium confidenceProvides integration points for external tools: CCR (Claude Code Router) for intelligent tool selection, Cometix for additional code analysis, and CCUsage for API usage tracking. The system detects installed external tools and exposes their functionality through ZCF commands (`ccr` and `ccu`), with automatic credential passing and output formatting. Integration is optional; ZCF functions without external tools but gains enhanced capabilities when they are installed.
Implements optional integration layer that detects external tools via PATH and exposes their capabilities through ZCF commands, with automatic credential passing and output normalization, allowing modular enhancement without core dependency
Provides optional tool routing and usage tracking without requiring external tools, versus standalone tools that force adoption of entire ecosystem
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with zcf, ranked by overlap. Discovered automatically through the match graph.
Multi (Nightly) – Frontier AI Coding Agent
Frontier AI Coding Agent for Builders Who Ship.
cc-switch
A cross-platform desktop All-in-One assistant tool for Claude Code, Codex, OpenCode, openclaw & Gemini CLI.
Toolbase
** - Desktop application that manages tools and MCP servers with just a few clicks - no coding required by **[gching](https://github.com/gching)**
XcodeBuildMCP
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Roo Code
Enhanced Cline fork with custom modes.
Multi – Frontier AI Coding Agent
Frontier AI Coding Agent for Builders Who Ship.
Best For
- ✓developers using both Claude Code and Codex simultaneously
- ✓teams standardizing on multiple AI coding tools
- ✓users managing complex multi-provider setups
- ✓developers evaluating multiple LLM providers
- ✓teams with separate API budgets per project
- ✓researchers comparing model outputs across providers
- ✓DevOps engineers deploying ZCF at scale
- ✓CI/CD pipeline builders integrating ZCF
Known Limitations
- ⚠Abstraction layer adds complexity if users need tool-specific advanced features not exposed by ZCF
- ⚠Configuration changes require CLI invocation rather than direct file editing for consistency
- ⚠Limited to the two supported tools; cannot manage other AI coding environments
- ⚠API keys stored in plaintext TOML files; requires OS-level file permissions for security
- ⚠No built-in credential rotation or expiration management
- ⚠Provider switching requires CLI invocation; no automatic fallback if primary provider fails
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
Repository Details
Last commit: Apr 2, 2026
About
Zero-Config Code Flow for Claude code & Codex
Categories
Alternatives to zcf
Are you the builder of zcf?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →