-
Notifications
You must be signed in to change notification settings - Fork 18
Open
Description
Bug
Nightshift v0.3.1 calls codex --quiet [prompt] but Codex CLI 0.98.0 no longer has a --quiet flag. The non-interactive mode is now codex exec [prompt].
Error
nightshift run -p ./my-project -t lint-fix --yes --verbose
--- Running: Linter Fixes (via codex) ---
FAILED: agent execution: exit status 2
Exit status 2 is a CLI argument parsing error:
$ codex --quiet "test"
error: unexpected argument '--quiet' found
tip: to pass '--quiet' as a value, use '-- --quiet'
Usage: codex [OPTIONS] [PROMPT]
Expected
Nightshift should use codex exec subcommand for non-interactive execution:
# Current (broken):
codex --quiet --dangerously-bypass-approvals-and-sandbox "prompt"
# Expected (works):
codex exec --dangerously-bypass-approvals-and-sandbox "prompt"Environment
- nightshift: v0.3.1
- codex-cli: 0.98.0
- macOS 15.5 (Apple Silicon)
Workaround
Created a wrapper script that translates --quiet → exec:
#!/bin/bash
args=()
for arg in "$@"; do
if [ "$arg" = "--quiet" ]; then
args+=("exec")
else
args+=("$arg")
fi
done
exec codex "${args[@]}"Would also be helpful to expose a binary_path or cli_path config option for providers (the Go code has WithCodexBinaryPath() but it's not exposed in YAML config).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels