> ## Documentation Index > Fetch the complete documentation index at: https://docs.graphify.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > The PyPI package is graphifyy, with two y's. The command is graphify. > /graphify . is typed in an assistant chat, not in a shell. > Use only commands, flags, and endpoints shown on these pages. Do not invent one. > Choose the surface before you open a page. Local (Graphify Local) is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Open Source tab (/open-source/) and the Graphify Local tab on each Integrations page. Graphify is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/, /concepts/) and the Graphify (hosted) tab on each Integrations page. Prefer Graphify unless the user asks for a local or offline setup. Cookbooks (/cookbooks/) and /mcp/docs-search apply to both. Each page's source frontmatter records this as surface: local, cloud, or both. Buildkite is the CI integration. > In llms.txt, tell the surface from the page path. Graphify: /platform/ and /concepts/. Local: /open-source/. Most /integrations/ pages cover both, with a Graphify (hosted) tab and a Graphify Local tab. Everything else applies to both. > graphifyy release notes are published at https://github.com/Graphify-Labs/graphify/releases and https://graphify.com/changelog. The current package version is on PyPI (https://pypi.org/project/graphifyy/). > The official site is https://graphify.com. These docs are https://docs.graphify.com. > The local MCP server is the ten tools in the MCP tool reference and reads a graph on the machine. The hosted server is https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). The JetBrains, ChatGPT, Codex, and Dots, and Vercel pages use the hosted server, not the ten-tool list. On pages with tabs, the Graphify (hosted) tab uses the hosted server and the Graphify Local tab uses the local skill or the ten-tool server. > Read https://docs.graphify.com/llms.txt, then open one page's .md link. Use https://docs.graphify.com/llms-full.txt only when one page is not enough. # Ask questions about your code > Ask Graphify plain-language questions about an indexed repository and get answers that cite real graph nodes, trace real paths, and say so when no path exists. **Ask** is where you question a repository in plain language. Graphify answers from the code knowledge graph of that repository, not from a model's guess: every answer cites the nodes it used and the path it followed. When the graph has no path that answers your question, Ask tells you it found no answer instead of inventing one. > [!NOTE] > > **Use Ask when** you want to know who owns some behaviour, how two parts of the code connect, or where something actually lives, before you open an editor. ## Before you start * A Graphify account at [app.graphify.com](https://app.graphify.com). * At least one repository with the status **Indexed**. See [Index a repository](https://docs.graphify.com/concepts/index-a-repository.md). ## How it works **1. Pick a repository** Open **Ask** in the Console and choose the repository to query. **2. Ask a question** Type a question about ownership, call paths, or where behaviour lives. While it works, Ask shows **Tracing the graph**. **3. Read the grounded answer** The answer is a short explanation plus the graph nodes it cites. **Traced through** lists the path it followed, so you can check every step. **4. Go deeper** Select **Open the graph** to see the cited nodes in [Graph explorer](https://docs.graphify.com/platform/graphs.md). ## Two modes **Ask** Questions and grounded answers. Good starters: * "Where is the session token validated?" * "What calls `create_invoice`?" * "How does the upload worker reach the storage client?" **Plan a change** Select **Plan a change**, then describe what should work differently. For example: *let users retry a failed upload without selecting the file again.* If you know where to start, add a **File or function**. Graphify finds the relevant code and suggests a plan with source links. It won't edit your code. ## Link straight to a question Ask reads the URL, so you can share a question or open a mode directly: | URL | Opens | | - | - | | `//ask?q=where%20is%20auth%20handled` | Ask, with the question already submitted | | `//ask?mode=change` | Ask, with **Plan a change** open | ## When Ask has no answer **No answer found for this question** means the graph has no path that supports an answer. This is deliberate: a near-miss is reported as no answer rather than a confident guess. To get an answer: * Name a real symbol, file, or module. * Ask about one relationship at a time. * Check the repository finished indexing. If Ask says it **isn't connected to your code yet**, the repository has no graph. ## An example answer The Console's demo preview uses a sample graph to show what an answer looks like. Asked "where is retry handled?", it answers: > Retry is handled in the workers module. retry\_with\_backoff in workers/dispatch.py is the shared helper: dispatch\_job calls it directly, an extracted relationship, and billing's retry\_charge (billing/invoices.py) appears to reach it as well, though that edge is inferred from usage rather than parsed. The answer cites each node with its file and confidence tag: | Node | File | Confidence | | - | - | - | | `retry_with_backoff` | `workers/dispatch.py` | extracted | | `dispatch_job` | `workers/dispatch.py` | extracted | | `retry_charge` | `billing/invoices.py` | extracted | | `requeue_stale` | `workers/queue.py` | inferred | **Traced through** lists each step, such as `dispatch_job` → calls → `retry_with_backoff`. When a step is inferred, the answer says so, for example "treat it as probably right, not proven." The demo data is a sample graph, not your code. ## Ask from anywhere You don't have to open the Ask page. The Ask bar in the Console reads **Deep research your codebase...**. Select it, or press ⌘+I on macOS or Ctrl+I on Windows and Linux, to ask without leaving the page you're on. When the box is empty, Ask may show up to four questions under **Suggested from your repository**. They're drawn from that repository. Select one to ask it. ## Limits * Each question goes to one repository. To compare repositories, ask each one, or use a [combined graph](https://docs.graphify.com/platform/graphs.md). * Your workspace has a per-minute limit on Ask requests. If you hit it, wait a minute and ask again. * Ask needs an active plan. New accounts get a 14-day Pro trial, then move to Free (3 repositories, no card required). ## Verify and troubleshoot | Symptom | Fix | | - | - | | No repositories to pick | Connect and index a repository from **Repositories**. | | Every question has no answer | Indexing may still be running. Wait for **Indexed**. | | Answer cites the wrong module | Open the cited node in the graph and refine the question with the correct name. | | "A question is required." | The box was empty. Type a question. | | "This organization's subscription is inactive." | Your workspace plan isn't active. Check **Billing**. | > **Does Ask change my code?** > > No. Both modes only read the graph. **Plan a change** produces a plan with links, not edits. > **Can my coding agent ask the same questions?** > > Yes. Connect it to the [hosted MCP](https://docs.graphify.com/platform/hosted-mcp.md) and it queries the same graph. > **Why does Ask answer each question on its own?** > > Ask doesn't carry hidden assumptions between questions. Name the symbol or module again in a follow-up so the graph search starts from the right place. > **Can Ask be wrong?** > > Yes. Inferred steps are labelled, and every claim links to the code. Open the cited node and check it before you act on it. ## What's next > **[Graph explorer](https://docs.graphify.com/platform/graphs.md)** > > See the nodes behind an answer. > **[Wiki](https://docs.graphify.com/platform/wiki.md)** > > Read the repository as documentation. > **[Connect your agent](https://docs.graphify.com/platform/connections.md)** > > Add the hosted MCP at `api.graphify.com/mcp`. Sign in with OAuth, no API key. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.