prime-workerlisted

# Prime Worker ## Overview `prime-agent` is installed locally and runs models from the user's **OpenCode Go subscription**. Because that is a subscription, per-token price is *not* the thing to optimize — the real axes are context window, latency, and how much the model can be trusted with the task. **A worker is a named directory.** `~/.claude/prime-workers/<name>/` holds exactly one session `.jsonl` plus a `worker.env` recording the `--cwd` and `--model` it was spawned with. The name is the only handle you ever need. Drive it with `scripts/pw`. Do not hand-roll `prime-agent` invocations — the raw CLI has a trap that silently breaks continuity (see Failure Modes). ## Choosing the Model: Ask First **Ask the user which model to use before spawning a worker.** Default to `deepseek-v4-flash`, but present the choice — the user tracks which models are performing well and that changes faster than this file does. Ask **once per worker, at spawn**. `pw say` reuses the recorded model silently; do not re-ask every turn. Use `AskUserQuestion` with `deepseek-v4-flash` first and marked `(Recommended)`. Sensible option set: | model | ctx / max-out | fits | |---|---|---| | **`deepseek-v4-flash`** *(default)* | 1M / 384K | Default for everything. Biggest output budget on the subscription. | | `mimo-v2.5` | 1M / 128K | Faster and lighter; accepts images. Good when the work is mechanical. | | `mimo-v2.5-pro` | 1M / 128K | Same shape, more capable. | | `gpt-5.6-luna` | 1.05M / 128K | S