{"slug": "the-entire-cli-is-now-integrated-with-grok", "title": "The Entire CLI Is Now Integrated with Grok", "summary": "Entire released an external agent plugin that integrates its Entire CLI with xAI's Grok Build, letting developers capture Grok Build sessions and store the prompts, responses, and tool calls in Git history alongside their commits. The plugin, published in the entireio/external-agents repository, requires Entire, Grok Build, Go, and mise, and is added to a repository with the command `entire agent add grok`, which installs Grok's hooks in `.grok/hooks/entire.json`. Sessions are read back with `entire checkpoint explain --commit HEAD --full`; the Grok Bot desktop app is not supported out of the box because it does not run agent hooks.", "body_md": "OCTOBER 16, 2026 · Lizzie Siegle\n\n# The Entire CLI Is Now Integrated with Grok\n\nYou can now capture your Grok Build sessions with the Entire CLI using an [external agent plugin](https://github.com/entireio/external-agents/tree/main/agents/entire-agent-grok). The plugin connects your conversation to your commits so you and your teammates can review the prompts, responses, and tool calls behind code changes, creating a loop of continuous memory across the production cycle.\n\nConversations are stored in your Git history, right alongside your code itself.\n\nBelow, you can run each terminal command directly or ask your agent in natural language to run it for you.\n\n## Install the Plugin\n\nYou’ll need [Entire](https://docs.entire.io/installation), [Grok Build](https://x.ai/build), [Go](https://go.dev/doc/install), and [mise](https://mise.jdx.dev/getting-started.html) installed.\n\nFirst, clone the external agents repository and build the Grok plugin:\n\n```\n$git clone https://github.com/entireio/external-agents.git\ncd external-agents/agents/entire-agent-grok\nmise run build\n```\n\nThen put the binary on your PATH:\n\n```\n$mkdir -p ~/.local/bin\ncp entire-agent-grok ~/.local/bin/\nexport PATH=\"$HOME/.local/bin:$PATH\"\ncommand -v entire-agent-grok\n```\n\nThat last command prints the binary location. The export applies to your current terminal session. If `~/.local/bin` is not on your PATH, add it to your shell configuration.\n\n## Connect Grok Build to Your Repo\n\nSwitch to the repository where you want to capture sessions and add the Grok agent:\n\n```\n$cd /path/to/your/repo\nentire agent add grok\n```\n\nThis enables Entire in the repository if it isn’t already, installs Grok’s hooks in `.grok/hooks/entire.json`, and turns on `external_agents` in `.entire/settings.local.json`, which Entire’s `.entire/.gitignore` keeps out of Git.\n\n## Trust the Hooks\n\nLaunch Grok by running:\n\n```\n$grok\n```\n\nWhen Grok asks whether you trust the contents of this directory, choose **Yes**. If you already dismissed that prompt, run this inside Grok:\n\n```\n/hooks-trust\n```\n\nGrok skips project hooks until you trust the folder, but it doesn’t warn you when it skips them. If your session produces no checkpoints, be sure to check folder trust!\n\n## Give Grok a Task and Commit the Change\n\nFor a small test, ask Grok something like:\n\n```\nCreate hello.txt containing \"hello world\". Don’t commit the change yet.\n```\n\nWhen Grok finishes, return to your shell, review the change, and commit it:\n\n```\n$git add hello.txt\ngit diff --cached\ngit commit -m \"Add hello world\"\n```\n\nEntire writes the checkpoint when you commit. Run to see your Grok Build session and its checkpoint.\n\n## Read the Conversation That Led to the Commit\n\nInspect the checkpoint associated with your latest commit:\n\n```\n$entire checkpoint explain --commit HEAD --full\n```\n\nReading the transcript, you can follow what you asked Grok to do and how the model responded. Later on, when a teammate asks why `hello.txt` exists, you can both read and reference the exact session that produced it.\n\nFor your project, replace the test task with your actual task and commit using standard Git commands.\n\n## Connect Grok Bot with Your Own Plugin\n\nGrok Bot, the desktop app, doesn’t run agent hooks, so it isn’t supported out of the box. You can connect it by writing an `entire-agent-grokbot` plugin that implements the [external agent protocol](https://github.com/entireio/cli/blob/main/docs/architecture/external-agent-protocol.md) and reports each bot’s session events to Entire. Entire picks up any `entire-agent-<name>` binary on your PATH, so once your plugin is there, add it with .\n\n## Try It in Your Existing Repo\n\nEntire records other agents the same way, for example or .\n\nPick a small task you already planned to give Grok. After committing, open the checkpoint and check whether the session gives a teammate enough context to understand the change.", "url": "https://wpnews.pro/news/the-entire-cli-is-now-integrated-with-grok", "canonical_source": "https://entire.io/blog/the-entire-cli-is-now-integrated-with-grok", "published_at": "2026-10-16 00:00:00+00:00", "updated_at": "2026-10-16 18:50:25.146590+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools", "ai-tools", "agent-protocols"], "entities": ["Entire", "Grok Build", "xAI", "Entire CLI", "Grok Bot", "Lizzie Siegle", "Go", "mise"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/the-entire-cli-is-now-integrated-with-grok", "markdown": "https://wpnews.pro/news/the-entire-cli-is-now-integrated-with-grok.md", "text": "https://wpnews.pro/news/the-entire-cli-is-now-integrated-with-grok.txt", "jsonld": "https://wpnews.pro/news/the-entire-cli-is-now-integrated-with-grok.jsonld"}}