---
title: "Dispatch"
description: "Dispatch is the workspace control plane — central inbox, cross-app orchestration, secrets vault, Slack/Telegram integration, and scheduled jobs."
---

# Dispatch

Dispatch is the app you run alongside your other Agent-Native apps to keep a multi-app workspace coordinated: one inbox for every channel, one secrets vault, and one agent that routes each request to the right specialist app instead of trying to do everything itself. It's for whoever runs the workspace — not for someone building a single standalone app.

<Callout tone="info">

**See also:** for the conceptual overview of what Dispatch does and when you want it, see [Dispatch](/docs/dispatch). This page is the template-specific reference.

</Callout>

<Video
  src="https://cdn.builder.io/o/assets%2FYJIGb4i01jvw0SRdL5Bt%2F65b2b76a0dec44dbbbaec738e5512228?alt=media&token=f5ad219e-c566-43b2-90ca-a51c72d9a607&apiKey=YJIGb4i01jvw0SRdL5Bt"
  alt="A short screen recording touring the Dispatch overview, inbox, and app launcher."
  caption="A brief tour of Dispatch."
  autoplay={true}
  loop={true}
/>

If you're running a [multi-app workspace](/docs/multi-app-workspace) with many apps, Dispatch is the glue.

## Dispatch in practice {#in-practice}

### A question in Slack becomes an analytics note

A message in one channel can end up as a change in a completely different app, without anyone copying information by hand.

<Sequence>

### The **#marketing** channel gets an update on a key client

### :blue: **Dispatch** sees the message and recognizes it as an analytics note

### A note is added to **Analytics** about that client

</Sequence>

### A Monday report pulls data from another app

A recurring job doesn't need its own copy of another app's data. It just asks for it, every time it runs.

<Sequence>

### A recurring job **wakes up** every Monday at 7am

### :blue: **Dispatch** asks the analytics agent for last week's signups

### A summary is **emailed** to the team

</Sequence>

### A discounted deal gets sign-off from two other teams

A single approval can touch several apps and teams before it's done, with Dispatch relaying each request and answer so no one leaves their own app to move it forward.

<Sequence>

### A **sales rep** requests discount approval in the CRM

### :blue: **Dispatch** asks Finance's agent if it's within policy

### **Finance** approves it in their own app

### :blue: **Dispatch** asks Legal's agent to check the contract terms

### **Legal** flags one clause and requests a change

### :blue: **Dispatch** relays the change back to the sales rep

</Sequence>

## What it replaces {#what-it-replaces}

<Comparison>

### Before

- A Slack bot, an email inbox, and a support alias, each wired to a different app by hand
- A `.env` file, and a copy of every key in it, duplicated per app
- A cron job or admin script per app for anything recurring
- No single place to see what changed, who approved it, or what an app is spending on LLM calls

### After

- One inbox: Slack, Teams, Discord, Telegram, WhatsApp, and email all reach the same agent
- One vault: every credential saved once, granted or synced to whichever apps need it
- One place for recurring jobs, Dreams' memory review loop, and admin approvals
- One operator console for audit history, usage, and thread debugging across every app

</Comparison>

<Callout tone="success">

