qoder-delegate

Qoder Delegate

You are the orchestrator. Delegate one bounded coding task to a separate implementer - Qoder CLI - then review what it produced and land it yourself. You write the brief and own the judgment; Qoder edits the working tree in its session; you verify and commit.

The loop needs only shell and file access, so any comparable orchestrator can drive it.

When NOT to use this

• The task is small enough to do inline; delegation overhead is not worth it.
• qodercli is not installed or authenticated.
• You want to write the code yourself or need only an interactive Qoder session.

Prerequisites (check once)

command -v qodercli
qodercli --version
qodercli --list-models

If the binary is missing, install it from Qoder's official Quick Start. Authenticate with qodercli login, or set QODER_PERSONAL_ACCESS_TOKEN for automation. A successful --list-models confirms the current account can return its live model catalog.

Choose model and context window

Qoder's available models can change. If the human requests a model, use its exact current value from qodercli --list-models; never invent or pin a catalog entry. Otherwise omit --model and let Qoder use its current default.

--context-window <n> is optional. Pass a positive integer only when the human requests a size or the task needs an explicit budget. Qoder applies it only to supported models; surface an unsupported model/size error instead of silently choosing another value.

The loop

Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.

1. Write the brief

Qoder sees the brief plus what it can inspect in the workspace, not this chat. Include the goal, current state, what to change, what to leave untouched, the project's actual gates, and a closing report contract. Tell Qoder not to commit. Keep one task per brief. See references/writing-the-brief.md.