UNPKG

@every-env/cli

Version:

Multi-agent orchestrator for AI-powered development workflows

67 lines (45 loc) 1.85 kB
# AgentCLI and Pass-through Options The `every` CLI now supports specifying alternative agent CLIs and passing through unrecognized options to the underlying CLI. ## Usage ### Using -a/--agentcli flag You can use the `-a` or `--agentcli` flag to specify which CLI to use instead of the default configured one: ```bash # Use codex instead of claude every review -a codex # Use a custom CLI for planning every plan -a my-custom-cli "implement user authentication" # Use codex for work command every work -a codex task-123 ``` ### Pass-through Options Any options not recognized by `every` CLI will be automatically passed through to the underlying agent CLI: ```bash # Pass model option to codex every review -a codex --model gpt-4 # Pass multiple options every plan -a codex "build feature" --model opus-3 --temperature 0.7 # Combined with review target every review PR-123 -a codex --model latest --verbose # Pass-through works with default CLI too every work "implement caching" --max-tokens 4096 --stream ``` ### Configuration Precedence 1. If `-a/--agentcli` is specified, it overrides the configured CLI 2. If no `-a/--agentcli` is specified, uses the CLI from `.every-env/config.json` 3. If no config exists, defaults to `claude` ### Examples ```bash # Review with codex and specific model every review -a codex --model gpt-4 # Plan with custom options every plan "refactor auth system" --context-window 100000 # Work with verbose output every work task-456 --verbose --debug # Review latest PR with custom model every review -a codex --model latest ``` ## Implementation Details - The CLI extracts all unrecognized options and their values - These options are appended to the agent CLI command - Options from config are combined with pass-through options - The rendered template is always the first argument to the agent CLI