alook vs Fusion
Self-hosted collaboration layer that turns local coding agents (Claude Code, Codex, OpenCode) into an always-on "AI company" — per-agent email, org chart, kanban, shared memory. — versus — A multi-agent software factory: describe a task, agents plan (PROMPT.md), build, review and merge in isolated worktrees — kanban + graph board, missions, agent chat rooms, any model. Early preview.
Both are collaboration layers that turn local coding agents into a coordinated team on a kanban board; alook leans on per-agent email and shared memory, Fusion on planned workflows, worktree isolation and merge gates.
| alook | Fusion | |
|---|---|---|
| Stars | 944 | 964 |
| Forks | 144 | 118 |
| Language | TypeScript | TypeScript |
| License | Apache-2.0 | MIT |
| Last activity | today | today |
| Topics | coding, orchestration | coding, orchestration |
| Curated connections | 9 | 3 |
alook — the curator's take
Pick alook when you already live in Claude Code or Codex and want those agents running as a persistent little team — email in and out, a kanban they work through, schedules, memory that compounds — without writing a line of orchestration code. It's a product, not a framework: BYO agent, you're the CEO. NOT for building agents programmatically (that's LangGraph/CrewAI territory), and if you need budgets, governance, and audit over a heterogeneous fleet, paperclip is the heavier, control-plane take on the same idea. Young project — expect sharp edges and a moving roadmap.
Fusion — the curator's take
The most ambitious entry in the agent-factory wave: visual workflow authoring (plan→execute→review graphs you can edit), per-task oversight levels from observe to autonomous with human gates on merges, a multi-node mesh (fleet on a server, steered from your phone), importable 'agent companies' (440+ pre-built agents), and a Command Center with real fleet telemetry. Genuinely MIT and shipping weekly. When NOT: it wears its 'early preview' badge honestly — breadth currently outruns depth, so expect rough edges; if you want minimal-machinery unattended runs from an issue tracker, contrabass is the leaner tool, and a single interactive session needs none of this.