Why this matters for CueSpec#
The current Mac companion observes Codex tasks and lets you reply in their context. A list of several tasks is not proof that CueSpec created the agents, assigned models or coordinates their work automatically.
Future multi-agent and multi-LLM ideas need separate scope: supported providers, task identity, assignment, cost visibility and authorization. A model selector alone would not solve task coordination; an agent dashboard alone would not establish provider compatibility.
Use current controls honestly#
Choose the intended conversation and use the controls actually available in its host environment. Do not assume CueSpec automatically selects a better model when a task becomes difficult or busy.
For a workflow discussion, state whether you need to see progress, send a reply, create new work, change a model or coordinate dependencies. Those are distinct capabilities and should have distinct documentation. This separation keeps software positioning clear while leaving room for the broader product direction.