> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/ida-actions/jumpanywhere.md).
# JumpAnywhere
## Description
Jump to any location in the database. Jump Anywhere simplifies navigating and quick jumps to any location within the IDB. The Jump Anywhere is designed as a fast, unified entry point to navigate "everywhere" - the dialog accept names, expressions, segment-relative addresses, and script identifiers.
{% hint style="success" %}
See the [full reference](/ida-9.5/core/user-interface/concepts/jump-anywhere.md) for acceptable inputs in the Jump Anywhere dialog.
{% endhint %}
**Jump Anywhere key functionalities**:
* Fast, case-insensitive and asynchronous search across functions, local types, names, and segments, with results ranked by type and similarity score.
* Supports searches for both mangled and demangled versions of functions and names.
* Allows searching by address or simple expression, as in "Jump to address...".
* Inline preview of matching results, showing the target location.
* The Jump Anywhere dialog supports jumping to a field offset in the Local Types view, acting as replacement for the “Jump to file offset” dialog.
## How Jump Anywhere Works
The Jump Anywhere performs a case-insensitive search across functions, local types, names, and segments. Matching results are presented in a list along with a preview, and can be navigated using the keyboard cursor keys.
If the input can be interpreted as an address expression, an entry for the corresponding destination is automatically added to the top of the results list.
## How to open Jump Anywhere
* Press G to open the Jump Anywhere dialog (default).
* Press G ↓ ↵ to jump again to the last location visited through Jump Anywhere.
## Settings and behavior
If you prefer the legacy G shortcut behavior bound with [Jump to address](/ida-9.5/ida-actions/jumpask.md), you can enable it under **Options → Feature Flags**.
## Adjusting Additional Parameters in idagui.cfg
The behavior of the Jump Anywhere dialog can be customized by editing `idagui.cfg`.
```
//-------------------------------------------------------------------------
// Jump anywhere parameters
//-------------------------------------------------------------------------
#ifdef __QT__
JUMP_ANYWHERE_MAX_HISTORY = 25 // maximum number of history entries in the jump anywhere dialog
JUMP_ANYWHERE_MAX_RESULTS = 10000 // maximum number of search results (0 = no limit)
#endif
```
The Jump Anywhere works even when the indexer is disabled (`ENABLE_INDEXER = NO` in `ida.cfg`). This can be useful when running IDA in headless mode, as it avoids the overhead of building and maintaining the index.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.hex-rays.com/ida-9.5/ida-actions/jumpanywhere.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.