Fusion vs helmor
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. — versus — Local-first desktop workbench for orchestrating coding agents: per-repo workspaces, task dispatch, live status and runnable actions — GUI plus CLI, Apache-2.0.
Factory vs workbench: Fusion runs autonomous plan-build-review-merge missions on a kanban board; Helmor keeps you as the lead dispatching tasks into workspaces.
| Fusion | helmor | |
|---|---|---|
| Stars | 964 | 1.3k |
| Forks | 118 | 115 |
| Language | TypeScript | TypeScript |
| License | MIT | Apache-2.0 |
| Last activity | yesterday | today |
| Topics | coding, orchestration | coding, orchestration |
| Curated connections | 4 | 3 |
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.
helmor — the curator's take
Workbench, not factory: you stay the lead and dispatch agents into per-repo workspaces, watching status like a build queue. Cleaner mental model than kanban swarms for a solo dev. Skip for headless issue-queue automation (contrabass) or if you live inside one OpenCode session (codenomad).