rockarxiv/Engineering-Orchestrator

EO is an open-source, local-first desktop app for running work through pipelines you build yourself. You describe the pipeline you want, the assistant drafts it, and you publish it; you change it the same way, at any time. A step is one of four kinds: an agent (Claude Code or Codex), a person, EO itself, or your own script, a module a person approved.
Software delivery is one template: each ticket is worked in its own git worktree, and the engine checks the implementer's claims (commits exist, the tree is clean, the tests ran) before a reviewer sees it. Other templates cover reports, inbox triage and content drafts.
Ask the assistant for a change. It reads the repository, drafts one ticket, and files it when you accept.
A piece of work is an item. It sits on a step of a pipeline, and the step says who has it right now: an agent, a person, EO itself, or a script. When that party is finished, the item moves along the route the pipeline declares for the result. When an agent gets stuck it comments and mentions you, which ends its run rather than leaving a subprocess waiting.
Pipelines are data. Start from a template — a weekly report, an inbox triage, a content draft — or describe what you want to the assistant and have it draft one.
The board and the graph behind it. Asked for a hand-checked QA step after Review, the assistant drafts the change; publishing it rewires the routes.
Software delivery is one template among them: in Software feature to merge an implementer works each ticket in its own git worktree, and the engine then checks the claim independently — commits exist, the tree is clean, your tests actually ran — before a reviewer sees it.
One ticket through Software feature to merge: a worktree, an index, an implementer, a reviewer, then Done. The repository has no forge, so no pull request is opened. The agent stretches are sped up.
A step can also be your own script. Ask for one in plain words and the assistant writes it as a module with its own tests; EO runs those tests when you approve it, and nothing is published unless they pass.
Weekly report from the gallery, then a script step asked for in plain words. The assistant writes a word-count module with nine tests; one fails on the first approval, so nothing is published. It fixes the module, the tests pass, and Word count goes in between Draft and Approve. The waits are sped up.
ARCHITECTURE.md is the design document.
## Running it
Requires Node 22+, pnpm 10+, and git on your PATH.
bash
pnpm install
pnpm dev
That's the whole thing — pnpm install rebuilds the native SQLite module for Electron, and pnpm dev opens the app with hot reload.
Devtools do not open by themselves. Toggle them with Ctrl/Cmd-Shift-I, or launch with EO_DEVTOOLS=1 to have them open detached.
## Download
Every release attaches installers for all three platforms: Releases.
| Windows | EO- -win.exe — one installer, x64 and arm64 |
| macOS | EO- -mac-arm64.dmg for Apple silicon, -x64 for Intel |
| Linux | EO- -linux-x86_64.AppImage — chmod +x it and run it |
They are not code-signed. Certificates are still outstanding, and until they exist your operating system will say so: