Ecomode

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: docs/shared/agent-tiers.md

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

Ecomode preference order:

// PREFERRED - Use for most tasks
delegate(role="executor", tier="LOW", task="...")
delegate(role="explore", tier="LOW", task="...")
delegate(role="architect", tier="LOW", task="...")

// FALLBACK - Only if LOW fails
delegate(role="executor", tier="STANDARD", task="...")
delegate(role="architect", tier="STANDARD", task="...")

// AVOID - Only for planning/critique if essential
delegate(role="planner", tier="THOROUGH", 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 omx_state MCP tools for ecomode lifecycle state.

• On activation: state_write({mode: "ecomode", active: true})
• On deactivation/completion: state_write({mode: "ecomode", active: false})
• On cancellation/cleanup: run $cancel (which should call state_clear(mode="ecomode"))