> For the complete documentation index, see [llms.txt](https://docs.mobiusflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobiusflow.com/help/mobiusflow-v3/mobiusflow-toolbox-v3/getting-started-with-toolbox.md).
# Getting Started with Toolbox
## Supported Browsers
MobiusFlow Toolbox supports the latest versions of most modern web browsers. We recommend the following:
* Google Chrome
* Firefox
* Safari
* Edge
{% hint style="info" %}
MobiusFlow Toolbox requires Javascript to be enabled on your browser
{% endhint %}
## Logging In
Open your web browser and navigate to your MobiusFlow Toolbox instance. This is typically a fully qualified domain name followed by `/toolbox`
{% hint style="info" %}
The exact URL will depend our your installation, but for instances hosted in the cloud by MobiusFlow the URL will have been provided or you will have chosen it when creating a hosted instance in MobiusFlow Manager
{% endhint %}
The first time you login you must use the initial administrator credentials supplied to you. You can change the default admin password and create new users once you are logged in.
{% hint style="warning" %}
Make sure to change your default admin user password or create a new account and delete the default admin account as soon as possible!
{% endhint %}
---
# 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.mobiusflow.com/help/mobiusflow-v3/mobiusflow-toolbox-v3/getting-started-with-toolbox.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.