**Dispatch can build the next app for you.** Describe what you need in chat — "build me an app for tracking customer onboarding" — and Dispatch starts a brand-new sibling app under `apps/` rather than bolting more screens onto an existing one. See [App creation hand-off](/docs/template-dispatch-developers#app-creation) for how it actually works, locally and in a hosted deployment.

</Callout>

## What it does {#what-it-does}

- **Central inbox.** Slack, Microsoft Teams, Discord, Telegram, WhatsApp, and email all land in one place. Dispatch triages and either handles a request itself or delegates it. See [Central inbox and routing](/docs/template-dispatch-features#central-inbox-and-routing).
- **Control-plane shell.** Chats, projects, runs, workspace apps, agents, and automations live in one operational shell, with status-first lists and drill-downs instead of one-off dashboards.
- **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.
- **Secrets vault and reusable integrations.** API keys, OAuth tokens, and provider accounts are saved once and granted to whichever apps need them, with a request/approve flow and an audit trail. See [Credentials and integrations](/docs/template-dispatch-features#credentials-and-integrations).
- **Workspace resources.** Global skills, guardrail instructions, custom agent profiles, reference resources, and HTTP MCP servers can be created once in Dispatch. All-app resources are inherited at runtime by every app with no copy step; selected grants cover app-specific exceptions.
- **Scheduled jobs and Dreams.** Cross-app recurring jobs live here, alongside a review loop that inspects recent runs and proposes memory, skill, and instruction improvements. See [Automations and scheduled jobs](/docs/template-dispatch-features#automations-and-scheduled-jobs) and [Dreams and approvals](/docs/template-dispatch-features#dreams-and-approvals).
- **Approval flow.** Durable changes — saved delivery destinations, All-app workspace resources, and shared or team-wide Dream memory proposals — can require a second admin's OK before they take effect.
- **Build new apps from chat.** Describe a need in plain English and Dispatch scaffolds a real, independent sibling app instead of adding one more screen to an existing one.

## When to use it {#when-to-use}

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, Teams, Discord, Telegram, WhatsApp, or email into the right domain agent.
- You want **scheduled jobs** that pull data from several apps.

Skip it for a single-app scaffold — use the [Chat template](/docs/template-chat) or any of the domain templates directly.

Live demo: [dispatch.agent-native.com](https://dispatch.agent-native.com).

## What you'll do with it day-to-day {#what-youll-do}

- **Connect your channels.** Slack, Microsoft Teams, Discord, Telegram, WhatsApp, or email — see [Connecting a channel](/docs/template-dispatch-features#connecting-a-channel) for wiring steps.
- **Save secrets and connect providers once.** Every other app in the workspace pulls from the vault or a shared connection instead of holding its own copy. See [Credentials and integrations](/docs/template-dispatch-features#credentials-and-integrations).
- **Keep company context global.** Put personas, positioning, company facts, and guardrails in Dispatch Resources once, then preview the effective workspace → app/org → personal stack for any app or user.
- **Set up recurring jobs.** "Every Monday at 7am, ask the analytics agent for last week's signups and email me a summary." See [Automations and scheduled jobs](/docs/template-dispatch-features#automations-and-scheduled-jobs).
- **Review Dream proposals.** Dispatch's memory review loop inspects prior runs and proposes source-backed changes to what the workspace remembers.
- **Gate durable changes.** Saved destinations, All-app workspace resources, and shared Dream proposals can require a second admin's OK before they apply — see the [approval flow](/docs/template-dispatch-features#approval-flow).
- **Watch the operator console.** Monitoring, database admin, thread debugging, audit history, and usage metrics all live under one roof — see [Operator console, at a glance](/docs/template-dispatch-features#operator-console-at-a-glance).
- **Spin up a new app from chat.** Ask for what you need and Dispatch scaffolds a new sibling app rather than growing an existing one.

## Get started {#get-started}

```bash
npx --yes @agent-native/core@latest create my-platform
# Dispatch is included automatically. Deselect Chat for Dispatch only, or select domain apps to scaffold alongside it
```

Dispatch is almost always scaffolded into a workspace alongside the apps it coordinates — a control plane with nothing to coordinate is just an empty inbox. See [Getting started](/docs/getting-started) for installing dependencies, running the dev server, and creating your first account.

## What's next

- [**Features**](/docs/template-dispatch-features) — every feature area, with setup steps for each
- [**Talk to the Agent**](/docs/template-dispatch-agent) — prompts by task and how the agent sees your screen
- [**Dispatch in a Multi-App Workspace**](/docs/template-dispatch-integrations) — how other apps connect to Dispatch, and how Dispatch discovers them
- [**Dispatch developer guide**](/docs/template-dispatch-developers) — the package/app split, scaffolding, and customizing it
- [**Dispatch action and data reference**](/docs/template-dispatch-reference) — the full action inventory, database schema, and route list
- [**Multi-App Workspace**](/docs/multi-app-workspace) — running Dispatch alongside multiple apps