Skip to main content
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.
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

​
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.

​
Two modes

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?”
Ask reads the URL, so you can share a question or open a mode directly:

​
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: 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.
  • 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

No. Both modes only read the graph. Plan a change produces a plan with links, not edits.
Yes. Connect it to the hosted MCP and it queries the same graph.
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.
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

See the nodes behind an answer.

Wiki

Read the repository as documentation.

Connect your agent

Add the hosted MCP at api.graphify.com/mcp. Sign in with OAuth, no API key.