Continuity
Graphify Code Context
Map code, docs, schemas, and configuration into a queryable relationship graph before broad source browsing — then keep it current as the repository changes.
Key ideas
- Relationship graph
- A navigable map of the files, symbols, and concepts that connect across an approved repository.
- Official package
- Install the official PyPI distribution named graphifyy; the command you run afterwards is graphify.
- Keep it fresh
- After the first graph exists, graphify update . refreshes code relationships without a new semantic extraction.
A practical starting sequence
- Install uv from its official source, then run uv tool install graphifyy — the official package name has two y characters.
- Confirm the installation with graphify --version before connecting it to an agent or a repository.
- Register only the integration you use: graphify install --platform codex or graphify install --platform hermes. Read the generated skill files before committing or sharing them.
- In an approved repository, ask your supported coding assistant to build the first graph; use Graphify's documented agent command rather than guessing terminal flags.
- Use graphify query, graphify explain, and graphify path to navigate the generated graph before broad source browsing. Run graphify update . after code changes.
- Start on a disposable or non-production repository. Review the extraction backend first: semantic extraction can use a configured model provider, so do not point it at secrets or customer exports.
Last reviewed: 2026-08-29