gra-context

GRA gives Claude Code a map of your Python codebase, so it finds the code it needs and understands how the parts connect before it starts changing things.

Claude asks GRA a question in plain words ("where are redirects followed?") and gets back the relevant functions and classes, each with a one-line explanation, its file and line range, how it connects to the rest, and the tests that cover it. GRA keeps the map current as files are edited, and remembers what earlier sessions did in the same code.

Install

pipx install gra-context          # or: uv tool install gra-context
cd /path/to/your/codebase
gra setup

The first time, gra setup asks for your email and saves a free key on your computer. Then start a new Claude Code session in that codebase. The first time, GRA builds the map in the background; after that it follows your edits by itself. Run gra setup once in each codebase you want GRA in (your key is remembered). On another computer, run gra key on this one and gra setup --api-key <your key> on the new one.

• --scope project turns GRA on for everyone working in the repository, through .mcp.json.
• --claude-md adds a line to CLAUDE.md telling Claude to start from GRA.

Your code and data

The map, the explanations and the work history are stored on your machine (~/.local/share/gra/), never inside your codebase. To write explanations, GRA sends one function's code at a time to GRA's service, which does not store it. Searching the map runs locally.

Commands

gra setup [--api-key K]          turn GRA on for the current codebase
gra key                          show your saved key, to use it on another computer
gra query "question" [--repo R]  what Claude gets back for a question
gra show <name> [repo]           a symbol, its explanation and its connections
gra install [repo]               build the map now, plus a git post-commit hook

Requires Python 3.10+ and a GRA key (free, from gra setup). Proprietary software; see LICENSE.