Ask a question about your code

Ask your agent a question in plain English, and Graphify answers from the graph of your indexed repository. The answer cites definitions and files, so your agent reads the code that matters instead of searching the whole repository. Use this when you know what you want to understand but not where it lives. If you already know the symbol name, ask your agent to look it up with graphify_find instead.

Before you start

An account at app.graphify.com. The Free plan covers 3 indexed repositories, and you don’t need a card.
A repository with the status Indexed. See Repositories and builds.
Your agent connected to the hosted MCP server at https://api.graphify.com/mcp. See Code with an agent.

Ask the question

Use Graphify to answer: how does a request get authenticated in Graphify-Labs/graphify?
Show the definitions and file paths you used.

graphify query "how does a request get authenticated" --budget 1500

Name the area you care about, such as a feature, a subsystem, or a file. A specific question returns a smaller, more useful set of results than a broad one. If you work in more than one workspace, ask your agent to list repositories first. The list_repositories tool shows the repositories this connection can query and their index status.

What your agent calls

Your agent picks the tools. These are the hosted tools it uses for a question in plain English:

Tool	What it returns
`query_graph`	The definitions that match a plain-English question.
`graphify_rank_files`	The source files most relevant to the question.
`graphify_find_seeds`	The top starting nodes for the question, without their definition bodies.
`graphify_expand`	Full definition bodies for node handles returned by another tool.

A common pattern is to find seeds or rank files first, then expand only the nodes the agent needs. The full list is in Tools. The local CLI takes these options:

Option	Default	Meaning
`--dfs`	Off	Follow one path deep instead of searching broadly.
`--context`	No filter	Keep only one kind of edge, such as `call`. Repeat it for more kinds.
`--budget`	`2000`	Approximate output token budget.
`--graph`	`graphify-out/graph.json`	The graph file to query.

Read the result

The result is graph evidence, not a checked answer. Each relationship carries a confidence tag:

EXTRACTED: written in the source.
INFERRED: worked out by Graphify, with or without a model.
AMBIGUOUS: flagged as uncertain by the model pass. Check the source.

Open the cited source before you rely on an answer. Edges and provenance explains each tag.

If something fails

What you see	What to do
The agent does not use Graphify	Name it in the prompt: “Use Graphify to answer”. Check that the connection is listed in your agent.
No repositories, or an empty answer	The repository is not indexed yet, or it is in another workspace. Check its status in Repositories and builds.
The answer is too broad	Name a function, class, file, or subsystem in the question.

Next steps

Try it in Graphify Cloud

We build and host the graph for you. Free for up to 3 repositories, no card required.

Repository graphs

See the nodes behind an answer in the console.

graphify query

Every option for the local command.

Get started

Core concepts

Review code

Explore

Workspace

Reference

Ask a question about your code

Before you start

Ask the question

What your agent calls

Read the result

If something fails

Next steps

Try it in Graphify Cloud

Repository graphs

graphify query

​Before you start

​Ask the question

​What your agent calls

​Read the result

​If something fails

​Next steps

Try it in Graphify Cloud

Repository graphs

graphify query

Before you start

Ask the question

What your agent calls

Read the result

If something fails

Next steps