qodercli version: 0.1.32
OS: macOS 15 (Darwin 25.3.0), Apple M4
Install: brew install qoderai/qoder/qodercli --cask
/quest is documented as headless-compatible, but it stops at an interactive confirmation prompt that can't be answered in -p mode. No work gets executed.
Reproduce
qodercli -p "/quest Create a simple Python hello world script" -f json -w /tmp/test --max-turns 25
# Also tried with --yolo — same result
qodercli -p "/quest Create a simple Python hello world script" -f json -w /tmp/test --max-turns 25 --yolo
Expected
Per your docs (https://docs.qoder.com/en/cli/user-guide/command#quick-start):
In Headless mode: Prompt-type commands (/init, /review, /quest) can be executed in Headless mode
Quest should plan and execute non-interactively, return JSON, and exit.
Actual
Quest activates, produces a plan, then asks:
Please respond with a number (1-3) or any form of agreement (e.g., "yes", "go", "proceed") to start implementation.
Process exits with "subtype":"success" and "done":true but zero files were created. The confirmation can't be answered since -p only provides one turn of input. --yolo doesn't help either — the confirmation is in Quest's prompt logic, not a system permission.
Current workaround
Plain -p with a detailed prompt (no /quest) executes directly. Works, but loses Quest's subagent orchestration.
Suggestion
- Auto-approve when running headless (detect
-p and skip the confirmation), or
- Add a flag like
--auto-approve to bypass it
Thanks!
qodercli version: 0.1.32
OS: macOS 15 (Darwin 25.3.0), Apple M4
Install:
brew install qoderai/qoder/qodercli --cask/questis documented as headless-compatible, but it stops at an interactive confirmation prompt that can't be answered in-pmode. No work gets executed.Reproduce
Expected
Per your docs (https://docs.qoder.com/en/cli/user-guide/command#quick-start):
Quest should plan and execute non-interactively, return JSON, and exit.
Actual
Quest activates, produces a plan, then asks:
Process exits with
"subtype":"success"and"done":truebut zero files were created. The confirmation can't be answered since-ponly provides one turn of input.--yolodoesn't help either — the confirmation is in Quest's prompt logic, not a system permission.Current workaround
Plain
-pwith a detailed prompt (no/quest) executes directly. Works, but loses Quest's subagent orchestration.Suggestion
-pand skip the confirmation), or--auto-approveto bypass itThanks!