> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myaione.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Paths
> Tell MyaiOne for Development where to find the command-line tools it relies on. Leave a path empty to auto-detect it, or set it explicitly when a tool lives somewhere non-standard.
The **Paths** settings tell MyaiOne for Development where the executables and frameworks it uses live on your system. Most can be **left empty for auto-detection** — set a path explicitly only when a tool is installed somewhere non-standard or isn't being detected automatically.
## Executable paths
Each field points to a command-line tool. Leave it blank to let MyaiOne for Development find the tool itself, or enter a full path to override. When a tool hasn't been found, the field shows **Not detected**.
* **Python Path** — the Python executable.
* **Git Path** — the Git executable.
* **GitHub CLI Path** — the GitHub CLI (`gh`) executable.
* **GitLab CLI Path** — the GitLab CLI (`glab`) executable.
* **Claude CLI Path** — the Claude CLI executable.
A **Not detected** label just means the tool wasn't found on the default path. If you have it installed, point the field at its location; if you don't use that tool, you can leave it as-is.
## Framework path
* **DevStation Path** — the relative path to the `devstation` directory within your projects.
Start by leaving everything on auto-detection. Only fill in a path if you see **Not detected** for a tool you know is installed, or if MyaiOne for Development is picking up the wrong version.
Remember to click **Save Settings** to apply your changes. **Cancel** discards them.