Problem
Many automation workflows (CI/CD pipelines, batch processing, third-party tools like `ooo`) need to invoke Qoder’s AI model programmatically from scripts or other CLI tools. Currently, Qoder only offers a GUI-based desktop experience — there is no way to run a one-shot prompt from the command line, pipe input/output, or integrate Qoder into shell scripts and automation pipelines.
For example, the open-source tool `ooo` (ouroboros-ai) uses `codex` or `claude` CLI as its LLM backend for quality assessment (`ooo qa`). Users who prefer Qoder’s models cannot use `ooo` with Qoder because there is no headless CLI entry point.
Solution
Add a `qoder exec` (or `qodercli`) command that provides a non-interactive, headless execution mode:
```
Basic usage: read prompt from stdin, output response to stdout
echo “Summarize this file” | qoder exec --model qwork-auto
Pass prompt as argument
qoder exec --prompt “Explain this error log” --model qwork-advanced
Pipe-friendly: no GUI, no TUI, just text in → text out
cat report.md | qoder exec --model qwork-auto --system “You are a concise summarizer”
Timeout control
qoder exec --prompt “…” --timeout 120
Context directory (like QoderWork’s workspace)
qoder exec --prompt “Review this code” --context-dir ./src
```
Key design points:
- Exit after one response (no interactive loop)
- stdout = model response, stderr = diagnostics/errors
- `–model` flag to select model tier
- `–timeout` for external process control
- `–context-dir` to provide file system context
- `–system` for system prompt override
- Return non-zero exit code on errors
Use Case
- CI/CD pipelines: automated code review, commit message generation, PR summarization
- Third-party CLI tools: `ooo`, `aider`, and similar tools could use Qoder as a backend
- Batch processing: run Qoder on hundreds of files in a script loop
- Developer workflows: integrate Qoder into shell scripts, Makefiles, git hooks
- Scheduled tasks: cron jobs that invoke Qoder for periodic analysis
Priority
Medium - Important improvement
Additional Info
Similar features in other products: `claude` CLI (Anthropic), `codex` CLI (OpenAI), `gemini` CLI (Google). This is a common pattern for developer-facing AI platforms.