Setup — Gemini CLI

Files

Level	File	Purpose
0	~/GEMINI.md	Global project map — loaded on every session
1	<project-root>/GEMINI.md	Per-project context — loaded when working inside the project
1.5	<project-root>/graphify-out/GRAPH_REPORT.md	Optional — Graphify graph

Step-by-step

Level 0 — global GEMINI.md

cp templates/level-0.md.template ~/GEMINI.md
# edit with your real projects and servers

Gemini CLI auto-discovers GEMINI.md in $HOME and in the current working directory.

Level 1 — per-project GEMINI.md

cd ~/projects/your-project-a
cp /path/to/ai-context-hierarchy/templates/level-1.md.template GEMINI.md

When you run gemini from inside the project, both files are loaded; the local one takes precedence on conflict.

Level 1.5 — Graphify with BeforeTool hook

pip install graphifyy
cd ~/projects/your-project-a
graphify .
graphify gemini install        # registers a BeforeTool hook

Verify

gemini
> What projects do I have?

Should answer from ~/GEMINI.md without read_file calls beyond the GEMINI.md files themselves.

MCP

Gemini CLI does not support MCP servers as of writing. If you need Graphify graph queries on Gemini, use the BeforeTool hook approach above (the agent reads GRAPH_REPORT.md directly) rather than the MCP server pattern used for Claude Desktop.

Removing

graphify gemini uninstall
rm <project>/GEMINI.md
rm ~/GEMINI.md