Mercury Agent Teases Copilot, Codex Support

This is a smart move if Mercury wants to be the orchestration layer instead of just another agent wrapper. Provider choice matters more than brand loyalty when teams care about cost, policy, and task fit.

• –Copilot and Codex support makes Mercury more useful as a neutral control plane for agent work
• –Users can choose providers by task, budget, or compliance instead of rewriting workflows
• –The hard part is operational, not marketing: auth, rate limits, and provider-specific behavior have to stay invisible
• –If Mercury keeps its permission and daemon model intact, this becomes a stronger always-on workflow tool
• –The update also signals that agent products are converging on multi-provider routing as a core feature, not a nice-to-have