Skip to main content
After you install and enable entire-graph, ask your coding agent questions about the repository in your own words. You do not need to run entire-graph commands yourself or mention entire-graph in every prompt.

​
What You Can Ask

Your agent chooses the entire-graph command that matches your question.

​
What Happens After You Ask

For a task that requires finding code, your agent starts with a entire-graph search to narrow its investigation. It then reads the source around the most relevant results and uses follow-up entire-graph queries when it needs to trace relationships or assess impact. entire-graph returns evidence for your agent to check, not a final conclusion. Your agent should verify the results against the source and run a focused test before completing a change. Interactive entire-graph queries read the working tree by default, so they include uncommitted edits.

​
Example

In the gorilla/mux repository, you could ask:

​
Example result

Where route matching happens
  • Router.Match (mux.go:151-182) checks each registered route, builds the middleware chain, and handles not-found and method-not-allowed results.
  • Route.Match (route.go:47-114) evaluates the matchers for an individual route and collects route variables.
  • routeRegexp.Match (regexp.go:189-209) checks host, path, and query patterns.
What calls it
  • Router.ServeHTTP calls Router.Match for incoming requests (mux.go:203).
  • Router.Match calls Route.Match for each registered route (mux.go:153).
  • The CORS middleware calls Route.Match when collecting allowed methods (middleware.go:79).
What could be affected
  • Handler selection and middleware execution
  • 404 and 405 responses
  • Route variables used by handlers
  • The Access-Control-Allow-Methods header produced by the CORS middleware
entire-graph helps your agent identify where to investigate, but the agent should still inspect the cited source before drawing a conclusion.

​
When entire-graph Is Not Needed

If a task already identifies the exact file and the file is small, your agent can read it directly. entire-graph is most useful when your agent needs to find where to begin or understand how code connects.

​
Run entire-graph Directly

You can also run entire-graph commands yourself for manual inspection, debugging, or automation. See the entire-graph CLI reference for commands and options.

​
Continue With

Install and Enable entire-graph

Install entire-graph and add its instructions to a repository.

How entire-graph Works

Learn what entire-graph analyzes and where its results have limits.

entire-graph CLI Reference

Review entire-graph commands and options.

entire-graph Troubleshooting

Fix installation, adoption, cache, and coverage problems.