Troubleshooting - Entire

Documentation Index

Use this page when Dispatches are missing, the summary is empty or too thin, or the CLI command rejects the scope you provided.

Dispatches are not visible in Entire.io

Dispatches may be enabled gradually for Entire.io accounts. If you do not see Dispatches in the sidebar or command palette:

The summary is empty or too thin

Check whether the selected scope contains captured work. Try this:

entire dispatch --local

The wrong repositories or branches are included

Check the dispatch scope. In Entire.io, branch selection appears only when you select one repository. If you select multiple repositories, Dispatches use each repository’s default branch. In the CLI, pass cloud repository slugs with owner/repo format:

entire dispatch --repos entireio/cli,entireio/entire.io

--repos does not work with --local

--repos is for cloud dispatches. --local reads from the local repository instead. Use cloud mode for specific remote repositories:

entire dispatch --repos entireio/cli

Use local mode for the current checkout:

entire dispatch --local

--all-branches did not include a branch

--all-branches only includes existing local branches in local mode. Renamed or deleted branches are skipped. Check local branches first:

git branch

Then run:

entire dispatch --local --all-branches

The voice or audience is wrong

Use a preset voice or provide custom guidance.

entire dispatch --voice neutral
entire dispatch --voice "Audience: leadership. Focus on impact and risks."

Still stuck?

Include these details when asking for help:

You can file an issue at github.com/entireio/cli or ask in the Entire Discord.