Dispatch
The agentic ticket board for Obsidian. A property-driven kanban, milestone, meeting and todo board over your own notes — where every card is also a launcher for an AI coding agent.
What it does
Two primitives carry the whole plugin:
- Boards are views over note frontmatter. Drag a card and the frontmatter is written immediately. There is no separate database; the notes are the board, so everything a board shows stays greppable, diffable and syncable.
- Chips are buttons that launch an agent — Claude Code, Codex, any CLI — in the right repository, with the ticket as context. The board knows what the agent is doing; the note keeps what it did.
Four tabs sit above the board. Kanban and Release Plan are always there; Meetings and Todos appear once you point them at their folders. Which frontmatter properties drive all of it is up to you — Dispatch never invents a pipeline you did not configure.
Where your data goes
Nowhere. Dispatch has no server, no account and no telemetry. It reads and writes markdown files in your own vault and runs programs you configured on your own machine. The developer receives nothing. The one optional feature that talks to an external service — importing Google Meet transcripts — runs on your computer with your own credentials, and is described in full in the privacy policy.
Dispatch is desktop-only, free, and open-source under the MIT licence.
Get it
- Obsidian community plugins — search for Dispatch, or open the directory listing.
- Source, documentation, issues and releases — github.com/kaimys/obsidian-dispatch.
- Website — articles, documentation and release notes at kaimys.github.io/obsidian-dispatch.
Documentation
- Overview — the boards, the chips, and what each tab does
- Installation — installing, and where each layer of settings lives
- Page types — the frontmatter contract a board reads
- Skills — the workflow commands agents run against your tickets
- Wiki structure — how a project wiki and its code repository fit together