Comparison
Ordewell vs Multica
Checked on , against Multica's README, documentation and license. Every statement about Multica links to its source.
Multica puts coding agents on a team's issue board, where you assign them work as you would a colleague. Ordewell turns one goal into a plan of tasks and runs them across agents. One is built around the team and the issue, the other around the plan.
Disclosure: the people who build Ordewell wrote this page. Where a difference could not be sourced from Multica's own pages, it is left out.
What each one is for
Multica describes itself as "a source-available workspace where you assign work to AI coding agents the way you'd assign it to a teammate — they pick up the issue, report progress, raise blockers, and hand it back for review" (README). "Multica records and coordinates the work; connected computers execute it" (how Multica works).
Ordewell's README puts it this way: "One goal becomes a plan graph you can edit, and each task gets its own agent, model and effort." Independent tasks run in parallel on their own branches, pass only on evidence, then merge (README).
How they differ
On the things Ordewell is built around. Each cell about Multica links to its source.
| Ordewell | Multica | |
|---|---|---|
| Who plans | A planner reads your repository without changing it, asks what is vague and writes tasks with dependencies. It can be a coding agent you are signed in to, or an API provider (README). | You, by filing issues and assigning them, or a squad's leader agent, which "reads the context and decides who takes the next step" (squads). "Agents never start work on their own" (how Multica works). |
| Plan editable before anything runs | Yes. Change any prompt, dependency, agent, model, effort or mode, then approve it; the desktop app shows the plan as a list or a graph. Build tasks wait for that approval unless you turn on autorun (README). | Issues and sub-issues on a board. Sub-issues can be given stages that advance in batches, and assigning an issue in Backlog never starts a run (issues). |
| Agent and model per task | Each task names its own agent, model and effort. Claude Code, Codex, OpenCode, Pi, GitHub Copilot CLI, Qwen Code, Cline, Gemini CLI and Cursor mix in one plan (README). | Each agent is set up with a runtime, an AI coding tool and a model (agents). Multica drives the agent CLIs you already have, such as Claude Code, Codex, Cursor and Copilot (README). |
| How a task counts as done | The agent reports through task_complete, or a script task exits cleanly. A clean exit with no report is a failure, and no second model decides (README). |
Agents set in_review when they deliver. Done is "left to a human reviewer or existing integrations", such as every linked pull request being merged (squads, issues). |
| Isolation and merging | With git, each task runs on its own branch in its own worktree. You review the diff and merge, or turn on automatic merging. Without git, tasks share your folder (README). | A run checks out a git worktree from a shared repository cache, or works in place in your project directory (daemon and runtimes). "Work lands in review, not in main" (README). |
| Surfaces | Desktop app, terminal UI, VS Code extension, CLI and a local API, on macOS, Linux and Windows (README). | Web, a desktop app for macOS, Windows and Linux, iPhone and iPad (built from source for now), a CLI and API, and chat channels such as Slack. Cloud or self-hosted (README). |
| License | Apache-2.0 (LICENSE). | The Multica License: the Apache 2.0 text plus additional conditions on hosted services, commercial embedding and branding (LICENSE). |
When Multica is the better choice
- A team of people and agents shares one board, with assignees, comments, an inbox, roles and access scopes (README).
- Work arrives from issues, mentions and chat channels, or from Autopilots that "run standups, audits, and reports on a cron" (README).
- You want a squad whose leader routes each issue to the member suited to it, whether that member is an agent or a person (squads).
- You want to self-host the whole stack with Docker Compose or Helm, against GitHub, GitLab, Gitea or Forgejo (README).
- You want an execution log that replays every tool call, command and error of a run (README).
When Ordewell is
- You have one goal and want the breakdown written for you: a planner reads the code, asks what is vague and writes dependent tasks.
- You want to edit and approve that whole plan before build tasks start.
- You want each task's verdict to come from its agent's
task_completereport or a script's exit status, not from a status an agent sets. - You want it on your own computer as a desktop app, terminal UI or VS Code extension.
- Your policy needs plain Apache-2.0, with no additional conditions, for forking or embedding.
Try Ordewell
Ordewell is open source under Apache-2.0 and runs on macOS, Linux and Windows. Get the desktop app from the download page, or install the terminal app:
# macOS and Linux: a standalone binary, no Node.js
curl -fsSL https://ordewell.ai/install.sh | sh
# Homebrew
brew install ordewell/tap/ordewell
# npm, Node 20.3+: the way to install on Windows
npm install -g ordewell
On Windows the terminal UI runs natively; its mouse and paste need Node 22.17+. git is
optional, 2.38+ recommended: with it, tasks run in their own worktrees. You also need a
supported coding agent, installed and signed in, or a provider API key. Then run
ordewell in your project and type a goal. The docs
cover the rest.
Sources
Every page below was read on 21 November 2026.