UltraCode Shim

Use Claude Code's UltraCode mode (xhigh effort + the Workflow/deep-reasoning
harness) with any model you already pay for — pick it live from the /model
menu.

One icon. Open Claude Code, type /model, and choose any backend you've set up —
all running with the full UltraCode harness. Your normal Claude Code install is
left untouched.

The example config ships ready-to-use entries for GPT‑5.5 (Codex login),
MiniMax‑M3, MiMo v2.5 Pro, DeepSeek V4 Pro/Flash, Step Flash,
Ollama Cloud, OpenCode Go, OpenRouter, Requesty, and local models — keep
the ones you have a plan for, delete the rest. (Cursor's Composer needs the
cursor-agent CLI and isn't HTTP-based — see
docs/ADD_A_MODEL.md.)

How it works
How is this possible? At the API level, "UltraCode" is just
effort=xhigh + adaptive thinking + a big max_tokens + one system reminder —
there is no secret model. The proxy adds that envelope to every request, so any
backend gets the UltraCode treatment. Full breakdown (with the reverse‑engineering
evidence) in docs/HOW_IT_WORKS.md.

Orchestrator + Worker: two models, one workflow 🪄

Claude Code's /model menu is single-slot — and its dynamic-workflow engine
quietly issues most of its background/sub-agent traffic as the *stock* model
(claude-opus-4-8) no matter what you pick. So the dozens of parallel workers
that do the bulk of a workflow don't follow your selection (and can bill a model
you didn't choose).

This proxy turns that single slot into two. The launcher opens a two-column
selector before Claude Code starts: choose an orchestrator (the main
interactive loop) on the left and a worker (every Workflow/Task sub-agent) on
the right. The same choices are also available later in /model: for every model
you configure, the proxy auto-adds a Worker →  entry.

- Pick one model (or…