{"slug": "how-to-enable-entire", "title": "How to Enable Entire", "summary": "Entire, a tool that captures the context behind AI-assisted code changes and links it to Git history, has introduced a new setup process. Developers can enable Entire by running 'entire enable -y' from the root of their Git repository, which installs hooks and creates project configuration to capture session context. New setups default to storing checkpoints under 'refs/entire/checkpoints/', while existing repositories can continue using the branch-based approach.", "body_md": "[Entire](https://entire.io/) captures the context behind AI-assisted code changes and connects it to your Git history.\n\nIt preserves details such as prompts, tool calls, file changes, and session transcripts as [checkpoints](https://docs.entire.io/overview). A checkpoint is a versioned record of the work completed during an agent session, linked to the Git commit that resulted from it.\n\nHere’s how to enable Entire and prepare your repository for its first checkpoint.\n\nFrom the root of your Git repository, run:\n\n```\nentire enable -y\n```\n\nThe `-y`\n\nflag accepts the default setup options, including enabling Entire for all [supported coding agents](https://docs.entire.io/agents/overview).\n\nEntire installs the necessary hooks and creates its project configuration. These hooks capture the context from your agent sessions and connect it to your commits.\n\nNew setups use Git refs by default, storing each checkpoint independently under:\n\n```\nrefs/entire/checkpoints/\n```\n\nEntire also supports storing checkpoints together on a dedicated branch:\n\n```\nentire/checkpoints/v1\n```\n\nBoth approaches keep your [session history](https://docs.entire.io/glossary) separate from your working branch, so transcripts and checkpoint metadata do not clutter your code commits.\n\nTo select the branch-based option explicitly, run:\n\n```\nentire enable -y --checkpoint-backend branch\n```\n\nExisting repositories using `entire/checkpoints/v1`\n\ncan continue using it, while new repositories use the refs-based approach by default.\n\nIf you want to review the setup options and choose which agents to connect, run:\n\n```\nentire enable\n```\n\nEntire will guide you through the configuration process.\n\nYou can also select a checkpoint storage option explicitly:\n\n```\nentire enable --checkpoint-backend refs\n```\n\nOr:\n\n```\nentire enable --checkpoint-backend branch\n```\n\nOnce setup is complete, check the repository’s status:\n\n```\nentire status\n```\n\nYou’ll see which agents are connected, where checkpoints will be synchronized, and whether any agent sessions are active.\n\nAfter you work with an agent and create a Git commit, you can view the resulting checkpoints with:\n\n```\nentire checkpoint list\n```\n\nYour repository is now ready to capture the context behind your agent-assisted work.\n\nFor a complete walkthrough, visit our [Quickstart](https://docs.entire.io/quickstart). If you are working with sensitive repositories, review Entire’s [security and privacy documentation](https://docs.entire.io/security).\n\nHappy trails!", "url": "https://wpnews.pro/news/how-to-enable-entire", "canonical_source": "https://dev.to/entire/how-to-enable-entire-4h9l", "published_at": "2026-08-14 22:17:46+00:00", "updated_at": "2026-08-14 22:25:00.294957+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents"], "entities": ["Entire"], "alternates": {"html": "https://wpnews.pro/news/how-to-enable-entire", "markdown": "https://wpnews.pro/news/how-to-enable-entire.md", "text": "https://wpnews.pro/news/how-to-enable-entire.txt", "jsonld": "https://wpnews.pro/news/how-to-enable-entire.jsonld"}}