Ordewell CLI
A planner for Claude Code, Codex and OpenCode: one goal becomes a task plan and independent tasks run in parallel
- 209 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Tasks run as you, in the mode the plan assigns, and change files in working copies
- Scripts and merging can proceed without your confirmation if you turn on autorun and automatic merging
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/ordewellDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Tasks run as you, in the mode the plan assigns, and change files in working copies
- Scripts and merging can proceed without your confirmation if you turn on autorun and automatic merging
This is third-party code. Review the repository files before installing.
What it does
Ordewell takes a goal, explores the repository, asks clarifying questions and builds a plan of tasks. Each task has its own runner, model, thinking effort and mode, so Claude Code, Codex and OpenCode can work side by side in one plan. The planner only reads code; the tasks of the plan make the changes. Independent tasks run in parallel in separate `git worktree` copies, dependent ones wait for their inputs. After a run Ordewell shows reports and changes, and merging into your branch happens after you confirm it. A plan can include check-and-fix loops that repeat until the check passes or a round limit is reached, and read-only tasks for research and operations. You can work in the terminal UI (the `ordewell` command), in the VS Code extension, with the `plan`, `run` and `handoff` commands, or through a local API. When an agent hits its account limit, tasks pause and unfinished work can move to another agent. Team instructions live in repository skills, which the planner attaches to tasks regardless of runner.
Who it is for. Developers who have Claude Code, Codex or OpenCode installed and a large task that splits naturally into parallel parts in separate branches.
Good fit when
- A large feature splits into independent parts that are best written at the same time in separate branches
- You want to read and edit the plan before it runs: prompts, dependencies, and the model and mode of each task
- One agent hit its limit mid-run and the rest of the work has to go to another
- A check keeps failing and you want it looped with the fix until it passes
- One goal needs repository research, code changes and a final verification in a single run
Not a fit when
- The change fits in one file and takes a couple of minutes: ask an agent directly
- None of Claude Code, Codex or OpenCode is installed: Ordewell does not write code itself
- The project folder has no git: tasks share one workspace and there is no branch isolation
- You need commands that stay stable between versions: the project is pre-1.0 and minor releases can break compatibility
Example request
Split the move to the new build system into tasks: configuration, script fixes, CI update and a final check. Let Claude Code write the configuration and Codex verify the result.Limitations
The project is pre-1.0 and minor releases can change behavior, so read the changelog before upgrading. It needs Node.js 20.3 or newer, git 2.38 or newer for task isolation, and at least one of Claude Code, Codex or OpenCode. On Windows the planner needs Git for Windows, and Codex tasks need Codex's own sandbox set up once.
Without a git repository, or with isolation turned off, tasks share the working folder and some files can be shared even between worktrees. Once a day Ordewell checks for updates and sends ordewell.ai its version and a random install ID after a one-time notice. Set `ORDEWELL_NO_VERSION_CHECK=1` or `DO_NOT_TRACK=1` to switch it off.
How to disable. `npm uninstall -g ordewell` removes the global install, and the VS Code extension is removed from the extensions list. Running through `npx ordewell` installs nothing system-wide.
FAQ
How do I try Ordewell without installing it?
Run `npx ordewell` in the project folder to open the terminal UI. On first launch, pick the planner and runners with `/planner` and `/runners`, then type a goal.
Does it need a separate API key?
No: a supported coding agent can do the planning without an extra key. You can connect an API provider as well if that suits you better.
Will Ordewell change my branch without asking?
No. Autorun and automatic merging are off by default, a submitted plan waits for approval, and merging follows a review of the changes. Research tasks can start during planning without plan approval, and scripts run with your consent.
What happens when an agent runs out of its limit?
Tasks pause. You can resume later or hand the unfinished work to another connected agent.
Which editors are supported?
The VS Code extension installs from the Marketplace or with `code --install-extension ordewell.ordewell`. Cursor, Windsurf and VSCodium get it from Open VSX. The extension bundles its own core and does not need npm.
Discussion
No questions or reviews yet.
Related
CLI toolsA local dashboard for many Claude Code sessions: each job gets its own context and todo, agents spawn child agents and message each other
One agent launches others in the background: Claude Code, Codex, Copilot CLI, Grok Build and Pi, with a model chosen per stage.
An OpenCode plugin that runs a team of parallel agents with separate sessions, a shared task board and messaging
A desktop app where Claude Code, Codex, Gemini and other agents work as a team of specialists in a shared project
A local control panel for coding agents: it runs Claude Code and Codex, keeps a task queue and merges verified work into main.
A team of AI agents from one request: it plans the task, writes code in parallel branches, tests, reviews and opens a pull request
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Ordewell (this card) | no | 209 | |
| Claude Squad | no | 8,738 | a terminal app for parallel agent sessions in tmux, without a shared plan with dependencies |
| CCManager | no | 1,278 | an agent session manager over git worktrees that does not build a task plan |
README in short
The documentation covers planner modes, skills, configuration and platform notes. Architecture decisions, including rejected options, are recorded in `docs/adr/`, and near-term plans are tracked in the repository issues.