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
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 or by mirroring a GitHub repository, 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.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.
Use cloud mode when you want a dispatch from Entire-tracked repo data:
--repos cannot be combined with --local, and --all-branches only applies to --local.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 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: