> ## 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. # Insights > Review code findings across your repositories and pull requests in Graphify, with evidence, priority, and a team decision on each one. **Insights** collects code findings in one place: findings from pull request reviews and findings from repository-wide analysis. Each finding has its evidence, a priority, and a status, so your team can decide what to fix, what's intentional, and what's wrong. > [!NOTE] > > **Use Insights when** you want one list of what needs attention across repositories, instead of reading each pull request. ## Before you start * A Graphify account at [app.graphify.com](https://app.graphify.com). * An indexed repository. Pull request findings need [reviews](https://docs.graphify.com/platform/reviews.md) on that repository. ## Find what matters **1. Open Insights** Choose a **Repository**, or **All repositories**. **2. Filter** Switch between **PR findings** and **Repository findings**. Filter by **Priority**, **Review category**, and **Finding status**, or **Search findings by title or file path**. **3. Sort** **Highest priority (PRs)** puts the most urgent first. `P0 · Critical` is the top priority. ## Read a finding Open a finding to see: * **Evidence**: the code and reasoning behind it. * Its status, such as **Supported by code**, **Confirmed by test**, or **Not yet verified**. * **Observed history**: earlier analysis of the same finding. * **Show in graph**: the code in [Graph explorer](https://docs.graphify.com/platform/graphs.md). When some checks didn't finish, the finding says **Some checks incomplete**. ## Act on a finding **Hand it to an agent** **Copy task for my agent** copies a task your coding agent can work from. Use **Preview or edit the task** first to adjust it. **Ask about it** **Ask about this finding** opens a conversation grounded in the same graph. **Decide as a team** Set a **Team decision** (**Open**, **Acknowledged**, **Fix proposed** or **Dismissed**), write a **Reason**, and select **Save team decision**. **Hide it** **Hide or give feedback** hides the finding for you, with a reason and optional feedback. Turn on **Include findings I hid** to see them again. ## Filters and what they mean | Filter | Options | | - | - | | Show | **Current findings**, **Earlier analysis**, **Hidden by me** | | Sort | **Newest first**, **Oldest first**, **Highest priority (PRs)** | | Category | **All review findings**, **Bugs**, **Improvements** | | Evidence | **Any evidence**, **Not yet verified**, **Supported by code**, **Confirmed by test** | | Priority | **Any priority**, **P0 · Critical**, **P1 · High**, **P2 · Medium**, **P3 · Low** | Searches match a finding's title or file path, up to 200 characters. Use **Clear filters** or **Reset filters** to start over. Findings load a page at a time. Select **More repository findings** or **Next PR findings** to load the next page. The evidence levels go from weakest to strongest. **Not yet verified** is a claim nobody has checked yet. **Supported by code** means the code backs it up. **Confirmed by test** means a test reproduced it. ## Team decisions and hiding These do different things: | | Team decision | Hide this finding | | - | - | - | | Who sees it | Everyone in the workspace | Only you (**Personal visibility**) | | Choices | **Open**, **Acknowledged**, **Fix proposed**, **Dismissed** | **Not useful**, **Intentional behavior**, **Finding appears incorrect** | | Reason | Required, up to 1,000 characters | Choose one | | Effect on evidence | None. "A team decision does not verify a fix or change the recorded evidence." | None | After you save, the Console shows **Team decision saved. Verification is unchanged.** After you hide a finding, it shows **Hidden for you. You can undo this below.** ## Verify and troubleshoot | Message | What to do | | - | - | | **Couldn't refresh. Showing saved results.** | The latest analysis is unavailable. Saved findings stay. Try again later. | | **Code findings are not available for this workspace.** | Insights isn't turned on for this workspace. | | No PR findings | The repository has no reviewed pull requests yet. | | **Could not save the team decision. Refresh and retry.** | Reload the page and save again. | | **This report is unavailable. It may no longer be accessible to your workspace.** | The repository was removed or you lost access to it. | | **PR findings are not available on this deployment yet.** | Use **Repository findings** instead. | > **Do findings block merges?** > > No. Findings are advisory. > **Does hiding a finding hide it for the team?** > > Hiding is personal. A team decision is shared. > **Does Dismissed mean the finding was wrong?** > > No. It records the team's decision and reason. The evidence level stays as it was. ## What's next > **[Pull request reviews](https://docs.graphify.com/platform/reviews.md)** > > Where PR findings come from. > **[Read a result](https://docs.graphify.com/platform/read-a-result.md)** > > How to read a review result. > **[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.