--- title: "Slides in a Multi-App Workspace" description: "How Slides connects to Dispatch, sharing decks through the Creative Context Library, and natural-language delegation across a multi-app workspace." --- # Slides in a Multi-App Workspace Slides is one app among many in a [Dispatch](/docs/template-dispatch) workspace. This page covers what that actually means in practice: how the connection works, and concrete ways other apps can act on your decks or reuse what's in them. See [Slides](/docs/template-slides) for the overview. ## How Slides connects to Dispatch Whether this is automatic depends on how Slides and Dispatch were set up together, not on whether either one is hosted or running locally. ### Same workspace: automatic If Slides and Dispatch were generated or added together into one Agent-Native workspace (via `create` or `add-app`) and deployed as one unit, they already share one `.env`, one `A2A_SECRET`, and one workspace registry. Discovery and authenticated A2A calling both just work, with nothing to set up, whether that workspace is running on your machine or in production. This is the expected setup for a real multi-app product built on Slides. ### Separate deployments: one manual step If Slides and Dispatch are two independently created Agent-Native projects, they don't share a secret and can't call each other yet. Connecting them takes one manual step on each side: add a `remote-agents/.json` resource with a shared secret, from Settings → Agent → Sub-agents (Connect agent), or Dispatch → Agents → Add external agent. See [A2A Protocol](/docs/a2a-protocol) for the full walkthrough. To check which situation you're in, ask either app's agent "what apps can you see?" If Slides is missing from Dispatch's answer, you're in the second case. ## Integration strategies **Sharing decks through the Creative Context Library.** Submitting a deck freezes one exact version in the shared Creative Context Library, and any app in the workspace, not just Slides, can search for and reuse those slides later. A meeting-notes app could pull an approved metrics slide into its own output instead of describing it in a prompt. **Natural-language delegation through Dispatch.** A sibling app doesn't need a special integration to work with Slides. It can hand Slides' agent a plain English request, like "build a 5-slide recap of this quarter's numbers," the same way you would in chat, and Slides answers or acts on it directly. This is the real mechanism behind something like a report request that arrives in Mail turning into a finished deck: Dispatch (or the app that received the message) delegates the request to Slides' agent, and Slides handles it like any other prompt. **Staying decoupled.** Slides never needs to know a sibling app's credentials, or vice versa, for any of this. The A2A protocol and the shared Creative Context Library sit between apps, so Slides only has to answer a real request or expose a real shared resource. It doesn't need to know who's calling, or how. ## What's next - [**Slides**](/docs/template-slides) — the overview and getting-started steps - [**Features**](/docs/template-slides-features) — decks and design systems - [**Talk to the Agent**](/docs/template-slides-agent) — prompts by task and what the agent sees - [**Developer Guide**](/docs/template-slides-developers) — quick start, actions, data model, and routes - [**Dispatch**](/docs/template-dispatch) — the workspace control plane these patterns run under - [**A2A Protocol**](/docs/a2a-protocol) — how apps discover, authenticate with, and call each other - [**Multi-App Workspace**](/docs/multi-app-workspace) — the general pattern of composing first-party apps instead of nesting them