Dispatches - Entire
What Dispatches summarize
Dispatches can summarize recent work from:
- checkpoints created from agent-assisted commits
- sessions, prompts, transcripts, and tool activity
- commits connected to captured agent work
- one repository, multiple repositories, or a narrower branch and time window
A dispatch is a summary. Use it to get oriented, write status updates, or prepare a handoff. Use Checkpoints when you need to inspect the exact prompt, transcript, files, and diff behind a change.
Where to generate Dispatches
| Surface | Use it when |
|---|---|
| Entire.io | You want to choose repositories, preview the markdown visually, and copy a stakeholder-ready update. |
| Entire CLI | You are already in the terminal, want scriptable markdown output, or need a local summary from repository data. |
Common uses
- Write a weekly engineering update from agent-assisted work
- Summarize progress across several repositories
- Create a focused recap for one repo and branch
- Prepare a non-technical brief from technical work
- Catch up before reviewing a branch or continuing a project
Before you start
Dispatches work best when:
- Entire is capturing agent work in the repositories you choose
- checkpoints or sessions have been pushed or are available locally
- you choose a time window that contains recent activity
- you are authenticated with
entire loginwhen using cloud-backed CLI dispatches.
Continue with
[**Dispatches in Entire.io**
Generate and preview dispatches in the web app.](https://docs.entire.io/guides/dispatches/dispatches-in-entire-io)
[**Dispatches in CLI**
Generate markdown dispatches from your terminal.](https://docs.entire.io/guides/dispatches/dispatches-in-cli)
[**Troubleshooting**
Fix missing Dispatches, thin summaries, scope issues, and CLI mode conflicts.](https://docs.entire.io/guides/dispatches/troubleshooting)