Follow along: I share what breaks (and what fixes it) putting AI agents into production — @surlymochan on X · Contra

⭐ If OpenFlow or OpenSwarm saves you time, a star is the best way to support the work — I'm pushing for 100 stars this month.

AI agents · Harness engineering · Reliable loops & graphs

I build tools for running coding agents, coordinating their work, and checking what they deliver. My focus is executable workflows, isolated execution, and experiments others can reproduce.

• 🌐 Phanes — my current flagship: a distributed, heterogeneous, self-evolving agent network. One control plane for goals and acceptance, a unified pool of compute resources, and final acceptance that must cite independent verification — never a worker's self-report. Architecture passed an adversarial multi-model design review; building in stages.
• 🔁 OpenFlow — executable delivery workflows for AI coding agents, with YAML phases and evidence gates. Quickstart · npm
• 🐝 OpenSwarm — quota-aware dispatch across coding agents, with isolated git worktrees, time budgets, and host-side verification. Getting started

• Phanes is where OpenBot, OpenSwarm, and my RSI (recursive self-improvement) work converge into one system: a single control plane holding agent identity, goals, authorization, and final accept/reject decisions; distributed heterogeneous execution scheduled against a unified resource registry (hosts, backends, models, quotas described separately from agents); and an evidence-driven improvement loop that proposes changes from verified run records. Tasks flow through one versioned contract — Goal → Task → Run/Attempt → Evidence — with idempotent dispatch, so a lost receipt or a restarted worker can never silently run the same attempt twice.

• OpenFlow turns delivery phases and acceptance evidence into an executable workflow. For developers who want to inspect how an agent's result was checked.

• OpenSwarm separates planning from execution and routes tasks across Codex, OpenCode, DeepSeek, and opt-in backends. Each task runs in its own worktree with explicit limits.

Recent merged contributions:

• oh-my-openagent — persisted Momus review verdicts next to the plan they reviewed.
• OpenBot — read inline triple-backtick code as text in Live Activities.
• OpenSpec — named the configured schema in the new-change progress line.
• OpenClaw — preserved compatible reasoning in follow-up requests.

Currently contributing fixes to oh-my-openagent, OpenBot, and strands-agents/harness-sdk. Open pull requests are proposals, not merged features or maintainer roles.

I publish benchmark methods and run records alongside my tools. Results are specific to the tasks, models, and configurations tested; small samples need careful interpretation.

• OpenFlow benchmarks
• OpenSwarm experiments
• Merged upstream PRs

More tools will appear here as their installation, documentation, and examples are ready for others to use.