## Documentation Index

Fetch the complete documentation index at: [/llms.txt](https://docs.entire.io/llms.txt)

Use this file to discover all available pages before exploring further.

Use this page when you need more detail about what Entire is doing locally or need to confirm which settings are active. Most diagnostic output is local to your machine. Turn on debug logging temporarily unless the whole team needs the same verbosity.

## Start here if

Use this page to:

- turn on debug logging while investigating an issue
- confirm which settings Entire is using
- run a repository health check
- view logs or create a diagnostic bundle

## Log level

`log_level` controls how much detail Entire writes to operational logs. The default is `info`; use `debug` while investigating.

- Temporary override

- Local settings

- Project settings

Use `ENTIRE_LOG_LEVEL` when you need debug output for one command or one shell session.

```
ENTIRE_LOG_LEVEL=debug entire status
```

`ENTIRE_LOG_LEVEL` takes precedence over settings files.

Use local settings for temporary debug logging or machine-specific troubleshooting.

.entire/settings.local.json

```
{
  "log_level": "debug"
}
```

Use project settings only when the whole repository should use the same log level.

.entire/settings.json

```
{
  "log_level": "debug"
}
```

Supported values are `debug`, `info`, `warn`, and `error`.

## Inspect active settings

Run:

```
entire status --detailed
```

Use this after editing settings to confirm Entire is reading the value you changed and to see which settings file supplied it.

## Check repository health

Run:

```
entire doctor
```

Use `entire doctor` when sessions look stuck, Git hooks are not firing, checkpoint data is not syncing, or `entire status` shows warnings. It checks repository setup, hook state, checkpoint metadata, and common session problems.

## View or share diagnostics

Entire writes local diagnostic logs under `.entire/logs/`. Keep logs local unless someone asks for a specific file or bundle while troubleshooting.

- View logs

- Create bundle

Show recent operational logs with:

```
entire doctor logs
```

To stream new log lines while you reproduce an issue, run:

```
entire doctor logs --follow
```

Create a diagnostic bundle for an issue report with:

```
entire doctor bundle
```

Diagnostic bundles are redacted by default. Use `--raw` only when support has asked for an unredacted bundle.

For other local runtime files under `.entire/`, see [Entire-Generated Files](https://docs.entire.io/guides/configuration/entire-files).

## Trace slow hooks

Hook performance traces are only available at debug log level. Turn on debug logging, reproduce the slow Git command, then run:

```
entire doctor trace
```

Use this when `git commit` or `git push` works but feels slower than expected.

## Verify logging changes

After changing logging settings, rerun the command you were investigating and check the logs:

```
entire doctor logs
```