MixAgents Broker plugin
Codex plugin that hands subtasks to subagents on other model providers without changing the main session's provider
- 219 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Sends assignments and context to a third-party model provider, billed separately from an OpenAI subscription
- Takes provider keys through MIXAGENTS_BROKER_CREDENTIALS_JSON and starts workers with access to the workspace, up to write level
- A worker gets the route's maxAccess permissions, and approving a working directory covers all its subfolders
Install
- Works in
Manual install
codex plugin marketplace add Utopia-V/mixagentsAdds the MixAgents marketplace. The plugin can also be installed from the Codex plugins page.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Sends assignments and context to a third-party model provider, billed separately from an OpenAI subscription
- Takes provider keys through MIXAGENTS_BROKER_CREDENTIALS_JSON and starts workers with access to the workspace, up to write level
- A worker gets the route's maxAccess permissions, and approving a working directory covers all its subfolders
This is third-party code. Review the repository files before installing.
What it does
MixAgents Broker installs into Codex as a plugin from the MixAgents marketplace and provides a $broker skill and a local stdio MCP server. A native Codex child agent inherits the parent's provider, so handing a subtask to another model vendor is normally impossible. Broker works around that: the skill picks a configured route, and the MCP server starts a Codex App Server worker on that route's exact provider and model. Routes live in broker.json: provider, model, endpoint, the name of the key variable, tags and a maxAccess ceiling. Every dispatch defaults to read-only. Keys are supplied through MIXAGENTS_BROKER_CREDENTIALS_JSON when Codex starts, and each worker receives only the keys of its route. The controller sees six operations: routes, spawn_agent, send, wait_agent, interrupt_agent and list_agents. Before dispatch the controller reports the chosen provider, model and backend. The parent conversation is not copied: the provider receives the assignment and any explicitly included context. It needs Codex 0.149.0 or newer and Node.js 22.19. The same repository holds the pi-dsh-mimic package for Pi, while the older DeepSeek subagent suits only Codex 0.148 and earlier.
Who it is for. Codex users who want to send part of the work to cheaper or faster models from other providers while keeping control over access.
Good fit when
- The main session runs on one model, and a module review is cheaper on a fast model such as DeepSeek V4 Flash
- A separate low-cost route handles extraction tasks and the agent should pick it on its own
- A subtask must stay read-only, with writing allowed only on an explicitly named route
- Provider keys live in a secrets manager and must stay out of prompts and config files
- Working directories need pre-approval through workspaceRoots so confirmation prompts do not interrupt the work
Not a fit when
- You run Codex older than 0.149.0: the legacy DeepSeek subagent package remains for that
- Task content must not go to third-party providers: the assignment and context travel to the chosen route
- The provider has no compatible Responses API: other models work only with that compatibility
- You need Claude Code or another agent: the plugin is built on Codex App Server
Example request
$broker Use opencode-deepseek-flash to review this module and return the three most important findingsLimitations
- Needs Codex 0.149.0 or newer. Compatibility is verified on Codex 0.151.0-alpha.7.2 with OpenCode Go and the deepseek-v4-flash model; other models must expose a compatible Responses API.
- The assignment and explicit context go to a third-party provider, and billing is separate from a ChatGPT or OpenAI subscription.
- Each route needs its own key. A route without a key is unavailable.
- A community project, unaffiliated with OpenAI, DeepSeek, Pi or OpenCode. After a provider switch in cc-switch the plugin registration has to be restored.
How to disable. Disable the plugin in the Codex plugin list. codex plugin marketplace remove mixagents drops the marketplace. The configuration is in ~/.config/mixagents/broker.json and state in ~/.local/state/mixagents-broker, and both paths are deleted by hand.
FAQ
Why use Broker when Codex has subagents?
A native Codex child agent inherits the parent's provider and cannot move to another. Broker starts a worker on the route's exact provider and model, so the lead session and the subtask can run at different vendors.
How do I install MixAgents Broker?
Run codex plugin marketplace add Utopia-V/mixagents and codex plugin add mixagents-broker@mixagents, or pick the plugin from the MixAgents source on the Codex plugins page. Then start a new task.
Where does my data go?
The assignment and any explicitly included context go to the chosen provider. The parent conversation is not copied automatically. Each worker receives only its route's keys, and they are hidden from shell commands the model generates.
What if the plugin vanishes after a provider switch in cc-switch?
Add the marketplaces.mixagents and plugins blocks to cc-switch's common config snippet and enable applying the common config for every Codex provider. If the plugin is already gone, remove the marketplace with codex plugin marketplace remove mixagents and install again.
Which models and providers work?
Any whose endpoint exposes a compatible Responses API. The tested combination is OpenCode Go with the deepseek-v4-flash model on Codex 0.151.0-alpha.7.2.
Discussion
No questions or reviews yet.
Related
PluginsA local bridge linking Claude Code and Codex in one session so the agents message each other and review each other's work
Codex on Crack splits Codex work across models: the lead plans, a worker implements and the lead reviews the result.
A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
A skill that sets DeepSeek up as a native subagent of desktop Codex on macOS and Windows and verifies request routing
A plugin that syncs Claude Code, Codex CLI and Antigravity on one project and lets them hand work to each other.
Awesome Codex Subagents
awesome-codex-subagents
Role templates for Codex: over 130 ready descriptions of specialized subagents by category including security roles
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| MixAgents Broker (this card) | no | 219 | |
| codex-deepseek-subagent | no | 394 | sets up DeepSeek as a built-in subagent of desktop Codex and fits older versions only |
| delegate-skills | no | 2,597 | delegates a task to a separate CLI agent rather than a Codex worker on another provider |
README in short
The front page, in Chinese with an English version, lists three packages: Broker for Codex 0.149 and newer, the legacy DeepSeek subagent for Codex 0.148 and older, and pi-dsh-mimic for DeepSeek V4 Pro in Pi. For the last, a frozen-task result is given: 92 for stock Pi against 96–98 over four runs with the mimic, and the author notes it is not a general benchmark. The author asks you to read SECURITY.md before installing.