Entire-Generated Files - Entire
Commit or keep local
| Path | Commit? | Use for |
|---|---|---|
.entire/settings.json |
Yes, when Entire is part of the project | Shared project settings, such as checkpoint storage, team redaction rules, and default repository behavior |
.entire/.gitignore |
Yes | Keeping local Entire files out of normal commits |
.entire/redactors/ |
Yes, for shared rule packs | Team redaction rules that should apply to everyone working in the repository |
.entire/settings.local.json |
No | Personal overrides, debug logging, private rules, and machine-specific settings |
.entire/redactors/local/ |
No | Personal redaction rule packs |
.entire/logs/ |
No | Local diagnostic logs |
.entire/tmp/ |
No | Temporary runtime files |
.entire/metadata/ |
No | Local metadata generated while Entire runs |
.entire/current_session |
No | Pointer to your current local session |
If you are trying Entire locally before adopting it for the project, keep .entire/settings.json local until the team decides to share Entire configuration.
Files stored elsewhere
Checkpoint data is not committed from your working tree. Entire stores checkpoint metadata on the entire/checkpoints/v1 branch or in a configured checkpoint remote. Global settings live at ~/.config/entire/settings.json. Agent hook files live in agent-specific folders, such as .claude/, .codex/, .cursor/, and .gemini/.