> For the complete documentation index, see [llms.txt](https://docs.volven.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.volven.io/changelog/v0.49.0.md). # v0.49.0 26th January 2024 ## What's new * \[Balances Chart] Add possibility to drag one wallet on another * \[Balances Chart] Add possibility to convert to any by drag * \[TMM] Add Stop Loss Mode parameter and remove Position Netting and Threshold parameters from TMM * \[Strategies] Update orders trolley indicator as in the design * Volven Terminal (macOS) unnecessarily asks for accessibility permission * \[Ticker] The volvenName is not used for product names * \[Strategies] Filtering the strategy list by status does not work * \[Balances Chart] Dragged wallet item is not auto-selected * \[Balances Chart] Not able to drag item near the edge * \[Balances Chart] Conversion dialog position should be centred and remembered * \[Orders] Unable to create spot order * \[Orders Chart] Small orders are not visible --- # 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.volven.io/changelog/v0.49.0.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.