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 takes precedence over settings files.debug, info, warn, and error.
Inspect active settings
Run:Check repository health
Run: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:To stream new log lines while you reproduce an issue, run:
.entire/, see Entire-Generated 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:git commit or git push works but feels slower than expected.