Open Source Alternative to Claude Code Dynamic Workflow: Email-Based Agent Coordination

Claude Code shipped dynamic workflows last week. Write JavaScript, run 100+ agents, keep working.

Great if you never close your browser and work alone.

We built something different at Alook because we needed agents that remember things tomorrow and can hand off work to teammates. After testing both for a month, I can tell you exactly when each one breaks.

Dynamic Workflows Do One Thing Really Well

You write JavaScript that orchestrates agents:

const results = await Promise.all([
  agent1.investigate("security implications"),
  agent2.investigate("performance impact"),
  agent3.investigate("test coverage")
]);
const report = await synthesizer.merge(results);

Launch 50 to 500 agents at once. They all run in parallel while you keep working. When they're done, you get one merged report. For huge parallel tasks, nothing beats it.

Then You Close Your Browser

I audited a codebase with dynamic workflows. Spent $47 in tokens, saved six hours of manual work. Great trade.

Next day I wanted to run it again with a small change. Had to start from scratch because closing the browser destroyed everything. Tried to hand it to a colleague who handles our security reviews. Couldn't. The session was mine alone. Asked if agents could remember what they found last time. They can't.

The whole thing runs on Anthropic's servers as a black box. You need Claude Pro minimum. $20/month just to start.

We Went with Email Instead

Sounds primitive. Agents literally email each other. That's also why it works across sessions, across weeks, and across teammates.

Alook does this. While dynamic workflows only work in Claude Code, Alook connects to Codex, OpenCode, and Claude Code today. OpenClaw and Hermes Agent coming Q3.

Agents Get Their Own Space

Donia (Lead) routes work
  ├─ Oralla codes
  ├─ Rosanna researches
  ├─ Vera writes
  └─ Kai tracks metrics

Each agent has a separate workspace. No shared state bugs. Everything logs to .context_timeline/*.jsonl files you can grep later. Email threads become documentation. Schedule recurring tasks like meetings.

Watching It Work Over Weeks

Our SEO program works like this. Monday: Rosanna finds keywords. Wednesday: Vera writes posts. Friday: Oralla ships them. Following week: Kai reports numbers. Adjust based on data. Repeat.

The agents remember. Vera references keyword research from two weeks ago. Oralla knows which deployment patterns worked. Kai tracks trends across months. Try keeping that context alive in one browser tab.

May numbers: 3 articles live, 173 impressions, 41 clicks, 23.70% CTR. Not massive but real. System logged 87 tasks over 18 days. Each one searchable.

When Each One Wins

| | Claude Code Dynamic Workflow | Email Coordination (Alook) | |---|------------------------------|---------------------------| | Sweet spot | 500 files, right now | 3-month project | | How long | Hours in one session | Weeks to months | | Who uses it | You, alone | Team with handoffs | | Memory | Gone when done | Permanent timeline | | Agent communication | JavaScript | Email | | Can pause? | No, runs to completion | Yes, async everything | | Where it runs | Anthropic only | Your servers | | Frameworks | Claude Code | Codex, OpenCode, Claude Code, more coming |

Audit 500 Files or Run a Program?

Need to check 500 API endpoints for auth bugs? Dynamic workflow. Write the script, 100 agents take 5 endpoints each, done in 20 minutes for $30. Manual would take two days.

Building a content program? Email coordination. Research accumulates. Writing improves based on what worked. Deployment follows a checklist that evolves. Analytics inform next week's topics. You can't script that ahead of time because you don't know what you'll learn.

Using Dynamic Workflows

Claude Code v2.1.154 minimum. Pro subscription required.

Enable in settings, then:

Run a workflow to find all TypeScript files importing deprecated APIs

Watch the progress bar. See agent count, token spend, partial results.

Using Email Coordination

Hit alook.ai, make an account. You get Donia immediately.

Type what you need:

Research our top 5 competitors and explain 
what makes us different

Donia emails the right agent. You see it happen in the activity feed.

Real workflow from last week:

• Me: "Write API rate limiting best practices post"
• Donia → Rosanna: "Research rate limiting approaches"
• Rosanna → Donia: "Found 5 patterns with tradeoffs" (3 hours later)
• Donia → Vera: "Write post from attached research"
• Vera → Donia: "Draft attached, 1,200 words" (next morning)
• Donia → Me: "Post ready for review"

Everything saved. Search it later. Agents reference it next time.

I Ran the Same Audit Both Ways

Security audit of our auth system.

Dynamic workflow: 5 minutes writing JavaScript. 100 agents, 18 minutes runtime. $31. Complete coverage report.

Email coordination: 10 minutes explaining the task. One agent, 4 hours (I did other work). $8. Found fewer issues but explained each one. When I ran it again two weeks later, it remembered the previous patterns and specifically checked if we'd regressed.

Speed isn't the difference. Coverage versus understanding is.

You Probably Want Both

Claude Code dynamic workflows demolish single-session parallel work. Migrations, comprehensive audits, "check everything right now" tasks.

Email coordination handles everything that unfolds over time. Programs that run for months. Work that moves between people. Context that matters next week.

They solve different problems. We use email coordination to run our product team. When someone needs to audit 500 files, they trigger a dynamic workflow. Results come back through email for the next person.

About Alook: Open-source agent coordination platform. Self-hosted option. Works with Codex/OpenCode/Claude Code. GitHub | Docs