> For the complete documentation index, see [llms.txt](https://docs.mojo.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mojo.trade/user-guide/managing-your-agents.md). # Managing Your Agents Once you have strategies running, here's how to keep an eye on them and step in when you need to. *** ### The "My" tab Your home for everything that's running. * **All active agents** — every strategy you currently have live * **P\&L** — performance per agent and across your whole portfolio * **Total assets** — your overall account value *** ### Inspecting an individual agent Tap any agent to drill in. You'll see: * Its current state (waiting, active, completed, stopped) * Open positions and pending conditions * A full timeline of every signal it has observed and every action it has taken * The original intent you described, and the strategy card you approved **Mojo is not a black box.** If you ever want to know *"why did my agent do that?"* — the answer is one screen away. *** ### Modifying or stopping an agent From the agent detail screen, you can: * **Modify parameters** — change the strategy mid-flight. You'll re-confirm the new card before changes take effect. * **Pause** — temporarily stop the agent from acting. Open positions remain. * **Cancel** — fully stop the agent. All three are available at any time. *** ### Agents and chats Every agent belongs to the chat you created it in. * **It reports back to that chat** — even while you're in a different one, in which case that chat is marked as unread. * **Your chat list shows how many agents are running in each chat.** * **To archive a chat, its agents need to be stopped first.** **Stop all and archive** stops only the agents in that chat. See [Managing Your Chats](/user-guide/managing-your-chats.md) for starting, finding, and archiving chats. *** ### One position, one driver A position has exactly one driver at a time — you, or an agent. The rules are the same on Hyperliquid and Polymarket: * **While an agent manages a position, you can't operate it manually.** To take back manual control, stop that agent first — then the position is yours again. * **Existing positions can be handed to an agent.** Any position not currently managed by another agent can be handed over for the agent to manage — including positions you opened manually. This prevents you and your agent from accidentally fighting over the same position. *** ### Notifications Mojo will push alerts to your phone for: * **Position opened** — when an agent enters a trade * **Position closed** — when a stop, take profit, or exit condition fires * **Risk alerts** — when something needs your attention Alerts arrive in-app, as phone push, or by email. You can adjust notification preferences in Settings. *** ### Known limits We're being upfront about where the product is still rough: * **Long-running strategies may hit edge cases.** Multi-day, complex agents are still under active testing. If something behaves unexpectedly, please report it (see [Feedback and Support](/user-guide/feedback-and-support.md)). * **No fiat on-ramp.** You'll need to fund your Mojo wallet with USDC from an existing wallet or exchange. * **On-chain token coverage varies.** Major tokens are fine. Very small-cap tokens may have liquidity issues. * **Polymarket settlement depends on the oracle.** Market resolution is determined by Polymarket's oracle — Mojo cannot speed this up. * **Mobile-first.** The web version is a companion. The best experience is in the app. * **Text input only.** The agent works from what you type — it can't analyze images or screenshots yet. These are the things we know about. If you find others, we want to hear about them. --- # 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.mojo.trade/user-guide/managing-your-agents.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.