Skip to main content

Install errors

uv tool install graphify: no solution found when resolving dependencies

The package name has two y’s. There is no graphify package on PyPI, so uv can’t resolve it. Install graphifyy instead:
The command it installs is still graphify. See Installation.

Error: could not find a version that satisfies the requirement graphify (no matching distribution found for graphify)

Same cause with pip or pipx. Use the graphifyy package:
Other packages with similar names are not the Graphify Labs package.

zsh: command not found: uv

uv isn’t installed, or your shell can’t find it yet. Install it with Homebrew (brew install uv) or uv’s own installer:
Open a new terminal and run uv --version. If it’s still not found, the install folder isn’t on your PATH; see the uv installation guide.

Unrecognized command '/graphify' in Claude Code

The Graphify skill isn’t installed for Claude Code, or Claude Code hasn’t loaded it yet. Register it:
This copies the skill to ~/.claude/skills/graphify/SKILL.md. Then restart Claude Code, open your project, and send /graphify . again. If you registered with --project, run Claude Code from that project’s root. See Claude Code.

Other problems

Run uv tool update-shell or pipx ensurepath, then open a new terminal. Verify that the package you installed was graphifyy. A GUI app may need an absolute executable path even when your terminal finds it.
Your command may be using a different Python environment. Install the mcp extra in the environment that launches the server, or use the graphify-mcp executable from the uv tool installation. See MCP setup.
Register the exact platform with graphify install --platform <name>. Confirm whether you intended a user or project installation. Refresh the assistant’s skills or restart it. In Codex, use the skill picker; not every client has the same slash-command behavior.
Run the build workflow before querying. For a local test, use graphify extract . --code-only at the project root. For another location, pass --graph /absolute/path/to/graph.json to queries and the absolute path to MCP.
Run graphify update ., then query again. Git hooks run in the background, so a query right after a commit or pull can briefly see the old graph. Without hooks, pulls and merges need an explicit update. Refresh document context through the skill or semantic extraction if documents changed.
Inspect the warning and confirm the smaller result is intentional. Missing dependencies or failed semantic calls can produce incomplete output. After an intentional removal or refactor, use graphify update . --force to allow replacement.
Check the node names and graph version. Paths respect stored direction by default; try --undirected only if you want general connectivity. Missing edges can reflect unresolved or unsupported code, not necessarily the absence of a relationship.
Lower --token-budget and --max-concurrency. Check that the chosen model supports the input and output size. Adjust GRAPHIFY_OLLAMA_NUM_CTX only with the local model’s memory needs in mind.
Run its configured command manually and inspect stderr. Check the MCP extra, executable path, and graph path. Refresh the client after changes. For HTTP, verify the endpoint path, reachability, and authentication header.
Confirm gh is installed and authenticated for the repository. Check the repo and base-branch options. CLI --triage additionally needs a configured model backend.
Not if you’ve run graphify hook install. A pull that merges fires the post-merge hook, and git pull --rebase fires post-rewrite. Both rebuild the code graph in the background. Docs, PDFs and images still need /graphify . --update. See Keep your code graph up to date.

Get help

Open a GitHub issue or join Discord. Include the installed version, operating system, exact command, and a sanitized error. A small reproducible example is more useful than a private repository dump.

Next steps

Try it in Graphify

We build and host the graph for you, and review your pull requests with it. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.

When something fails in Graphify

Fixes for builds, sign-in, and agent connections.

Installation

Reinstall or upgrade the local package.