Persistent session continuity for the Gemini CLI.

Gemini Workspace History is a Gemini CLI extension designed to provide continuity between AI-assisted coding sessions within a specific workspace. It solves "context amnesia" by automatically restoring the latest technical summary at the start of every session and archiving transcripts at the end.

• Context Restoration: Automatic injection of the latest session summary (active-context.md) into the current context.
• Session Archiving: Automatic Gzip compression of session transcripts for long-term history.
• Controlled Exit: Custom close-workspace command ensures a high-quality summary is generated before closing.
• Workspace Summarizer Skill: A dedicated skill to assist in generating and managing session summaries.
• Local Storage: All history (summaries, compressed transcripts, and active context) is kept within the project's .gemini-workspace-history/ directory.

To use this extension in your project, link it to your Gemini CLI:

gemini extension link .

1. Start: When you start a new session (gemini), the on-start.js hook identifies the latest summary and prepares active-context.md.
2. Work: The Gemini CLI automatically loads active-context.md into your session context.
3. End: Use the /close-workspace (or your custom command name) to summarize your work and exit cleanly.

• /close-workspace: Prompts the agent to write a structured technical summary of the current session and then saves it to .gemini-workspace-history/ using standard tools before exiting. This is the recommended way to end a session to ensure continuity.

The extension maintains all its data in the .gemini-workspace-history/ directory:

• active-context.md: The summary currently being injected into the session.
• session-YYYY-MM-DD-HH-mm.json.gz: Compressed session transcripts.
• summary-YYYY-MM-DD-HH-mm.md: Individual session summaries.

• Lifecycle Hooks:
  • SessionStart: Executes hooks/on-start.js to prepare the active context from the most recent session summary and history.
  • SessionEnd: Executes hooks/on-end.js to archive the session transcript as a compressed Gzipped JSON file.
• Context Injection: The gemini-extension.json manifest is configured with contextFileName: ".gemini-workspace-history/active-context.md", which the CLI uses to automatically include the file in every session.
• Hooks Configuration: Lifecycle hooks are managed via hooks/hooks.json.
• Skills: Includes the workspace-summarizer skill to help maintain session continuity.

To verify the extension's functionality and path resolution:

npm test

The project uses a strict versioning policy. Every PR must include a version bump, which is verified by the automated test suite.

To increment the patch version based on the latest git tag:

npm run bump

This command will update both package.json and gemini-extension.json to the next patch version (e.g., 0.1.2 -> 0.1.3).