Dispatch

Dispatch is the workspace control plane. Where other templates are domain apps (Mail, Calendar, Analytics), Dispatch is the app you run alongside them to coordinate everything: a central inbox, a secrets vault, scheduled jobs, Slack/Telegram integration, and an orchestrator agent that delegates domain work to the right specialist app over A2A.

If you're running an multi-app workspace with many apps, Dispatch is the glue.

What it does

  • Central inbox. Slack DMs, Telegram messages, email notifications, A2A requests from other agents — all land in one place. The Dispatch agent triages and either handles them itself or delegates.
  • Orchestrator, not specialist. Dispatch does not try to be the email app or the analytics app. When someone asks "summarize last week's signups," Dispatch calls the analytics agent over A2A and returns the answer. When someone asks "draft a reply to Alice," Dispatch calls the mail agent.
  • Secrets vault. A central store for API keys, OAuth tokens, and shared credentials. Apps in the workspace resolve secrets from Dispatch instead of duplicating them in every .env. Requests + approvals for sensitive access.
  • Integrations catalog. One page showing every third-party integration — Slack, Telegram, SendGrid, Apollo, etc. — with a "configured / not configured / pending approval" status per app.
  • Scheduled jobs hub. Cross-app recurring jobs live here: "every weekday at 7, pull yesterday's key metrics from analytics and draft a morning summary email."
  • Approval flow. Destructive or external actions (sending money, shipping an outbound email, posting to Slack at scale) can require an admin OK before they fire. Dispatch owns the queue.

When to use it

Use Dispatch when:

  • You have two or more agent-native apps in a workspace and want one place to coordinate between them.
  • You need centralized secrets with per-app grants and an audit trail.
  • You want a messaging hub that routes Slack or Telegram into the right domain agent.
  • You want scheduled jobs that pull data from several apps.

Skip it for a single-app scaffold — use the Starter template or any of the domain templates directly.

Architecture at a glance

  • Orchestrator agent. The chat is set up as a router: it reads AGENTS.md, LEARNINGS.md, and routes to specialist sub-agents or remote A2A agents.
  • Remote agent registry. A2A manifests live in remote-agents/*.json — one per app. Dispatch calls them using the call-agent action.
  • Vault schema. Drizzle tables for secrets, grants, requests, approvals, and audit logs. See server/db/schema.ts in the template.
  • Slack / Telegram plugins. Server plugins that register webhooks and forward incoming messages to the orchestrator agent.
  • MCP hub mode. Dispatch can act as the workspace's MCP hub so every other app in the workspace pulls the same org-scope MCP server list.

Scaffolding

pnpm dlx @agent-native/core create my-platform
# pick "Dispatch" in the multi-select picker, plus whichever domain apps you want

Dispatch is usually scaffolded into a workspace alongside the apps it coordinates. For a workspace, Dispatch's shared auth, database, and brand are inherited from the workspace core — see Multi-App Workspace.

Customize it

Dispatch is a full cloneable SaaS like any other template — see Cloneable SaaS. Ask the agent to "add a new integration for Datadog" or "route Slack DMs from channel X to the issues agent" and it'll edit the routing config, add the webhook handler, and wire it up.

What's next