> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entire.com/llms.txt
> Use this file to discover all available pages before exploring further.

# dispatch

> Generate a dispatch summarizing recent agent work.

Generate a dispatch summarizing recent agent work.

```bash theme={null}
entire dispatch [flags]
```

`entire dispatch` has two modes:

* **Cloud mode** (default) generates a dispatch from Entire server data
* **Local mode** (`--local`) generates a dispatch from local repository data using your locally installed agent CLI

Cloud mode carries the requirement below, and covers repositories placed in exactly one jurisdiction — the cell for that jurisdiction generates the dispatch. Local mode reads the repository on disk instead, so it works without a published repository.

> [!NOTE]
>
> **Requires a published repository.** Entire answers this from its own servers rather than from your local clone, so the repository must be published somewhere Entire can reach and its checkpoints pushed.
>
> Publish by [creating an Entire repository](/guides/repositories/entire-native-repositories) or by [mirroring a GitHub repository](/guides/repositories/mirrors), then `git push`. `entire enable` does not create or push to a remote for you.
>
> Your work becomes available shortly after it reaches Entire, so give a recent push a couple of minutes before treating a missing result as a problem.

If you run `entire dispatch` with no flags in an interactive terminal, Entire launches a guided wizard. In non-interactive contexts, or whenever you provide flags, it prints markdown output directly.

| Flag | Description |
| - | - |
| `--local` | Generate via the locally installed agent CLI instead of the Entire server |
| `--since TIME` | Start of the time window. Accepts Go durations, relative times, or ISO dates. Defaults to `7d`. |
| `--until TIME` | End of the time window. Defaults to now. |
| `--all-branches` | Include every existing local branch. Only valid with `--local`. |
| `--repos REPO` | Limit cloud dispatch to up to 5 repositories, comma-separated. Each is forge-qualified: `gh/OWNER/REPO` or `et/PROJECT/REPO`. |
| `--voice PRESET_OR_TEXT` | Customize the dispatch tone with a preset such as `neutral` or `marvin`, or provide your own text. |
| `--agent NAME` | Local text-generation agent to use. Only valid with `--local`. |
| `-j, --jurisdiction SLUG` | Jurisdiction whose cell generates the cloud dispatch, such as `us` or `eu`. Defaults to your home jurisdiction. |

Use cloud mode when you want a dispatch from Entire-tracked repo data:

```bash theme={null}
# Default dispatch for recent work in the current repo
entire dispatch

# Limit cloud dispatch to specific repos
entire dispatch --repos gh/entireio/cli,et/myproject/service
```

Use local mode when you want a dispatch from local repository history:

```bash theme={null}
# Local dispatch from the current branch
entire dispatch --local

# Local dispatch across all local branches
entire dispatch --local --all-branches
```

You can also customize the dispatch voice:

```bash theme={null}
entire dispatch --voice neutral
```

> [!NOTE]
>
> `--repos` cannot be combined with `--local`, and `--all-branches` only applies to `--local`.

> [!NOTE]
>
> Cloud dispatch supports up to 5 repositories per request, and each must be forge-qualified as `gh/OWNER/REPO` or `et/PROJECT/REPO`. A bare `owner/repo` is refused.

## Jurisdictions

A cloud dispatch covers repositories placed in exactly one jurisdiction, and is generated by that jurisdiction's cell. Without `--jurisdiction`, Entire uses your home jurisdiction, which [`entire auth status`](/cli-reference/auth#auth-status) reports.

A repository mirrored only elsewhere is reported as not found in your home jurisdiction. Pass `--jurisdiction SLUG` to target the jurisdiction the repository is actually placed in:

```bash theme={null}
entire dispatch --repos gh/entirehq/ferrata --jurisdiction us
```