# AI use cases for Mixagents (Utopia-V/mixagents)

Repo: [Utopia-V/mixagents](https://github.com/Utopia-V/mixagents) | Use cases: 3 | Page: https://dedupedai.com/use-cases/utopia-v-mixagents/

A set of three separately installable TypeScript agent packages that let Codex hand subtasks to other model providers and let DeepSeek V4 Pro run more reliably inside the Pi agent.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Hand Codex subtasks to other model providers: https://dedupedai.com/use-cases/utopia-v-mixagents/delegate-subtasks-from-codex-to-other-providers/
- Run DeepSeek V4 Pro in Pi with the DSH mimic: https://dedupedai.com/use-cases/utopia-v-mixagents/run-deepseek-v4-pro-in-pi-with-dsh-mimic/
- Keep the legacy Codex DeepSeek subagent working: https://dedupedai.com/use-cases/utopia-v-mixagents/keep-legacy-codex-deepseek-subagent-running/

## How to hand Codex subtasks to other model providers with Mixagents

Repo: [Utopia-V/mixagents](https://github.com/Utopia-V/mixagents) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Route a subtask from Codex to another provider while Codex stays the controller.

**Who it is for:** A developer using Codex who wants a cheaper or different model to handle a bounded subtask without changing the provider that runs the main session.

**The problem:** Codex is tied to one controller provider, so delegating part of a job to another model normally means switching the whole session.

**The outcome:** Codex keeps its controller and sends selected subtasks to another provider through the MixAgents Broker plugin.

### Steps

1. Run `codex plugin marketplace add Utopia-V/mixagents`
2. Run `codex plugin add mixagents-broker@mixagents`
3. Open packages/broker/README.zh-CN.md (or packages/broker/README.md) and complete the configuration section for your provider
4. Read packages/broker/SECURITY.md and confirm which task and file content will leave your machine
5. Ask Codex to delegate one bounded subtask through the broker and check the returned result before accepting it

### Prompt to paste into your agent

```text
Using the repo Utopia-V/mixagents, install the mixagents-broker package for Codex and configure it for <provider>. Delegate the subtask <subtask description> through the broker and return the provider's result. Verify that the controller in Codex did not change and that you read packages/broker/SECURITY.md before sending any file content.
```

### Caveat

The README says these packages may send task content, file content and tool results to the configured third-party provider, and that those costs are separate from ChatGPT/OpenAI billing.

Risk, credentials: Provider credentials are needed for each third-party provider you configure, so store them carefully and limit their scope.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/utopia-v-mixagents/delegate-subtasks-from-codex-to-other-providers/

## How to run DeepSeek V4 Pro in Pi with the DSH mimic with Mixagents

Repo: [Utopia-V/mixagents](https://github.com/Utopia-V/mixagents) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Use the DSH Minimal persona on Pi's first DeepSeek V4 Pro request, then restore native Pi.

**Who it is for:** A developer who uses Pi with DeepSeek V4 Pro and wants the first request to follow a narrower persona and tool set.

**The problem:** Default Pi sends DeepSeek V4 Pro its full tool catalog from the first request, which the author's frozen Project2 test found less effective than the mimic path.

**The outcome:** Pi sends a modified first request with the DSH Minimal persona and two tools, then returns to the native request and full tool catalog after the first valid response.

### Steps

1. Open packages/pi-dsh-mimic/README.zh-CN.md (or the English README in the same folder) and follow its install section
2. Install the pi-dsh-mimic package into Pi using the method in that install section (inferred, check the README)
3. Start a DeepSeek V4 Pro session in Pi and confirm the first request uses the DSH Minimal persona
4. Read docs/project2-evidence.md to see the frozen Project2 scores before drawing conclusions
5. Run the same task with default Pi and compare results on your own work

### Prompt to paste into your agent

```text
Using the repo Utopia-V/mixagents, install the pi-dsh-mimic package into Pi and run one DeepSeek V4 Pro task on <task description>. Return the output and a short comparison with default Pi on the same task. Verify that the first request used the DSH Minimal persona and that native Pi tools were restored after the first valid response.
```

### Caveat

The README says the Project2 scores (92 default, 96 to 98 in four repeats) come from one frozen task and do not represent a general benchmark.

Risk, reverse engineering: This package modifies the first request Pi sends to DeepSeek V4 Pro, so check the behavior against docs/advanced.zh-CN.md before relying on it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/utopia-v-mixagents/run-deepseek-v4-pro-in-pi-with-dsh-mimic/

## How to keep the legacy Codex DeepSeek subagent working with Mixagents

Repo: [Utopia-V/mixagents](https://github.com/Utopia-V/mixagents) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README

Run the older DeepSeek subagent on Codex 0.148.x or earlier.

**Who it is for:** A developer whose Codex install is still on 0.148.x or earlier and who already relies on the older DeepSeek subagent setup.

**The problem:** The README says the old DeepSeek subagent only applies to Codex 0.148.x and earlier, and that Codex 0.149.0 and later should use the broker instead.

**The outcome:** A working legacy DeepSeek subagent on an older Codex build, with a clear plan to move to the broker when the Codex version changes.

### Steps

1. Confirm your Codex version is 0.148.x or earlier
2. Open packages/codex-deepseek-subagent/README.md and follow its install and use section
3. Read packages/codex-deepseek-subagent/SECURITY.md to understand the security boundary
4. Ask Codex to run one DeepSeek subagent task and check the output
5. Plan to switch to the MixAgents Broker when you upgrade Codex to 0.149.0 or later

### Prompt to paste into your agent

```text
Using the repo Utopia-V/mixagents, install the legacy codex-deepseek-subagent package for a Codex build of version <version> that is 0.148.x or earlier. Run one subagent task on <task description> and return the output. Verify the Codex version first and confirm the security boundary in packages/codex-deepseek-subagent/SECURITY.md.
```

### Caveat

The README marks this package as legacy and says Codex 0.149.0 and later should use MixAgents Broker instead.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/utopia-v-mixagents/keep-legacy-codex-deepseek-subagent-running/
