Use Palimem with Gemini CLI
Connect Palimem to the Gemini CLI using ai-memory connect gemini. The helper merges a memory-service entry into ~/.gemini/settings.json (or a project .gemini/settings.json).
Prerequisites
Section titled “Prerequisites”- Gemini CLI installed
- Node.js 18+
- Repository cloned and Node dependencies installed:
Terminal window cd app && npm install
Recommended install
Section titled “Recommended install”From your repository root (user-level config):
node app/scripts/ai-memory.js connect gemini \ --project-root "$(pwd)" \ --data-dir .ai-memory/dataDefault target: ~/.gemini/settings.json. Set GEMINI_HOME to override the config directory.
Project-level config
Section titled “Project-level config”node app/scripts/ai-memory.js connect gemini \ --project-root "$(pwd)" \ --project-config .gemini/settings.json \ --data-dir .ai-memory/dataConfig block
Section titled “Config block”The committed sample lives at examples/gemini-cli/.gemini/settings.json.sample:
{ "mcpServers": { "memory-service": { "command": "node", "args": ["/absolute/path/to/repo/app/scripts/memory-service-mcp.js"], "env": { "MEMORY_SERVICE_DATA_DIR": "/absolute/path/to/repo/.ai-memory/data" } } }}Use absolute paths. The ai-memory connect gemini CLI resolves them automatically.
Verification
Section titled “Verification”Restart Gemini CLI after writing settings. Invoke memory_status via MCP.
Smoke test (non-interactive):
bash examples/gemini-cli/demo/gemini-smoke.shThe smoke starts the MCP server via stdio and verifies memory_status responds with all eleven tools.
Agent prompt
Section titled “Agent prompt”Set up Palimem as governed local memory for this Gemini CLI session.
- Project: Palimem (spec v1.7.0)- Run: node app/scripts/ai-memory.js connect gemini --project-root "$(pwd)" --data-dir .ai-memory/data- Verify: tools/list (11 tools), then memory_status — expect ok and index_status current
Use local data directory .ai-memory/data. Do not enable cloud services.CLI options
Section titled “CLI options”| Flag | Purpose |
|---|---|
--config PATH |
User settings.json (default: ~/.gemini/settings.json) |
--project-config PATH |
Also write project .gemini/settings.json |
--project-root PATH |
Repo root for resolving script paths |
--data-dir PATH |
MEMORY_SERVICE_DATA_DIR (default: .ai-memory/data) |
--replace |
Overwrite existing memory-service entry |
--dry-run |
Print merged JSON without writing |
Troubleshooting
Section titled “Troubleshooting”MCP server not listed
Restart Gemini CLI after writing settings.json.
ENOENT on memory-service-mcp.js
Run cd app && npm install.
Existing entry refused
Re-run with --replace:
node app/scripts/ai-memory.js connect gemini \ --project-root "$(pwd)" --data-dir .ai-memory/data --replaceWrong config directory
Set GEMINI_HOME to point at the directory containing settings.json.
Seed memory (optional)
Section titled “Seed memory (optional)”python3 app/import_markdown.py \ --data-dir .ai-memory/data \ examples/markdown/USER.md.sample \ examples/markdown/MEMORY.md.sampleNext steps
Section titled “Next steps”- Codex — another CLI MCP integration
- Palimpsest model
- MCP tools reference