> For the complete documentation index, see [llms.txt](https://bc-security.gitbook.io/empire-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bc-security.gitbook.io/empire-wiki/stagers/multi_generate_agent.md).

# multi\_generate\_agent

## Overview

`multi_generate_agent` is an Empire stager that generates a **stageless agent**, combining stage 0, stage 1, and stage 2 into a single file. Unlike traditional staged execution methods, this stager ensures that the agent is fully formed and ready to run immediately upon execution. This method is particularly useful for **debugging**, as it allows operators to analyze a fully assembled agent without concerns about staged delivery issues. It is also beneficial for **pre-staging agents**, making it useful in environments where fetching additional stages is undesirable or impractical. Additionally, it can help **reduce detection risk**, as all necessary code is included in a single artifact, which may be beneficial in environments with restricted outbound network connectivity.

## Compatibility

The `multi_generate_agent` stager is designed specifically for **Python, IronPython, and PowerShell agents**. It does not apply to **C# or Go agents**, as these are already compiled and inherently prestaged.

## How It Works

The `multi_generate_agent` stager generates a self-contained Empire agent file that incorporates all required stages. Upon execution, the agent **performs a full key exchange** with the Empire server but does **not execute the passed code immediately**, allowing operators to trigger execution when needed. This design makes it ideal for debugging or scenarios where an agent needs to be prestaged without requiring additional network requests to retrieve code.

![generate\_agent](/files/j7t8B1BtMJw8AT6dwT9q)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bc-security.gitbook.io/empire-wiki/stagers/multi_generate_agent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.