v0.1.0 to v0.1.0

---

name: daemon-backend-qwen-code

description: >

Nested daemon-cli-backends reference for the Qwen Code (`qwen-code` /

`qwen`) daemon backend's flag surface. Read this only when a daemon task

needs Qwen-specific CLI flags (model selection, provider tunables): it

routes you to the installed CLI's live help via shell and shows how to

translate that help into the generic `backend_options` mechanism. It is

not a flag catalog.

version: 0.1.0

related_files:

- src/lingtai/tools/daemon/manual/reference/cli-backends/SKILL.md

- src/lingtai/tools/bash/manual/reference/bash-qwen-code/SKILL.md

maintenance: |

Tracks the Qwen Code daemon backend flag-discovery topic it documents; update when that integration changes.

---

# Qwen Code Daemon Backend — Flag Discovery Entrypoint

## Discover flags from the installed CLI

1. Load `shell-manual` (its nested `reference/bash-qwen-code/SKILL.md` has

broader Qwen Code CLI context).

2. Run, in bash: `qwen --version` and `qwen --help`. The daemon backend wraps

the top-level `qwen` binary directly — it spawns

`qwen --yolo <backend_argv...> -p <prompt>`, no subcommand — so

`qwen --help` is the whole relevant flag surface. These are local

read-only commands; no session is started.

## Example: model selection via the generic route

Your options land between the harness-owned `--yolo` and the final

`-p <prompt>` (argv placement is pinned by

`tests/test_daemon_backend_options.py::test_qwen_code_cmd_appends_backend_argv_before_prompt`):

```jsonc

{

"backend": "qwen",

"tasks": [{

"task": "Implement and validate the change.",

"tools": [],

"backend_options": {

"model": "qwen3-coder-plus"

}

}]

}

// argv: qwen --yolo --model qwen3-coder-plus -p <prompt>

```

## Harness boundary

Qwen Code reserves `--prompt`/`-p`, `--yolo`/`-y`, and `--approval-mode`:

they drive LingTai's non-interactive headless harness, and passing any of

them in `backend_options` refuses the whole batch before spawn. Beyond that,

do not re-point harness-owned surfaces: the daemon writes a per-run

`<run>/qwen-daemon-settings.json` (carrying `mcpServers.daemon_common` plus

parent stdio MCP registrations) and injects it via the

`QWEN_CODE_SYSTEM_SETTINGS_PATH` environment variable — overriding settings

paths silently breaks completion enforcement.

Plan flags at emanate time: `daemon(action='ask')` is intentionally

unsupported for this backend (no stable headless resume contract), so there

is no later chance to adjust a running session. Output parsing is verbatim

text — Qwen Code headless mode has no machine-readable event stream here, so

stdout/stderr are recorded as-is and the result is the final stdout text;

the `daemon_common` `finish(status="done")` call is still required for

success.