Duo 0.3.0 — Custom Templates

Duo 0.3.0 — Custom Templates

Custom Templates are Duo's universal foundation for coordinating models. Pair, Debate, Review, Council and Ask are fully constructed as templates in this same system. Every built-in method can be recreated from a new method in the visual maker, customized, saved and run through the same executor.

Build your own coordination method with the building blocks behind Duo's built-ins. Define model roles, choose who holds them, route selected responses, change roles based on results, and decide when the workflow finishes. Named memory channels retain selected information across turns or runs within explicit entry and character budgets.

The desktop builder provides clickable workflows, role and response editors, conditions, routing, memory controls, validation and undo/redo. JSON is an alternate editor. Describe with AI uses your chosen Claude or Codex model to draft or revise a method, validates it, and returns it to the builder for review. Save methods locally, copy a built-in, or use the matching duo template commands.

The maker exposes built-in stages, complete stage prompts, response schemas, starting model assignments, shared context, workflow branches and supported stage settings. Reusable host operations handle mechanics such as ledger updates, citation checks, ranking and workspace isolation; templates define the stage order and completion policy. Thirteen regression scenarios verify the built-ins' original prompts, schemas, outcomes, reports and domain artifacts. Existing Continue behavior is retained.

Debate now ends with every model reviewing the frozen claim ledger and explicitly agreeing or disagreeing with every peer claim. Incomplete reviews retry once and fail if still incomplete. Reports, the run view and continued debates retain those final decisions.

This release also fixes seat selection with an eligibility pool, exception messages lost before completion, malformed-definition validation crashes, stale discarded JSON drafts, round-count editing and GUI bundles missing updated shared code or CSS. Saved templates can be deleted from the builder. Generated drafts and recorded methods can be reopened in the visual builder from their runs. Removing a persistent channel, switching it to run-only storage, or deleting its saved template clears that channel from disk. Past run audit records remain available.

Additional write roles use a fully custom method with an explicit workspace isolation policy. Copied native methods keep their original writer workspace and permission contracts. Memory budgets govern automatically referenced content; provider conversation files and Duo audit traces have their own storage.

Install or upgrade

The duo-0.3.0-source.tar.gz asset contains source, the dependency lockfile, the built GUI, tests and documentation. It requires Node.js 22.18 or newer and Git; dependencies and Electron are installed on your machine. It is not a standalone installer.

Extract the archive, open a terminal in duo-0.3.0, then run:

npm ci
node bin/duo.js setup
node bin/duo.js doctor

Close Duo before upgrading. If you already use a Git checkout, update it to v0.3.0, run npm ci, and rerun node bin/duo.js setup if its location changed. Existing chats, runs and configuration stay in Duo's data folders. Sign-in uses your installed Claude Code and the pinned bundled Codex CLI.

The companion SHA256SUMS file contains the archive checksum. On Linux, verify with sha256sum -c SHA256SUMS; on macOS, use shasum -a 256 -c SHA256SUMS; on Windows, compare (Get-FileHash .\duo-0.3.0-source.tar.gz -Algorithm SHA256).Hash with the listed value.

See the template guide for examples and storage semantics, and the changelog for the complete changes.