mixagents: Skill for Codex

Maintain Mixagents

The repository contains two independent integrations and the provider-neutral Broker project. Select the affected package first and keep its lifecycle, distribution surface, and evidence separate from the others. Do not introduce a shared abstraction merely because packages involve agents, providers, or similar transports.

MixAgents Broker

Read the Broker product and status owner, its accepted backend and lifecycle policy, its accepted controller contract, its local project instructions, and its security owner before changing routing, worker lifecycle, provider data, credentials, permissions, tools, or paid-call behavior.

Broker exists to schedule workers across model providers without globally switching the controller's provider. Preserve that parent outcome rather than reducing the package to a DeepSeek-specific adapter or a one-shot model tool. Keep these boundaries explicit:

• Name the effective controller, provider, model, backend, worker identity, and lifecycle owner truthfully.
• A backend owns only the lifecycle semantics it can actually provide. Never present an externally managed worker as a native Codex child.
• Provider selection does not grant tool, filesystem, network, or mutation authority. The effective harness and environment own those permissions and side effects.
• Missing capability, credentials, or transport fails closed. Never silently change provider, model, backend, or task carrier.
• Prefer native Codex children only when the full cross-provider capability contract passes; otherwise select the qualified App Server fallback before dispatch. Never migrate a live Agent as an implicit retry.
• Route from a versioned qualification record. Do not trial-spawn a native child per Agent; requalify only when the Codex build, plugin, route, credential identity, environment, permissions, or relevant protocol changes. Start with offline checks, and require explicit authorization for a live canary.
• Promote a fully evidenced qualification atomically for new Agents only. Demote the affected key on a provider, transport, identity, or lifecycle contract violation, not an ordinary task failure. Reuse the same creation through App Server only after proving native accepted no child and began no external effect; ambiguity must not create a second worker.
• Preserve the native-sized Agent thread contract: routes, spawn_agent, send, wait_agent, interrupt_agent, and list_agents; a small status vocabulary; and final text or an error. Do not reintroduce a generic Job, revision, pending-action, cancellation, artifact, or release protocol without a demonstrated consumer that App Server threads cannot serve.
• Completion, failure, and interruption end the current turn, not the Agent thread. Follow-up input may start another turn on the same App Server thread.
• App Server owns managed thread history, turn results, and recovery. Persist only non-secret runtime metadata that cannot be reconstructed from it.
• Scope runtime processes by route and effective access. The $broker Skill routes qualified native Agents through Codex collaboration tools directly; the local STDIO MCP server owns App Server-backed Agents.
• MCP tools accept only preconfigured routes, never inline credentials, endpoints, headers, or provider definitions.
• Send only the complete assignment and context explicitly selected for the worker. Managed workers use the supplied checkout directly; the controller serializes overlapping writers or prepares a Codex worktree before dispatch.
• Relay transient non-secret approval or user-input requests through the host only when it advertises elicitation during an associated call. Otherwise decline explicitly; never collect credentials or expand route authority.
• Treat App Server turn/interrupt as a local turn result. State the provider compute/billing limitation instead of inventing a remote-cancellation claim.
• Treat probes as disposable evidence; record only decision-grade results in their durable project owner.