qckfx
command is the primary interface for running AI agents from the command line. It supports various options for model selection, configuration, session management, and more.
Syntax
Options
Agent Configuration
Path to an agent definition JSON file. Supports smart path resolution:
- Direct file paths (relative or absolute)
- Auto-appends
.json
extension if missing - Looks in
.qckfx/
directory for shorthand names
Model to use for this execution. Overrides the default model in agent configuration.
API Configuration
Override the
LLM_API_KEY
environment variable for this execution.Override the
LLM_BASE_URL
environment variable for this execution.Session Management
Continue the most recent session for the current working directory. Sessions are automatically saved after each execution.
Sub-agents
Add one or more sub-agent tools for this execution. Sub-agents are resolved from
.qckfx/sub-agents/<name>.json
.Output Control
Suppress all output except the final response or errors. Perfect for CI/CD environments and GitHub Actions where you want clean, minimal output. When using this flag, a prompt must be provided as arguments since interactive mode is disabled.
Validation
Validate an agent definition file and exit. Does not execute the agent.
Prompt
The prompt to send to the agent. If not provided, the CLI will enter interactive mode.
Commands
init
Theinit
command sets up a new project with default agent configurations:
- Creates a
.qckfx
directory in the current working directory - Installs essential agent configurations used by the qckfx development team:
advanced-agent.json
- General-purpose coding agent with browser sub-agent, uses OpenAI o3 for orchestration and Claude Code for implementationagent-editor.json
- Specialized for editing system prompts in agent configuration filescommit.json
- Helps write good commit messagessub-agents/browser.json
- Codebase research capabilities using GPT-4.1-nano for cost-efficient local file analysissub-agents/coder.json
- Advanced coding assistance
The
init
command is the fastest way to get started with qckfx. It gives you the same agent configurations that the qckfx team uses for daily development.If a
.qckfx
directory already exists, the init
command will overwrite existing files with the same names.Examples
Project Initialization
Basic Usage
Model Selection
Agent Configurations
Session Management
Sub-agents
API Configuration
Quiet Mode for CI/CD
Interactive Mode
When you runqckfx
without a prompt, it enters interactive mode:
Path Resolution
The CLI uses smart path resolution for agent configurations:- Direct Path: If the file exists as specified, use it
- Auto Extension: If missing
.json
, append it and check again - Convention Directory: Look in
.qckfx/<name>.json
- Fallback: Return the direct path (will cause error if not found)
Exit Codes
Code | Meaning |
---|---|
0 | Success |
1 | Error (validation failed, execution error, etc.) |
Error Handling
The CLI provides clear error messages for common issues:- Invalid Configuration: Shows validation errors with specific details
- Missing Files: Reports which files couldn’t be found
- API Errors: Displays model provider error messages
- Session Errors: Warns about session loading failures but continues
If session loading fails when using
--continue
, the CLI will warn you but start a fresh session instead of failing.Performance Tips
- Use
--continue
to maintain context across multiple interactions - Leverage sub-agents for specialized tasks instead of complex prompts
- Validate configurations with
--validate
before deployment - Use shorter model names when possible (e.g.,
claude-sonnet-4
vs full model IDs) - Use
--quiet
in CI/CD environments to reduce log noise and improve performance