> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/platform/tutorials/edit-agent.md). # Edit an Agent ## **Overview** This guide explains how to access and edit existing agents in AutoGPT, whether they're your own creations or downloaded from the marketplace. ## **Steps to Edit an Agent** ### **1. Access the Monitor Tab** * Navigate to the Monitor Tab in the AutoGPT builder * You'll see a list of all your agents, including: * Agents you've created * Agents downloaded from the marketplace ### **2. Select the Agent** * Locate the agent you want to edit from the list * Click on the agent name to select it ### **3. Enter Edit Mode** * Look for the pencil icon next to the selected agent * Click the pencil icon to open the editor ### **4. Modify the Agent** * The agent will load in the editor with all its existing components * Make your desired modifications to the agent's configuration ### **5. Save Changes** * After making your modifications, save the updated agent ## **Note** * All agents can be edited, regardless of whether they were created by you or downloaded from the marketplace * Changes are saved to your local instance --- # 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://agpt.co/docs/platform/tutorials/edit-agent.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.