> 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-actions/dscloaddeps.md).
# DSCLoadDeps
## Description
Open a picker dialog that loads the selected images **plus** their dependencies. The dialog lets you cap the recursion depth and individually include or exclude specific dependencies.
Available from the DSC Index context menu, under **Load**.
The "Load > Selection with dependencies..." entry in the DSC Index context menu
### The dependencies picker dialog
The dialog is split into two lists:
* **Source images** (top) — the images selected from the [DSC Index](/ida-actions/opendscindex.md) when the action was triggered. They feed the dependency computation; on their own they do not drive what gets loaded.
* **Full list of images to load** (bottom) — the source images plus their dependencies, computed at the depth set by the **Dependency depth** spin box. Each row shows the image's address (where it will be loaded in the database), its size, and its current state (`Loaded` if it is already in the database).
**What ultimately gets loaded is the set of checked entries in this bottom list.** Use the top list to seed; tweak the bottom list — depth, individual checkboxes — to fine-tune what lands in the database.
The same dialog is used by [From external Mach-O...](/ida-actions/dscloaddepsexternal.md), where the source images come from the load commands of an off-cache Mach-O instead of from the DSC Index selection.
The dependencies picker dialog
See [DSC Workflow](/core/disassembler/concepts/dsc-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-actions/dscloaddeps.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.
