Ecomode deprecated

Hard-deprecated. Do not invoke or route this skill. Use $ultrawork directly for maintained high-throughput execution workflows.

What Ecomode Does

Overrides default model selection to prefer cheaper tiers:

What Ecomode Does NOT Do

• Persistence: Use ralph for "don't stop until done"
• Parallel Execution: Use ultrawork for parallel agents
• Delegation Enforcement: Always active via core orchestration

Combining Ecomode with Other Modes

Ecomode is a modifier that combines with execution modes:

Ecomode Routing Rules

ALWAYS prefer lower tiers. Only escalate when task genuinely requires it.

Agent Selection in Ecomode

FIRST ACTION: Before delegating any work, read the agent reference file:

Read file: references/agent-tiers.md

This provides the complete agent tier matrix, MCP tool assignments, and selection guidance.

Ecomode preference order:

// PREFERRED - Use for most tasks
use /prompts:executor for this scoped task
use /prompts:explore for this scoped task
use /prompts:architect for this scoped task

// FALLBACK - Only if LOW fails
use /prompts:executor for this scoped task
use /prompts:architect for this scoped task

// AVOID - Only for planning/critique if essential
use /prompts:planner for this scoped task

Delegation Enforcement

Ecomode maintains all delegation rules from core protocol with cost-optimized routing:

Background Execution

Long-running commands (install, build, test) run in background. Maximum 20 concurrent.

Token Savings Tips

1. Batch similar tasks to one agent instead of spawning many
2. Use explore (LOW tier) for file discovery, not architect
3. Prefer LOW-tier executor routing for simple changes - only upgrade if it fails
4. Use writer (LOW tier) for all documentation tasks
5. Avoid THOROUGH-tier agents unless the task genuinely requires deep reasoning

Disabling Ecomode

Ecomode can be completely disabled via config. When disabled, all ecomode keywords are ignored.

Set in ~/.codex/.omx-config.json:

{
  "ecomode": {
    "enabled": false
  }
}

State Management

Use the CLI-first state surface (omx state ... --json) for ecomode lifecycle state. If explicit MCP compatibility tools are already available, equivalent omx_state calls are optional compatibility, not the default.

• On activation: omx state write --input '{"mode":"ecomode","active":true}' --json
• On deactivation/completion: omx state write --input '{"mode":"ecomode","active":false}' --json
• On cancellation/cleanup: run $cancel (which should call omx state clear --input '{"mode":"ecomode"}' --json)