Jeffrey Emanuel's Agentic Coding Flywheel

Table of content
Jeffrey Emanuel's Agentic Coding Flywheel

Jeffrey Emanuel spent a decade as a long/short equity analyst at hedge funds like Millennium and Balyasny. In late 2025, he pivoted to building what he calls the “Agentic Coding Flywheel” — a collection of interconnected MCP servers and tools that let multiple AI agents work together on the same codebase without stepping on each other.

Background

GitHub | Twitter | Site

The Flywheel Concept

The core insight: individual AI coding tools become more useful when they feed into each other. Memory systems inform task planning. Task planning drives agent coordination. Coordination requires file locking. File locking needs audit trails.

Emanuel built tools for each piece, designed to work together:

ToolStarsPurpose
MCP Agent Mail1,400Agent-to-agent messaging with file reservations
Beads Viewer891Task dependency visualization with graph metrics
CASS152Persistent agent memory (episodic, procedural, semantic)
Ultimate MCP Server12850+ tools: web scraping, databases, file ops
Ultimate Bug Scanner132Meta-runner for ESLint, Ruff, Clippy
NTM69Named tmux manager for spawning agent panes
SLB49Cryptographic command binding for safety

MCP Agent Mail

The flagship project. It gives coding agents a way to coordinate without human intervention.

{
  "mcpServers": {
    "agent-mail": {
      "command": "npx",
      "args": ["-y", "@anthropic/mcp-agent-mail"]
    }
  }
}

What it does:

Steve Yegge (creator of Beads) wrote about the integration:

“The most compelling case to come along so far for direct integration with an orchestrator was MCP Agent Mail, written by a gentleman named Jeffrey Emanuel.”

Emanuel ran 7 concurrent Codex instances working as a team on a commercial project. After many hours, they exchanged over 1,000 agent messages without human coordination.

Multi-Agent Workflow

The flywheel workflow:

  1. NTM spawns named agent panes in tmux
  2. Agents register with Agent Mail
  3. Agent Mail reserves files to prevent conflicts
  4. SLB validates dangerous commands
  5. Ultimate Bug Scanner checks code quality
  6. Beads tracks task dependencies
  7. CASS provides persistent memory

From Emanuel’s observations:

“It doesn’t require massive setup or coordination. You just give them a task and tell them to go sort it out amongst themselves. There’s no ego, so they quickly decide on a leader and just split things up.”

Ultimate MCP Server

A comprehensive server exposing 50+ capabilities:

The cost optimization routes tasks: expensive reasoning to Claude 3.7 Sonnet, simple operations to Gemini Flash 2.0 Lite. Emanuel claims 70-90% API cost savings.

CASS Memory System

Three types of memory for agents:

Memory TypePurpose
ProceduralHow-to playbooks and workflows
EpisodicSession histories and past interactions
SemanticFacts and domain knowledge

This solves the problem of agents forgetting context between sessions. CASS stores memories in SQLite with vector search for retrieval.

Key Takeaways

PrincipleImplementation
Tools should composeEach tool feeds into others
Agents need coordinationMessaging + file locking + audit trails
Memory persistsProcedural, episodic, semantic storage
Cost optimization mattersRoute tasks to appropriate models
Safety requires verificationCryptographic command binding

Getting Started

Install the recommended stack:

# MCP servers
npm install -g @anthropic/mcp-agent-mail

# CLI tools
pip install beads-viewer cass ubs

Configure Claude Code to use Agent Mail, then spawn multiple agents with NTM. They’ll self-organize.


Next: Jesse Vincent’s Superpowers Framework

Topics: mcp multi-agent ai-coding open-source workflow