Architecture

Middleman is three things running on your machine:

┌─────────────────────────────────────────────┐
│  Dashboard UI (TanStack + Vite SPA)         │
│  Chat, agent status, settings, artifacts    │
└──────────────────┬──────────────────────────┘
                   │ WebSocket
┌──────────────────▼──────────────────────────┐
│  Backend Daemon (Node.js)                   │
│  HTTP + WS server, agent orchestration,     │
│  message routing, persistence, scheduler    │
└──────────────────┬──────────────────────────┘
                   │ spawns & messages
┌──────────────────▼──────────────────────────┐
│  Agents (pi / Codex)                        │
│  Manager → Workers → Merger                 │
│  Each in its own worktree                   │
└─────────────────────────────────────────────┘

• apps/backend is the daemon. HTTP + WebSocket server, swarm orchestration runtime, persistence, and scheduler.
• apps/ui is the dashboard. Real-time agent monitoring, chat interface, and settings management.
• The manager agent is built on pi, is event-driven, and never blocks. Always ready for the next message.

How It Works in Practice

1. Create a manager for your project from the dashboard.
2. Onboard it by chatting. Tell it your preferred workflow, what tools to use, how you want work sequenced.
3. Dump tasks on it. A feature spec, a list of bugs, a vague idea.
4. The manager spawns workers, assigns tasks, and orchestrates execution in parallel where possible.
5. You review when you want, or let it roll.

A Note

This is a vibecoded project. It's here to inspire, not to be a polished product. Fork it, tear it apart, or use it as a starting point to build your own middle manager.

License

Apache-2.0