Skip to main content
Gemini CLI is Google’s command-line interface for Gemini AI. Entire supports capturing sessions from Gemini CLI, tracking your AI-assisted coding interactions. The Gemini CLI integration is in preview and may contain bugs.

Prerequisites

Enable

Entire integrates with Gemini CLI through Git hooks. When you start Gemini CLI in an Entire-enabled repository:
  1. Process Detection — Entire detects when Gemini CLI is running.
  2. File Monitoring — file changes are tracked during the session.
  3. Checkpoint Creation — created when you or the agent make a Git commit.
  4. Session Storage — data saved to the entire/checkpoints/v1 branch.
The session ends when Gemini CLI exits.
DataDescription
File changesAll files modified during the session
TimestampsSession and checkpoint timing
Session boundariesStart and end of Gemini sessions
CheckpointsRewind points within sessions
Rewind during sessions. Use entire checkpoint rewind to restore to a previous checkpoint during or after a Gemini CLI session. See the checkpoint rewind command reference for full flag documentation.Resume previous sessions. Switch to a session’s branch with entire session resume BRANCH. The CLI restores the session log if needed and prints the command to resume the session. See the session resume command reference for full flag documentation.Explain commits. Inspect any commit or checkpoint with entire checkpoint explain. See the checkpoint explain command reference for full flag documentation.
  • Conversation transcripts may not be captured depending on Gemini CLI version.
  • Session detection relies on process monitoring rather than dedicated lifecycle hooks.
  • Token usage is not tracked.
  • Works best when you commit at logical stopping points, or tell the agent to handle committing.
Commit at logical points. Commit when you’ve made meaningful progress:
Check status regularly. Monitor your session with entire status.

Troubleshooting

  1. Ensure you’re in an Entire-enabled repo: entire status
  2. Verify Gemini CLI is running from within the repository
  3. Check Git hooks are installed: ls .git/hooks
  1. Checkpoints require file changes
  2. Make sure Gemini is modifying files in the repository
  3. Check your settings in .entire/settings.json