> For the complete documentation index, see [llms.txt](https://docs.nuclearplayer.com/nuclear/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuclearplayer.com/nuclear/plugins.md).

# Plugins

- [Getting started with plugins](https://docs.nuclearplayer.com/nuclear/plugins/getting-started.md): Create and load your first Nuclear plugin and verify the SDK works end-to-end.
- [Plugin system](https://docs.nuclearplayer.com/nuclear/plugins/plugin-system.md): How do plugins work in Nuclear?
- [Plugin store](https://docs.nuclearplayer.com/nuclear/plugins/plugin-store.md): Browse, install, and manage plugins from the built-in plugin store.
- [Publishing](https://docs.nuclearplayer.com/nuclear/plugins/publishing.md): Package, release, and submit your plugin to the Nuclear plugin store.
- [Settings](https://docs.nuclearplayer.com/nuclear/plugins/settings.md): How plugins define, read, and update persisted settings in Nuclear.
- [Queue](https://docs.nuclearplayer.com/nuclear/plugins/queue.md): Control playback order, manipulate the queue, and react to track changes in Nuclear.
- [Favorites](https://docs.nuclearplayer.com/nuclear/plugins/favorites.md): Save and manage user's favorite tracks, albums, and artists.
- [Playlists](https://docs.nuclearplayer.com/nuclear/plugins/playlists.md): Create, modify, and import playlists, or register a provider that fetches playlists from URLs.
- [Playback](https://docs.nuclearplayer.com/nuclear/plugins/playback.md): Control audio transport, read playback state, and react to playback changes.
- [Events](https://docs.nuclearplayer.com/nuclear/plugins/events.md): Subscribe to player lifecycle events and react to playback milestones.
- [Shell](https://docs.nuclearplayer.com/nuclear/plugins/shell.md): Open URLs in the user's system browser from a plugin.
- [Streaming](https://docs.nuclearplayer.com/nuclear/plugins/streaming.md): Resolve audio streams for tracks in Nuclear's queue.
- [Metadata](https://docs.nuclearplayer.com/nuclear/plugins/metadata.md): Build metadata providers that power search, artist pages, and album views in Nuclear.
- [Dashboard](https://docs.nuclearplayer.com/nuclear/plugins/dashboard.md): Supply dashboard content: top tracks, trending artists, curated playlists, and more.
- [Discovery](https://docs.nuclearplayer.com/nuclear/plugins/discovery.md): Recommend tracks based on the user's listening context
- [Logger](https://docs.nuclearplayer.com/nuclear/plugins/logger.md): Structured logging for plugins, routed to Nuclear's log file and developer console.
- [HTTP](https://docs.nuclearplayer.com/nuclear/plugins/http.md): Make CORS-free HTTP requests from plugins using a standard fetch API.
- [yt-dlp](https://docs.nuclearplayer.com/nuclear/plugins/ytdlp.md): Search YouTube and resolve audio stream URLs via yt-dlp.
- [Providers](https://docs.nuclearplayer.com/nuclear/plugins/providers.md): Register providers that supply metadata, audio streams, dashboard content, and more to Nuclear.


---

# 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.nuclearplayer.com/nuclear/plugins.md?ask=<question>&goal=<endgoal>
```

`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.
