Dispatch

The agentic ticket board for Obsidian.

Your coding agents ship faster than you can decide. You are now the bottleneck — what remains of the development cycle is deciding what to build, agreeing on it as a team, and reviewing what comes back. Dispatch turns an agent-friendly wiki (à la Karpathy's LLM wiki pattern) into the cockpit for that human side: tickets are plain notes, boards are live views over their frontmatter, and every card can dispatch a coding agent — Claude Code, Codex, any CLI — into the right repository.

• Refinement is the new development. The agent posts a ticket's open questions into your team chat (Slack via MCP), the team answers where it already talks, and the answers flow back into the spec. Every card shows its refinement state as a ? N badge that burns down to green — green means build-ready.
• Release planning is drag & drop. The Release Plan view groups tickets by target version: live weighted progress per release, velocity-based forecasts that accumulate across versions, linked release notes for everything shipped. Drag a card — the plan is up to date the moment you drop it.
• Meetings run themselves around you. The agenda is prepared from the board; after the call, a NoteTaker transcript (e.g. Google Gemini) becomes an interpreted report in your vault, decisions are folded into the affected tickets automatically, and the action items show up per person on the Meetings and Todos tabs.
• Testing works like refinement. Manual test plans cover only what the automated suites don't; a ✓ N badge counts the open checks through review and turns green when a ticket is safe to ship.
• Claude Skills and MCP are the glue. Chips on the board are one-liners (/refine US00042); the workflow logic behind them lives as Claude skills in your code repository — versioned with the code, reviewed like code, shared through git — while MCP connects the agent to your team's Slack, your tracker and your NoteTaker. Wiki, team and codebase become one loop, and the agents run it with you.

Under the hood, two primitives: boards (kanban views driven by note properties — drag & drop writes frontmatter) and chips (buttons that launch coding agents with the ticket as context). Desktop only — chips and automations spawn local processes.

Documentation

New to the idea? Read Overview, then Wiki structure.

Quick start

1. Download main.js, manifest.json and styles.css from a release (or build from source), copy them into <vault>/.obsidian/plugins/dispatch/, and enable Dispatch in Settings → Community plugins. BRAT works too.
2. Point Settings → Dispatch at the folder holding your tickets and list your status values as columns.
3. Map your repository alias to a local path under This device, and add one chip template.

Or skip steps 2 and 3 and let an agent do them. An unconfigured board says so and offers a Set up with claude button, which starts Claude Code in your vault folder with the right prompt — it shows you the exact command first, and there is a Copy the prompt button if you would rather paste it into an agent you already have open.

The skill it uses lives in this repo's plugin marketplace:

/plugin marketplace add kaimys/obsidian-dispatch
/plugin install dispatch-setup

The prompt carries those two lines itself, so the button also works before you have installed the skill. It interviews you about your wiki, writes both config layers, scaffolds ticket templates and workflow commands, and verifies the result. Details in Installation & configuration.

Roadmap

• Multiple named boards
• Column colors
• Milestone burndown over time
• Chip runs with inline output (headless mode) instead of opening a terminal
• Worktree-isolated runs, so two agents can work one repo in parallel

License

MIT