> For the complete documentation index, see [llms.txt](https://docs.amee.thiennguyen.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amee.thiennguyen.dev/features/mini-player-window.md). # The Mini Player Window The floating mini player stays on top of every other window, with no title bar — just a compact, transparent pill. ## Moving it Drag the pill by its content (its title/artwork, or wherever the active skin marks as a drag handle) to move it anywhere on screen. Amee remembers where you last dragged it to and reopens there next launch. **Snap presets** (Dashboard → General) place the window in one of five positions — top-left, top-right, bottom-left, bottom-right, or center — relative to whichever screen currently holds it. **Reset** snaps back to the built-in default position. ## Resizing Some skins let you drag-resize the mini player within bounds that skin defines; others are a fixed size. Your resized size is remembered per skin, across restarts and across switching to another skin and back. ## Popovers and controls that pop out Some skins can pop open extra controls — a volume slider, an expanding panel — that temporarily extend beyond the mini player's normal bounds, growing whichever direction has room on your screen and then collapsing back automatically. ## Hover controls that keep working in the background Some skins have hover-driven controls (like a volume flyout) that keep responding to your cursor even while you're working in another app — you don't need to click into Amee first for these to react. ## Click-through If a skin leaves blank space around its compact content, clicks in that empty space pass straight through to whatever's behind the floating window, rather than the window blocking them. ## Showing and hiding The mini player can be hidden without quitting Amee — via the auto-hide feature (see [Now Playing](/features/now-playing.md#auto-hide-when-idle)), or programmatically from a skin using `amee.hide()`. Bring it back from the tray menu ("Show Player") or by calling `amee.activateWindow()`. Skins can react to these transitions: `amee.onShow(cb)` fires when the window becomes visible again (e.g. to replay an entrance animation), and `amee.onHide(cb)` fires right before the window hides (e.g. to reset the UI to a clean state so a later reveal doesn't flash stale content). See the [SDK reference](/customization/sdk-reference.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.amee.thiennguyen.dev/features/mini-player-window.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.