Gemini CLI - Entire
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
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
- Entire CLI installed
- Gemini CLI installed
- A Git repository with Entire enabled
Enable
entire agent add gemini
gemini
How it works
Entire integrates with Gemini CLI through Git hooks. When you start Gemini CLI in an Entire-enabled repository:
- Process Detection — Entire detects when Gemini CLI is running.
- File Monitoring — file changes are tracked during the session.
- Checkpoint Creation — created when you or the agent make a Git commit.
- Session Storage — data saved to the
entire/checkpoints/v1branch.
The session ends when Gemini CLI exits.
What gets captured
| Data | Description |
|---|---|
| File changes | All files modified during the session |
| Timestamps | Session and checkpoint timing |
| Session boundaries | Start and end of Gemini sessions |
| Checkpoints | Rewind points within sessions |
Features
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.
Caveats and limitations
- 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.
Best practices
Commit at logical points. Commit when you’ve made meaningful progress:
git add .
git commit -m "Implement feature with Gemini assistance"
Check status regularly. Monitor your session with entire status.
Example workflow
# 1. Setup
cd my-project
entire agent add gemini
# 2. Start Gemini CLI
gemini
# 3. Work with Gemini
# Ask it to write code, make changes, etc.
# 4. Check session (in another terminal)
entire status
# 5. Rewind if needed
entire checkpoint rewind
# 6. Commit when ready
git add .
git commit -m "Add feature with Gemini"
# 7. Push
git push
Troubleshooting
Session not detected
- Ensure you’re in an Entire-enabled repo:
entire status - Verify Gemini CLI is running from within the repository
- Check Git hooks are installed:
ls .git/hooks
No checkpoints created
- Checkpoints require file changes
- Make sure Gemini is modifying files in the repository
- Check your settings in
.entire/settings.json