> 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/openkcindex.md). # OpenKCIndex ## Description Open the **KC Index** subview, which lists every region of the currently-loaded Apple kernelcache, grouped by the KEXT that owns it. From there you can load what you want and reach the KC actions (`Locate`). Available under **View > Open subviews** when the current database is a kernelcache.

KEXTs are named by their bundle identifier, and the tree nests on the dots, so `com.apple.iokit.IONetworkingFamily` sits under `com` -> `apple` -> `iokit`. The letter beside each one says which collection it came from: **B** for boot, **S** for system, **A** for auxiliary. On a cache that spans more than one, the context menu also offers **Show contents for**, which hides and shows each collection. Double-clicking a KEXT maps it on demand and jumps there. See [Kernelcache Workflow](/ida-9.5/core/disassembler/concepts/kc-workflow.md). --- # 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/openkcindex.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.