Yann AbadieHire me on Upwork

All selected work

nexus-swarm-os

A multi-model orchestration platform. 7 native provider drivers, a second model that checks each tool result, and security layers that are on by default.

Status
Status: Working
Stack
Python 3.11+, 7 provider SDK drivers, Docker, FastAPI, MCP
Last commit
19 November 2026
Sources
Each tag opens the README line that makes the claim, at commit 20b9c6c.

The problem

A model checking its own work misses its own mistakes, and an orchestrator can report success on a step that failed. README L19 (source in the nexus-swarm-os repository) Teams that use several providers also need failover, one place for access control, and a log of every action.

What I built

The README calls the platform NEXUS. README L1 (source in the nexus-swarm-os repository)

System as built

  1. Request in

    From the REPL, the MCP server, the REST API or the CLI.README L28–35 (source in the nexus-swarm-os repository)

  2. FSM orchestrator

    12 states route the task.README L32 (source in the nexus-swarm-os repository)

  3. HiveMind or Swarm Engine

    7 phases, or 6 collaboration modes.README L64–66 (source in the nexus-swarm-os repository)

  4. Driver layer

    The provider call, with failover and a circuit breaker.README L50–54 (source in the nexus-swarm-os repository)

  5. Tool runs in the sandbox

    Docker by default; the host is opt-in.README L286 (source in the nexus-swarm-os repository)

  6. The opposite model validates

    If Claude issued the command, Gemini reviews the result before the pipeline advances.README L19 (source in the nexus-swarm-os repository)

  7. Security layer

    InputGuard and OutputGuard filter what goes in and out; AuditLogger records the action.README L274–281 (source in the nexus-swarm-os repository)

How it is verified

What this means for your project

  • If you use more than one model provider, failover and a second-model check can live in the orchestration layer instead of in each prompt. That is an Agent or MCP build.
  • RBAC and an audit log come with the first release, not after the first incident.
  • An Architecture review can decide where a second-model check is worth its cost.

Status & limits

  • Working reference codebase: PR #1 was merged on 19 November 2026 so push/PR CI passes (Tests 3.11–3.13, Lint & Types, Security, Swarm evaluation harness). Last commit: 19 November 2026. No tagged release.
  • Scheduled nightly stress tests (Torture Protocol) still report 20/76 known failures tied to an open saga compensation design question. Treat the repo as a reference implementation of these patterns rather than a turnkey product.
  • No hosted demo. The research CLI has a mock mode that needs no API keys. README L86 (source in the nexus-swarm-os repository)
  • SwarmProof reuses its swarm engine.