> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/workspaces-and-drives/drive-status-menu.md). # Drive Status Menu The drive status menu pops up automatically when you initiate an upload from a local drive into the app, and can be brought up manually by clicking the tray in the bottom left corner of the app. The drive you want to view the status for can be selected at the top of this menu. Going left to right: ## **Uploading Status** This panel shows you the status of any uploads you have initiated through the web app. This includes upload speed, time left, and the ability to cancel uploads. ## **Downloading Status** This panel shows you the status of any downloads you have initiated through the web app. This includes download speed, time left, and the ability to cancel downloads. In the desktop app, you can also pause and resume downloads. ## **Indexing Status** This panel shows you the status of the jobs that are run on your uploaded assets: **Basic Jobs:** * Sync with File System * Metadata * Previews * Proxies **AI Jobs:** * Core Job * Audio Job * Automated Custom Metadata **Additional Jobs** * Color Palette * Facial Recognition * Transcription ## **Mount Status** This panel is only available in the desktop app. It shows you the status of any uploads you have initiated through the ShadeFS mount, and status for syncing any changes from other editors. These are files you uploading through the mount in your file explorer. This includes upload speed, and time left. --- # 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://academy.shade.inc/workspaces-and-drives/drive-status-menu.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.