dl

Hand a sub-task to a brand-new session that runs on its own — in another project directory and/or on another engine (codex, deepseek, kimi, glm, ollama, claude). You do NOT wait for it. You get a receipt back at once; the child notifies the user when it finishes. Use it when the work belongs in another directory, suits another engine, or simply should not block this conversation. For parallel work inside this same repository, your own subagents are usually the better tool. ## 1. Delegate Decide: target `cwd` (absolute project directory), `engine`, a short `title`, and the task. Write the task as a self-contained brief — the child sees none of this conversation. Put anything longer than a line or two in a brief file, so no JSON escaping is involved: ```bash BRIEF=$(mktemp /tmp/cockpit-brief.XXXXXX) cat > "$BRIEF" <<'EOF_BRIEF' <goal, context the child needs, constraints, what "done" looks like> EOF_BRIEF curl -sS --fail-with-body -X POST "{{BASE_URL}}/api/sessions/delegate" \ -H "Content-Type: application/json" \ -H "x-cockpit-run-id: $COCKPIT_RUN_ID" \ --data-binary @- <<EOF_JSON {"cwd": "/abs/target/project", "engine": "codex", "title": "<short label>", "briefPath": "$BRIEF"} EOF_JSON ``` - `engine` is inherited from the session you are running in when omitted — that is what the `x-cockpit-run-id` header above is for, so always send it. Spell `engine` out only when the task should run somewhere else, which for `/dl` it often should. Claude when the calling ...