Comparing Multi-Agent AI Systems: Anthropic's Harness vs Agyn's Engineering Org Model

Anthropic has published a harness design for long-running application development, while the Agyn multi-agent system for team-based autonomous software engineering was open-sourced last month on arXiv. Both approaches reject the "monolithic agent" model and instead structure AI agents to work like real engineering teams with role separation, structured handoffs, and review loops.
Core Architecture Differences
Anthropic's system uses a GAN-inspired architecture with three roles: planner → generator → evaluator. The evaluator uses Playwright to interact with the running application like a real user, then provides structured critique back to the generator.
Agyn models the process as an engineering organization with four roles: coordination → research → implementation → review. Agents operate in isolated sandboxes and communicate through defined contracts.
Shared Solutions to Common Problems
- Models losing coherence over long tasks: Anthropic uses context resets with structured handoff artifacts, while Agyn uses compaction with structured handoffs between roles
- Self-evaluation being too lenient: Both systems separate evaluation from generation. Anthropic uses a separate evaluator agent calibrated on few-shot examples, while Agyn has a dedicated review role separated from implementation
- Ambiguous "done" criteria: Anthropic uses sprint contracts negotiated before work starts, while Agyn has a task specification phase with explicit acceptance criteria and required tests
- Complex task decomposition: Anthropic's planner expands one-sentence prompts into full specifications, while Agyn's researcher agent decomposes issues and produces specifications before implementation begins
- Context anxiety: Anthropic uses resets for clean slates, while Agyn uses compaction with a memory layer
Agyn's Distinctive Features
Agyn includes two features not present in Anthropic's harness:
- Isolated sandboxes per agent: Each agent operates in its own isolated file and network namespace, preventing collisions on shared state during parallel or sequential work
- GitHub as shared state: The system uses GitHub primitives (commits, comments, PRs, reviews) that human teams already understand, providing a full audit log without requiring custom communication protocols
Implementation Differences
Anthropic's harness is built tightly around Claude using the Claude Agent SDK and Playwright MCP for the evaluation loop. The evaluator navigates live running applications before scoring.
Agyn is model-agnostic by design, supporting Claude, Codex, and open-weight models. The system allows mixing different models per role, which in practice has been found to outperform using one model for everything.
📖 Read the full source: r/ClaudeAI
👀 See Also

Vellium Adds Desktop Pets and CLI-Inspired Agents for Local LLMs
Vellium, an open-source crossplatform app for local LLMs, now supports desktop pets that float above windows and agents with MCP integration, terminal commands, and file editing.

Memento Vault: Local Tool for Persistent Context in Claude Code Sessions
Memento Vault is a set of hooks that automatically captures session transcripts, scores them, and stores atomic notes in a local git repo. It provides zero-cost retrieval via BM25 + vector search with 472ms average latency and injects relevant context at session start, on every prompt, and on file reads.

Jake Benchmark v1: Local LLM Performance Testing for OpenClaw AI Agents
A developer tested 7 local LLMs as AI agents with OpenClaw using 22 practical tasks including email processing, meeting scheduling, and phishing detection. Results ranged from 59.4% for Qwen 27B to 1.6% for Nemotron 30B, with detailed conversation logs available.
MathCode: A Mathematical Coding Agent with Lean 4 Formalization
MathCode is a terminal AI coding assistant that converts plain-language math problems into Lean 4 theorems and attempts formal proofs, with a persistent REPL, reusable libraries, and an Obsidian knowledge graph.