Process Explorer fixed

README.md

@@ -82,6 +82,87 @@ The agent will be cross-compiled for Windows using MinGW in a Docker container.
 
 ---
 
+## 🔨 Customizing Cazalla
+
+If you've forked Cazalla or made local changes and want to use your customized version, you need to configure Mythic to use local builds instead of remote images.
+
+### Making Changes Work
+
+By default, Mythic may use pre-built remote images for faster deployment. However, if you've made local changes to the agent code, translator, or any Python files, you need to configure Mythic to use your local build context.
+
+#### Configure Build Variables
+
+After installing Cazalla, Mythic will add these variables to your `~/Mythic/.env` file:
+
+```bash
+# Use local build context instead of remote image
+CAZALLA_USE_BUILD_CONTEXT="true"
+
+# Use direct mount instead of Docker volume (recommended for development)
+CAZALLA_USE_VOLUME="false"
+
+# Optional: Remote image URL (only used if USE_BUILD_CONTEXT is false)
+CAZALLA_REMOTE_IMAGE="ghcr.io/your-org/cazalla:v1.0.0"
+```
+
+#### Variables Explanation
+
+- **`CAZALLA_USE_BUILD_CONTEXT`**: 
+  - Set to `"true"` to build from your local `Dockerfile` and include your local changes
+  - Set to `"false"` (default) to use the pre-built remote image
+  - **Important**: You must set this to `"true"` if you've modified any files!
+
+- **`CAZALLA_USE_VOLUME`**:
+  - Set to `"false"` (default) to mount the local folder directly into the container
+  - Set to `"true"` to use a Docker volume instead
+  - Direct mount is better for development as changes are immediately visible
+
+- **`CAZALLA_REMOTE_IMAGE`** (optional):
+  - Specifies a pre-built remote image URL
+  - Only used when `CAZALLA_USE_BUILD_CONTEXT="false"`
+
+#### Apply Changes
+
+After modifying these variables, rebuild the container:
+
+```bash
+cd ~/Mythic
+sudo ./mythic-cli build cazalla
+```
+
+#### Verifying Your Changes
+
+1. Make your code changes
+2. Set `CAZALLA_USE_BUILD_CONTEXT="true"` in `~/Mythic/.env`
+3. Run `sudo ./mythic-cli build cazalla`
+4. Check logs: `sudo docker logs cazalla_translator`
+
+If changes still don't appear:
+- Verify the `Dockerfile` copies your modified files (see line 39: `COPY ./ /Mythic/cazalla/`)
+- Check that file paths in the Dockerfile match your directory structure
+- Ensure you're editing files in the correct location (inside `Payload_Type/cazalla/`)
+
+#### Example: Customizing Agent Code
+
+```bash
+# 1. Edit agent C code
+vim Payload_Type/cazalla/cazalla/agent_code/cazalla/comandos.c
+
+# 2. Ensure build context is enabled
+echo 'CAZALLA_USE_BUILD_CONTEXT="true"' >> ~/Mythic/.env
+
+# 3. Rebuild the container
+cd ~/Mythic
+sudo ./mythic-cli build cazalla
+
+# 4. Rebuild a payload from the UI
+# Your changes will now be included in the compiled agent
+```
+
+For more information, see the [Mythic documentation on customizing public agents](https://docs.mythic-c2.net/customizing/customizing-public-agent).
+
+---
+
 ## 🛠️ Supported Commands
 
 ### File System Operations