I Turned helix-agent into helix-agents: One MCP Server for Ollama, Codex, and OpenAI-Compatible Models

If you use Claude Code heavily, you eventually hit the same wall: some tasks are cheap enough for local models some tasks want a stronger coding agent some tasks are better sent to an API model But many MCP servers still force one provider and one execution style. So I evolved helix-agent into helix-agents. It now lets Claude Code delegate work across: ollama codex openai-compatible from one MCP server. What changed The original project was focused on one thing: sending routine work to local Ollama models with automatic routing. The new version keeps that path, but adds: multi-provider switching Codex-backed code delegation OpenAI-compatible chat API support Claude Code-style background agents Under the hood, the runtime now supports two different delegation styles: a built-in ReAct loop for ollama and openai-compatible an autonomous Codex-backed path for repo-heavy work That means the workflow is no longer: Claude Code -> one tool call -> one reply It can now be: Claude Code -&g