Overview
OpenDucktor orchestrates your coding agents on your computer: OpenCode, Codex, and Claude Code. They write the spec and the plan, build each task in its own Git worktree, and pass a QA review before yours.
OpenDucktor is free and open source. Its license is the Apache License 2.0. Read the code on GitHub.
Pin notes to the top of a notebook
fieldnotes-p6d4Reply here
Empty state Which action should the empty notebook offer first?
Other answerEmpty state
Create a note
Answer all questions to confirm.
Answer sent.
The implementation is ready for QA review.
OpenReview the changes and approve or request updates.
OpenThis task is closed.
OpenWhich action should the empty notebook offer first?
OpenHow a task moves
A task goes from a one-line request to merged code. The built-in Spec, Plan, Build workflow sets its steps. You start the first agent of each task. Autopilot can start the next agents and the pull request for you.
Key terms
| Term | Meaning |
|---|---|
| Workspace | A local Git repository that you open in OpenDucktor. Each workspace has its own board, tasks, and settings. Settings lists workspaces under Repositories. |
| Task | One piece of work on the board, of the type Feature, Task, or Bug. See Tasks and workflows. |
| Workflow | The lanes, roles, artifacts, and actions that a task follows. OpenDucktor has one workflow, Spec, Plan, Build. See How a task moves. |
| Lane | A column of the board. Each lane holds the tasks in one state of the workflow. See The board. |
| Role | The job of an agent on a task. The built-in roles are Spec (writes the specification), Planner, Builder, and QA. See Start an agent. |
| Session | One conversation between you and an agent. A task session runs one role of a task. A workspace session has no task. See Coding sessions. |
| Artifact | A file that an agent or you save on a task, such as the Specification, the Implementation Plan, or the QA Report. See Artifacts. |
| Worktree | A separate folder and branch for the code changes of one task. Your main checkout stays the same. See Git and pull requests. |
| Harness | The coding agent that runs a session: OpenCode, Codex, or Claude Code. Settings lists them under Agent runtimes, and shows Claude Code as Claude. See Harnesses. |
| Host | The part of OpenDucktor that runs the agents, Git, the terminals, and the task store on your computer. To use it from another device, see Remote control. |
Where it runs
You do not need an OpenDucktor account. OpenDucktor runs on your computer. It starts the coding agents that you installed, in your own repositories. Your coding agent sends prompts and code to the model provider that you set up.
To follow the agents from your phone or from another computer, turn on Remote control and pair the device. Other agents can also create and update tasks through External MCP.