The graphify command is not found
The graphify command is not found
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.Python cannot import graphify or mcp
Python cannot import graphify or mcp
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.My assistant does not discover the skill
My assistant does not discover the skill
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.graph.json does not exist
graph.json does not exist
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.The answer reflects old code
The answer reflects old code
Run
graphify update ., then query again. Git hooks run in the background, and pulls/merges require an explicit update. Refresh document context through the skill or semantic extraction if documents changed.A refresh refuses to write a smaller graph
A refresh refuses to write a smaller graph
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.A query returns no path
A query returns no path
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.Local model extraction is slow or runs out of memory
Local model extraction is slow or runs out of memory
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.The MCP server disconnects or shows no tools
The MCP server disconnects or shows no tools
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.
PR commands fail
PR commands fail
Confirm
gh is installed and authenticated for the repository. Check the repo and base-branch options. CLI --triage additionally needs a configured model backend.