A new Overview, with code findings
Overview is now a compact home page for your workspace. It puts what needs you first and keeps everything else one click away.- Needs attention collects review bugs, incomplete reviews and indexing failures. Mark items as read, and Undo if you change your mind.
- Code findings lists dead code and duplicate code across your repositories, grouped by type. View all opens the full list, split into repository scans and PR reviews. Open a finding to see its symbol, file and lines, then use Copy task for my agent to hand it off (you can preview or edit the task first), or Hide or give feedback if it’s intentional or wrong.
- Continue work takes you back to the reviews and findings you were looking at, and Recent activity shows what changed lately.
- Latest pull request shows the review and formal verification result for your most recent PR side by side.
A new Reviews workspace
Reviews now opens as an inbox of your pull requests, showing the latest review for each one. Search by title or PR number, filter by repository or to the reviews that need attention, and page through ten at a time. Status chips like Action needed show which reviews need you.Open a pull request to review it in one place:- Review starts with the review summary in plain language, then Files with findings, with a count next to each file and a box to find a file or finding. Step through issues with Next finding, and tick Viewed on each file to keep your place. When the review captured a file’s changes, you can read them as a Unified or Split diff. Otherwise, Open file at reviewed commit takes you to the code.
- Evidence stays beside the code. It shows what supports the finding, whether it’s grounded or advisory, its location and callers, and the exact commit that was reviewed. From there, Explain this finding asks Graphify about it.
- Activity shows the review’s history and other reviews of the same PR, including runs superseded by a newer push.
Verification results in plain language, and the memories behind an answer
Formal Verification now explains each run in words you can act on. Runs are grouped by pull request, and each one leads with a summary like “Behavior changed in 2 of 5 functions” or “Proven same: 3 of 3 functions (within checked range)”.A How to read results legend explains the five outcomes: Behavior changed, Proven same, No change found, Not checked and Couldn’t run. Re-run check, the commit and PR links, and paging all work as before.Ask now shows its sources from memory too. Under a grounded answer, open Memories given to this answer to see which memories Graphify used and why each was recalled. Mark one Useful, Wrong or Stale to improve what gets recalled next time.Read about formal verificationConnect your agent in three steps
Your agent is where Graphify pays off, so connecting it is now the shortest path in the console.Connectors brings integrations and MCP setup into one page, with MCP open by default. Setup has three steps shown at the top of the card: choose your agent, connect it, and try a query.- Official plugins. ChatGPT, Codex, VS Code, JetBrains, Gemini CLI and OpenClaw get install buttons with short sign-in and first-prompt instructions.
- A real Connected state. Step 3 confirms connection when Graphify sees your agent make a tool call, so you are not left guessing. You can still confirm by hand if that check is unavailable.
- Connect while you wait. You can set up your agent while your first repository is still indexing, and the graph page shows a Connect your agent card until you do.
- Clearer Claude Code setup. The steps now follow the order you run them: add the server, authenticate, then ask.
A readable wiki for every repository
Open Wiki to read documentation generated from your repository’s code graph. It explains your code in plain language: what each area does, its key components, and the decisions and caveats behind them.- A reader built for long pages. Articles sit in a clean reading column with an On this page outline that follows you as you scroll.
- Sources you can check. Each article links the source files it was written from, and a How we know panel shows where its claims came from.
- Search or ask. Search finds words inside articles. When you need an explanation that spans the code, use Ask the wiki instead to get an answer grounded in your graph.
Developer Memory, with Simple and Advanced views
Graphify remembers what happens in your repository: reviews, verifications, merged pull requests and what your agent learns while it works. Memory now runs for every repository you authorize, with no setup.The Memory page offers two views of the same records. Switch with Simple / Advanced in the page header. Your choice is kept per workspace.- Simple is the default. Ask or search your memories in a chat-style panel, keep or discard suggested memories in one click, and read long notes in a side drawer.
- Advanced is for developers. It has a memories table with an entity sidebar, a review queue grouped by reason, and an inline recall inspector that shows what your agent would retrieve.
Ask Graphify in Slack
You can now connect Slack from the Slack tile on the console’s integrations page. Graphify answers questions from your code graph, with sources, in direct messages and in the channels you choose.- Direct messages. Pick a default repository, then message Graphify directly to ask about that code.
- Channels. Add the channels Graphify may answer in and pick a repository for each. Then invite
@Graphifyto the channel so it can reply.
Reviews when your PR is ready, and @graphify review
Graphify now reviews a pull request when it is ready, not on every push. That means fewer repeated comments on work in progress.- A PR gets its first review when you open it or reopen it.
- A draft PR gets reviewed when you mark it Ready for review.
- Pushing more commits no longer triggers a new review on its own.
@graphify review on the pull request. Graphify analyzes the full pull request, from where it branched to its latest commit. It updates the review result.Formal verification is unchanged. It still runs on every push, so your behavior checks stay current while you iterate.Read about reviewsA redesigned console
The console has a new look, built around the pages you use most.- A refreshed dashboard. Overview, Repositories, Members and Billing share one cleaner layout.
- Cancel a running index. You can cancel an index that is still running from the graph page.
- Better builds. Each successful build shows how its graph changed against the previous one, for example
+250nodes. Retry appears only on the latest build. - A clearer sign-in. The login page is redesigned, and Pro workspaces show a Pro badge.
- A friendlier first run. Onboarding has a new layout and a walkthrough of the main pages.
Teams, and switching between workspaces
The Teams plan lets your whole team share one Graphify workspace, with a seat for each developer. Start it at signup: choose how many seats you need and check out with Stripe.When you upgrade, you can turn your current workspace into a team workspace and keep its repositories, graphs, memory and address. Or you can create a new team workspace. Invite teammates from Members in the user menu at the bottom of the sidebar. Owners and admins of a team workspace see there how many seats are in use.If you belong to more than one workspace, switch between them from the top of the sidebar. Team workspaces show a Teams badge.See pricingConnect 30 agents to Graphify
You can now connect Graphify to 30 clients from the console. The connect page groups them into Coding agents and Cloud connectors.New coding agents include Gemini CLI, Amp, Kiro, OpenCode, Warp, Conductor, Amazon Q Developer, Factory Droid, JetBrains Junie, Kilo Code, Crush, OpenHands, LM Studio and Jan.New cloud connectors include ChatGPT, Perplexity and Microsoft 365 Copilot.Every client uses the same setup: copy its config, then sign in the first time it connects. No API key is pasted into a config file.See all integrationsContributors
A Contributors page in the console sidebar shows who has shaped each repository. People are ranked by reach, which is how much of the code graph they authored. Each row shows their commit count and how many of those commits were AI-assisted.The Tamper risk tab flags supply-chain risks: critical code with a single owner, new contributors working in high-impact areas, unsigned commits in sensitive paths, and unverified AI-assisted changes near critical code. Each flag comes with the evidence behind it and a suggested fix.Anyone who can read a repository can open its Contributors page, including members.Read about contributorsLearn: teach Graphify which review findings matter
Reviews get quieter as your team uses them. Reply to a Graphify review on the pull request and it learns from what you say:@graphify wrong <finding>dismisses a finding that does not apply.@graphify good <finding>confirms one that was useful.@graphify suppress <rule>mutes a rule, optionally for one path.
Pull request reviews and formal verification
Graphify now checks your pull requests in two complementary ways, and both are available to every workspace.Reviews. Graphify reviews a pull request using your code graph, so it looks beyond the diff to the callers and dependencies a change can reach. Findings appear on the pull request and in the Reviews page of the console, next to the affected code.Formal Verification. For supported functions, Graphify compares the changed version with the previous one. It either proves they behave the same within the checked range or finds a concrete input that gives a different result. Open a run to see each function’s verdict, and re-run it when you need a fresh result.A review points you to something worth a look. Verification tells you whether behavior actually changed.Read about reviewsShare a GitHub org with your team
Before, if a teammate had already installed the Graphify GitHub App on your organization, you hit a dead end when you tried to connect.Now Graphify tells you which workspace owns the installation and lets you request access. Graphify checks that you are a member of the organization on GitHub, and the workspace owner approves you in. You then work in the same workspace, on the same repositories, as the rest of your team.Read about repositoriesFree and Pro plans
Graphify now has two plans.- Free lets you sign in, connect a repository and use the console.
- Pro raises the limits for larger repositories and teams. Start Pro at signup and check out for a single seat.
Connect any MCP client, and sign in with GitLab
Graphify now works with more of the tools you already use.MCP for every client. Your agent connects to Graphify’s hosted MCP server and signs in through your browser. There is no key to copy. The connect page has one-click setup for popular agents.GitLab. You can sign in to Graphify with GitLab and connect GitLab repositories, alongside GitHub. Formal verification is GitHub-only for now.Read the MCP overviewAsk questions about your code
Ask is live in the console. Type a question about your repository in plain English and get an answer grounded in your code graph. Answers point back to the parts of the code they came from.Use it to find where something is implemented, trace how a request moves through your services, or check what a change might touch before you make it.Learn how to query your graphCombine repositories into one graph
Code rarely lives in one repository. You can now combine several of your repositories into a single cross-repository graph and follow calls and dependencies across service boundaries.Choose Combine graphs to pick the repositories, and Graphify builds the merged graph for you. Your combined groups appear on Overview, so you can come back to them.Explore your graphsGraphify is live
You can now use Graphify at app.graphify.com.- Sign in.
- Create your workspace.
- Connect GitHub and choose the repositories Graphify can read.
- Graphify indexes each repository into a code graph.
- Explore the graph in the console.