Skip to main content
Use configuration docs when you need to change how Entire behaves in a repository, on your machine, or during Git and agent workflows. Use the table below to find the guide for the part of Entire you want to configure.

​
What are you configuring?

If you want to configure…Go to
Local, project, or global settings filesLocal, Project, and Global Settings
Which Entire-generated files should be committed or kept localEntire-Generated Files
Where checkpoint data is stored or pushedCheckpoint Storage
Git commit and push hooks, including GUI Git clientsGit Hooks
Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, or external agent hooksAgent Hooks
Redaction rules, PII, telemetry, or checkpoint commit signingPrivacy and Redaction
Debug logs, diagnostics, or effective settingsLogging and Diagnostics
Saved review profiles for entire reviewReview Profiles

​
How configuration is layered

Entire merges settings from multiple places. More specific settings win:
  1. Local settings: .entire/settings.local.json
  2. Project settings: .entire/settings.json
  3. Global settings: ~/.config/entire/settings.json
  4. Defaults
Use project settings for behavior the whole team should share. Use local settings for personal preferences, machine-specific setup, debug logging, or private redaction rules.

​
Common paths

Local, project, and global settings

Choose local, project, or global settings for a configuration change.

Entire-generated files

Decide which Entire-generated files belong in Git and which should stay local.

Store checkpoints elsewhere

Configure checkpoint remotes, local-only checkpoint data, and push behavior.

Fix GUI Git commits

Use absolute Git hook paths when GUI clients cannot find the Entire binary.

Control privacy settings

Configure redaction, telemetry, and checkpoint commit signing.