Memory hooks with Gemini CLI?

[timkjr]

Has anyone tried/investigated/looked into incorporating the memory hooks into Gemini CLI? I note it includes a hooks mechanism but I haven't looked thoroughly to see if/how it would match. Curious if anyone has looked into this.

[doobidoo]

Great question, @timkjr! I've been looking into this, and I agree that a hook system similar to the one for Claude
Code would be a fantastic addition to the Gemini CLI. The existing claude-hooks for the MCP Memory Service provide a
great blueprint.

I've put together a high-level plan for how this could be implemented. The goal would be to create a generic hook
mechanism within the Gemini CLI that could then be used by a ported version of the MCP Memory Service hooks.

Plan for a Gemini CLI Hook System

1. Core CLI Feature:

   • The Gemini CLI itself would be updated to support a hook system.
   • It would look for a configuration file, something like ~/.gemini/hooks.json, to discover and manage hooks.

2. Hook Configuration (~/.gemini/hooks.json):

   • This file would allow users to register scripts to be executed on specific lifecycle events.
   • Example:

    1         {
    2           "hooks": [
    3             {
    4               "name": "McpMemorySessionStart",
    5               "event": "session-start",
    6               "command": "node ~/.gemini/hooks/mcp-memory/session-start.js",
    7               "enabled": true
    8             },
    9             {
   10               "name": "McpMemorySessionEnd",
   11               "event": "session-end",
   12               "command": "node ~/.gemini/hooks/mcp-memory/session-end.js",
   13               "enabled": true
   14             }
   15           ]
   16         }

3. Lifecycle Events:

   • The system would be built around events. The most critical for memory integration would be:
     • session-start: To load context when the CLI starts.
     • session-end: To save a summary of the session when the CLI closes.

4. Porting the Hooks:

   • The existing claude-hooks are written in Node.js and primarily communicate with the MCP Memory Service via
     HTTP. This makes them highly portable.
   • The main work would be to create a new gemini-hooks repository and adapt the scripts to the Gemini CLI's
     specific way of passing context (e.g., via stdin).

This approach would bring the powerful, automated context management of the MCP Memory Service to the Gemini CLI. It
would also open the door for many other interesting community-built integrations.

I think this is a very promising direction. What does everyone think of this as a starting point?

[doobidoo]

Have added a feature Request at google-gemini/gemini-cli#15882

[timkjr]

This might be a moot question, Gemini now has a "migrate claude hooks option. https://geminicli.com/docs/hooks/#migration-from-claude-code, "gemini hooks migrate --from-claude". I'm experimenting with it currently.