The agent release
Dispatch 0.2.5 is now available, with full Codex support as its headline feature. You can use the same skills with both Claude Code and Codex, then choose which coding agent to launch from the confirmation dialog shown below. The dispatch-setup skill is also available through both agent plugin marketplaces.
The canonical skill set included with Dispatch now also includes /code-review. This lets you run a code review with a different agent and model from the ones used to write the code, providing an independent perspective that can produce a more rigorous review.
Dispatch skills now live in a dedicated /dispatch folder in your repository. References in .claude, .codex, CLAUDE.md, and AGENTS.md point to the corresponding skills in that folder, so a skill change is automatically available to both agents.
Codex is a first-class chip tool
Chips can now dispatch Codex as well as Claude Code, through every install
route — the Claude plugin marketplace, the Codex marketplace, and the Codex
skill installer. In a multi-agent setup the board offers one neutral chip per
workflow intent and keeps the agent-specific / or $ prefix in device-local
configuration, so the same menu entry launches either agent.
A code-review chip on the card
/code-review <id> launches from the ticket card. The point is not
convenience: a chip launch is a fresh session by construction, and "the
reviewer is not the author" is the one precondition a review cannot fake. Cards
also gained a blocking-findings counter beside the existing questions and tests
badges.
The skills catalog describes what you actually get
The setup skill scaffolds nine workflow commands; the documentation still
claimed Dispatch shipped none, and mixed those defaults with examples that were
never shipped.
Install and setup
Every install document now says what is true — Dispatch is in the Obsidian
community plugin directory, and the quick start no longer routes people through
a manual file copy.
A wiki and its code repository are now paired by configuration rather than by
folder nesting and symlinks, so the two no longer have to live inside one
another on disk.
Google Meet transcripts import themselves
Meeting summaries and transcripts no longer have to be downloaded by hand and
dropped into a sources folder before a meeting report can run.
Fixes
The milestone forecast was pessimistic on young boards. Velocity was
divided by the full look-back window even when the board had only been
collecting completions for a fraction of it, so a new board reported a fraction
of its real throughput and every version forecast inherited the error.
New tickets no longer claim a refinement nobody did. The starter ticket
templates seeded open_questions: 0, so every ticket created from one rendered
a green counter badge and met the development gate before anyone had refined
it. All three gated counters now ship empty, and a counter reads 0 only where
the section it counts records that the count was taken. This changes what a new
ticket looks like — nothing rewrites tickets that already exist.
Security
The community directory's security review is answered, and the open advisories
are cleared.
One recommendation was deliberately not taken: removing the plugin's
clipboard write. It backs one convenience button, the reach it costs is a
single documented call, and the review's concern is answered directly instead.
Upgrading
No migration and no configuration change. minAppVersion stays at 1.7.2.
Download main.js, manifest.json and styles.css below into
<vault>/.obsidian/plugins/dispatch/, or install Dispatch from Obsidian's
community plugin directory. Desktop only.
Full changelog: 0.2.4...0.2.5