Gemini CLI
Gemini CLI integrations use the same scoped-key contract as other first-party agents. Gemini/Vertex is not the default UnifiedMemory cognition lane; MiniMax is the default UM-owned cognition provider, while Google Memory Bank remains a managed co-processor.
Scope and capabilities
| Setting | Value |
|---|---|
| Source app | gemini |
| Default container | jeethendra |
| Default scope | own |
| MCP URL | https://edge-api.jithendranara.dev/mcp |
Install
gemini mcp add --transport http --scope user \
-H "Authorization: Bearer <scoped-key>" \
unified-memory https://edge-api.jithendranara.dev/mcp
Verify
List MCP tools from Gemini CLI and run a small recall canary. The response
should identify effective source app gemini and should not expose other
agents' working memory.
Memory behavior
- Gemini may recall own working/session memory and approved canonical facts.
- Google Memory Bank output is comparison evidence, not automatic truth.
- MiniMax remains the default UnifiedMemory judge/cognition lane.
Risk notes
If Gemini tooling has its own memory layer, keep it separate from UnifiedMemory writeback unless the integration explicitly calls retain or writeback with a scoped key.