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

# Troubleshooting

> Resolve common issues with Entire.io — Unknown author, missing checkpoints, GitHub App permissions

Common issues and how to fix them.

## "Unknown author" on a checkpoint

Entire shows `Unknown author` when the commit associated with a checkpoint does not have an author identity that GitHub can match to a user.

This usually happens when:

* The commit was authored with a different or unexpected Git identity
* The commit author email is not associated with a GitHub account
* GitHub returned commit metadata without a matched author username

To fix it, set your Git author identity to an email that's associated with your GitHub account, then create and push a new commit.

<Note>
  `.entire/settings.json` does not affect commit author identity — only your Git config does.
</Note>

## Missing checkpoints / sync delay

If a checkpoint you expected doesn't appear on entire.io:

1. **Check the shadow branch.** Open `entire/checkpoints/v1` on GitHub and confirm the checkpoint folder is there. If it isn't, the CLI never pushed it — re-run your last `entire` command and watch for errors.
2. **Wait briefly.** Entire.io receives push webhooks from GitHub when checkpoints land on the shadow branch, so new checkpoints typically appear within seconds. A delivered webhook can occasionally be delayed; a daily reconciliation pass catches anything missed.
3. **Confirm the GitHub App still has access.** If the Entire GitHub App was uninstalled or its repository allow-list changed, sync stops for affected repos. See "GitHub App permissions" below.

## GitHub App permissions issues

If you can sign in but no repositories appear, or repositories you expect are missing:

1. Open **Repositories** in the sidebar and check the list
2. If a repo you expect isn't there, install or update the Entire GitHub App on the relevant user or organization via GitHub's app settings
3. Verify the repositories you want are in the app's allow-list

When the GitHub App is reinstalled or its repository allow-list changes, Entire receives an installation webhook from GitHub and updates access automatically — you don't need to sign out and back in.

## Where to file bugs

If you've worked through this page and the issue persists:

* **GitHub Issues** — [github.com/entireio/cli](https://github.com/entireio/cli)
* **Discord** — join the [Entire Discord](https://discord.gg/jZJs3Tue4S) for live help

When filing a bug, include:

* The CLI version (`entire version`)
* The name of the AI coding agent and its version
* A short description of what you expected vs. what happened
* The checkpoint ID, if there is one

## Continue with

<CardGroup cols={2}>
  <Card title="Overview" icon="book" href="/web/overview">
    Refresh on what entire.io does and how it relates to the CLI.
  </Card>

  <Card title="Connect a repository" icon="github" href="/web/connect-repository">
    Re-check your GitHub App authorization.
  </Card>
</CardGroup>