fix(auth): patch critical Auth.js vulnerabilities

Each visible chart row was hardcoded to a fixed pixel height (110px in
advanced mode, 56px-capped in compact) regardless of the widget's actual
tile size - resizing the tile taller left the extra height unused, and
some visible charts required scrolling to reach.

Divide the available height evenly across rows using CSS Grid's
grid-auto-rows: 1fr (the Stack fills the tile via a definite pixel
height, the SimpleGrid grows into it via flex and divides its rows
evenly) rather than computing a per-chart pixel height in JS. Confirmed
via live inspection of a deployed board that Mantine's h prop is not
safe for this: its rem() converter strips a "px" suffix from any string
before checking whether it's a parseable number, so even a literal pixel
*string* passed through h= gets rescaled by rem() * var(--mantine-scale)
exactly like a raw number would - style.height is the only way to set
an exact, un-rescaled pixel value.

.agents/skills/codebase-context/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: codebase-context
+description: Navigate Homarr's monorepo architecture and reuse shared packages. Use when locating code, choosing a package boundary, understanding runtime services, tRPC, databases, widgets, integrations, cron jobs, Custom Widgets, Workshop, or checking @homarr/common before creating a utility.
+---
+
+# Homarr Codebase Context
+
+Orient from the current checkout before editing. Treat package manifests, exports, and source as authoritative when they differ from this snapshot.
+
+## Workflow
+
+1. Confirm the branch and inspect the nearest `package.json`, existing sibling modules, and package exports.
+2. Search `@homarr/common` before creating a general-purpose helper. Read [references/common.md](references/common.md) for every public entrypoint and export.
+3. Read [references/architecture.md](references/architecture.md) when the task crosses packages, runtimes, routing, data, widgets, integrations, cron jobs, Custom Widgets, or Workshop.
+4. Keep the change in the deepest package that owns the behavior. Reuse public entrypoints rather than deep-importing implementation files.
+5. Re-run targeted searches before documenting counts, consumers, or dependency edges; these change faster than the architectural seams.
+
+## Current toolchain
+
+- Use Node `24.18.0` from `mise.toml` and pnpm `11.15.1` from `package.json`.
+- Use pnpm workspaces with Turborepo. Workspace packages use the `@homarr/` scope and catalog-managed dependencies.
+- Use Next.js App Router, TypeScript, tRPC, Drizzle, Mantine v9, Tabler icons, Jotai, TanStack Query, next-intl, Vitest, and Playwright.
+- Use oxlint and oxfmt. Mantine is the application UI system; Tailwind is limited to the docs app.
+- `pnpm dev` starts only `@homarr/nextjs`. Start a standalone runtime explicitly when the task needs it.
+
+## High-value seams
+
+- Server/RSC tRPC: `@homarr/api/server`
+- Client tRPC hooks: `@homarr/api/client`
+- Main router: `packages/api/src/root.ts`
+- MCP eager router: `packages/api/src/mcp.ts`
+- Database schemas: `packages/db/schema/{sqlite,mysql,postgresql}.ts`
+- Widget registry: `packages/widgets/src/registry.ts`
+- Widget loading manifest: `packages/widgets/src/manifest.ts`
+- Integration definitions: `packages/definitions/src/integration.ts`
+- Integration factory: `packages/integrations/src/base/creator.ts`
+- Cron jobs: `packages/cron-jobs/src/jobs/`
+- App routes: `apps/nextjs/src/app/[locale]/`
+
+When a code change affects users, invoke `documentation-sync`. When exposing tRPC through MCP, invoke `mcp-integration`.

.agents/skills/codebase-context/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Homarr Codebase Context"
+  short_description: "Navigate Homarr architecture and shared APIs"
+  default_prompt: "Use $codebase-context to locate the right Homarr package and reuse existing shared APIs."

.agents/skills/codebase-context/references/architecture.md

@@ -0,0 +1,110 @@
+# Homarr architecture
+
+## Contents
+
+- [Applications and runtimes](#applications-and-runtimes)
+- [Package map](#package-map)
+- [Dependency direction](#dependency-direction)
+- [Core patterns](#core-patterns)
+- [Commands and conventions](#commands-and-conventions)
+
+## Applications and runtimes
+
+| Path             | Role                                                                                     |
+| ---------------- | ---------------------------------------------------------------------------------------- |
+| `apps/nextjs`    | Main Next.js application and HTTP APIs on port 3000                                      |
+| `apps/docs`      | Docusaurus documentation site on port 3003                                               |
+| `apps/tasks`     | Cron-job initialization and scheduling runtime; it does not expose the old port-3002 API |
+| `apps/websocket` | tRPC WebSocket subscriptions on port 3001                                                |
+| `apps/workshop`  | Go/PocketBase Workshop service and provider integration                                  |
+
+`pnpm dev` runs only `@homarr/nextjs`. Use `pnpm --filter @homarr/tasks dev`, `pnpm --filter @homarr/websocket dev`, or `pnpm dev:docs` when a task needs those runtimes.
+
+In production, `apps/nextjs/src/instrumentation-node.ts` starts the tasks and WebSocket runtimes inside the Node process. Nginx listens on port 7575, proxies `/websockets` to port 3001, and sends other traffic to port 3000. Redis can run internally or externally.
+
+## Package map
+
+### Foundation and domain
+
+- `core`: environment validation, database and Redis factories, logging, infrastructure.
+- `definitions`: domain enums, integration definitions, widget kinds, permissions.
+- `common`: shared utilities with environment-specific entrypoints. Search it before adding helpers.
+- `validation`: shared Zod schemas.
+- `server-settings`: typed server-setting keys and access.
+
+### Data, identity, and transport
+
+- `db`: Drizzle schemas, queries, migrations, and three database drivers.
+- `auth`: Auth.js/NextAuth configuration, sessions, providers, and API keys.
+- `api`: tRPC routers, contexts, MCP metadata extraction, OpenAPI, and client/server entrypoints.
+- `redis`: Redis clients, pub/sub channels, and caches.
+- `cron-jobs-core`, `cron-jobs`, `cron-job-status`: scheduling primitives, job implementations, and status transport.
+
+### Backends and external systems
+
+- `integrations`: typed clients for external applications.
+- `request-handler`: shared server request flows.
+- `docker`, `ping`, `image-proxy`, `icons`, `analytics`: bounded infrastructure capabilities.
+- `custom-widgets`: Custom JSX v2 schema, validation, runtime, and security contracts.
+- `workshop`: TypeScript Workshop client, backend contracts, and schemas used by Homarr.
+
+### UI and composed features
+
+- `ui`: shared Mantine components, theme, and hooks. Search here before creating a primitive.
+- `form`, `forms-collection`: Zod-backed form setup and reusable forms.
+- `modals`, `modals-collection`: modal primitives and feature modals.
+- `boards`: board state, edit mode, and cache coordination.
+- `settings`, `spotlight`, `notifications`, `onboarding`: cross-feature UI flows.
+- `widgets`: widget definitions, dynamic component loaders, and shared widget UI.
+- `translation`: next-intl configuration and locale catalogs.
+- `cli`: Node operations CLI. `tools/homarr-dev` is the separate Go developer CLI.
+
+## Dependency direction
+
+Prefer these directions; verify the exact dependency in package manifests before changing a boundary.
+
+1. Put infrastructure in `core` and stable domain names in `definitions`.
+2. Put reusable, dependency-light helpers in `common`; use its public environment-specific entrypoints.
+3. Build persistence in `db`, identity in `auth`, transport in `redis`, and external clients in `integrations`.
+4. Compose server behavior in `api`, `cron-jobs`, and request-handler packages.
+5. Build primitives in `ui`, `form`, and `modals`; compose product surfaces in widgets and collection packages.
+6. Keep app entrypoints in `apps/*` thin. Avoid moving reusable behavior into `apps/nextjs` when a package already owns it.
+
+## Core patterns
+
+### tRPC and MCP
+
+`packages/api/src/root.ts` lazily composes the application router. Server components use `@homarr/api/server`; client components use `@homarr/api/client`. MCP extraction requires the eager router in `packages/api/src/mcp.ts`, so MCP-enabled subrouters must be imported and registered there directly. Use the `mcp-integration` skill for exposure and security rules.
+
+### Databases
+
+Drizzle schemas live in parallel files under `packages/db/schema/`. `DB_DRIVER` selects `better-sqlite3`, `mysql2`, or `node-postgres`; migrations live in matching directories under `packages/db/migrations/`. Apply schema behavior consistently across all supported drivers unless the task is explicitly driver-specific.
+
+### Widgets
+
+`packages/widgets/src/registry.ts` owns the explicit widget-module and component-loader registries. `packages/widgets/src/manifest.ts` caches those loaders and exposes definitions, components, and combined resources. Widget modules use `createWidgetDefinition` and typed option builders. Data commonly comes from tRPC queries or Redis-backed cron results. Use existing shared widget components before creating local variants.
+
+### Integrations
+
+`packages/definitions/src/integration.ts` owns `integrationDefs` and `IntegrationKind`. `packages/integrations/src/base/creator.ts` owns `createIntegrationAsync`; concrete integrations implement the shared base contract. Keep credentials and permission checks on server-owned paths.
+
+### Cron jobs
+
+Jobs live in `packages/cron-jobs/src/jobs/` and use `createCronJob`. `apps/tasks` initializes and starts the job group. Job results and status can flow through Redis and tRPC; the retired port-3002 management-API model is no longer part of the architecture.
+
+### Routing and localization
+
+User routes live below `apps/nextjs/src/app/[locale]/`; the locale segment does not add a URL prefix. Route groups organize home and board surfaces. Administrative routes live under `manage`, Custom Widget configuration has a token route, and Workshop has a management surface.
+
+### Custom Widgets and Workshop
+
+`packages/custom-widgets` owns the Custom JSX v2 contract. `packages/workshop` is the Homarr-side client/contract package; `apps/workshop` is the separate Go/PocketBase service. Use the `homarr-custom-widget` skill for authoring and security constraints.
+
+## Commands and conventions
+
+- Read current scripts from the root or package `package.json`; avoid caching commands that do not exist.
+- Use `pnpm dev` for Next.js, `pnpm dev:docs` for docs, and `pnpm dev:cli -- <args>` for the Go developer CLI.
+- Use `pnpm docker:dev:up` for the Redis development dependency.
+- Use package-filtered typechecks or focused tests for the touched behavior.
+- Use `~/*` only inside the Next.js app. Use public `@homarr/*` entrypoints across package boundaries.
+- Keep Mantine application styles separate from the Tailwind-based docs app.

.agents/skills/codebase-context/references/common.md

@@ -0,0 +1,86 @@
+# `@homarr/common` public API
+
+## Contents
+
+- [Reuse workflow](#reuse-workflow)
+- [Entrypoints](#entrypoints)
+- [Root exports](#root-exports)
+- [Types exports](#types-exports)
+- [Server exports](#server-exports)
+- [Client and environment exports](#client-and-environment-exports)
+
+## Reuse workflow
+
+Before writing a utility, search both the public name and the behavior:
+
+```bash
+rg -n "export (const|function|class|type|interface)|export \*" packages/common
+rg -n "@homarr/common" apps packages
+```
+
+Import only from an exported package entrypoint. Do not deep-import `@homarr/common/src/*`. Check `packages/common/package.json` and the source again when adding or renaming an export; this inventory describes the current repository tree.
+
+## Entrypoints
+
+| Import                  | Source                       | Environment                                                                         |
+| ----------------------- | ---------------------------- | ----------------------------------------------------------------------------------- |
+| `@homarr/common`        | `index.ts` -> `src/index.ts` | Shared root; includes React hooks and some Next/Mantine-aware helpers               |
+| `@homarr/common/types`  | `src/types.ts`               | Type-only utilities                                                                 |
+| `@homarr/common/server` | `src/server.ts`              | Node/server-only security, encryption, request, error, and bounded-response helpers |
+| `@homarr/common/client` | `src/client.ts`              | Client-facing Next server action export                                             |
+| `@homarr/common/env`    | `env.ts`                     | Validated package environment                                                       |
+
+## Root exports
+
+| Area              | Public exports                                                                                                                                       | Purpose                                                         |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
+| Objects           | `objectKeys`, `objectEntries`, `hashObjectBase64`                                                                                                    | Typed key/entry iteration and stable query-key hashing          |
+| Strings           | `capitalize`, `isNullOrWhitespace`, `bestMatch`, `normalizeImageName`, `getImageMatchRank`                                                           | Text normalization and matching                                 |
+| Cookies           | `parseCookies`, `setClientCookie`                                                                                                                    | Cookie parsing and browser cookie serialization                 |
+| Arrays            | `splitToNChunks`, `splitToChunksWithNItems`                                                                                                          | Split by number of groups or maximum group size                 |
+| Dates             | `formatDuration`, `toValidDate`, `isDateWithin`                                                                                                      | Duration formatting, safe date coercion, relative-window checks |
+| Timing            | `Stopwatch`                                                                                                                                          | Elapsed-time measurement and formatting                         |
+| React hooks       | `useTimeAgo`, `useIntegrationConnected`                                                                                                              | Relative time and integration freshness state                   |
+| URLs              | `removeTrailingSlash`, `extractBaseUrlFromHeaders`, `getPortFromUrl`, `isAbsoluteUrl`, `SAFE_NEW_TAB_REL`, `getSafeApplicationUrl`, `getSafeAppHref` | URL normalization, safe navigation, ports, and new-tab policy   |
+| Numbers and bytes | `formatNumber`, `randomInt`, `formatBytes`, `formatBytesPair`, `formatByteRate`, `metricToImperial`, `imperialToMetric`                              | Compact numbers, byte displays, rates, and unit conversion      |
+| Legacy bytes      | `humanFileSize`                                                                                                                                      | Deprecated; use the `formatBytes*` helpers in new code          |
+| Byte types        | `ByteUnitSystem`, `FormatBytesOptions`                                                                                                               | Options for byte formatting                                     |
+| Errors            | `extractErrorMessage`, `FlattenError`                                                                                                                | Unknown-error messages and flattenable domain errors            |
+| Theme             | `getMantineColor`                                                                                                                                    | Resolve a Mantine color and shade                               |
+| Functions         | `isFunction`                                                                                                                                         | Unknown-value function guard                                    |
+| Grid              | `GridAlgorithmItem`, `generateResponsiveGridFor`                                                                                                     | Responsive nested-section grid placement                        |
+| IDs               | `createId`                                                                                                                                           | CUID2 ID creation                                               |
+
+The root deliberately does not re-export `types`, `server`, `client`, or `env`; use their named entrypoints.
+
+## Types exports
+
+`@homarr/common/types` exports:
+
+- `MaybePromise<T>`
+- `AtLeastOneOf<T>`
+- `Modify<T, R>`
+- `RemoveReadonly<T>`
+- `MaybeArray<T>`
+- `Inverse<T>`
+- `inferSearchParamsFromSchema<TSchema>`
+
+## Server exports
+
+`@homarr/common/server` exports:
+
+- Security: `generateSecureRandomToken`.
+- Encryption: `encryptSecret`, `decryptSecret`, `decryptSecretWithKey`, `createKeyedFingerprint`, `verifyKeyedFingerprint`.
+- Requests: `userAgent`, `DeviceType`, `ipAddressFromHeaders`.
+- Bounded bodies: `readBoundedJsonResponseAsync`.
+- Parse errors: `ParseError`, `ParseErrorHandler`, `ZodParseErrorHandler`, `JsonParseErrorHandler`.
+- HTTP handlers: `HttpErrorHandler`, `FetchHttpErrorHandler`, `matchErrorCode`, `OFetchHttpErrorHandler`, `AxiosHttpErrorHandler`, `TsdavHttpErrorHandler`, `OctokitHttpErrorHandler`.
+- HTTP errors: `RequestError`, `ResponseError`, `requestErrorMap`.
+- HTTP error types: `AnyRequestError`, `AnyRequestErrorInput`, `RequestErrorInput`, `RequestErrorType`, `RequestErrorReason`, `AnyRequestErrorReason`, `RequestErrorCode`.
+
+`NodeFetchHttpErrorHandler` exists as an implementation file but is not exported by the public server entrypoint. Add an intentional public export before using it across packages.
+
+## Client and environment exports
+
+- `@homarr/common/client` exports `revalidatePathActionAsync`, a Next server action for page revalidation.
+- `@homarr/common/env` exports `env` with validated `NODE_ENV`, `SECRET_ENCRYPTION_KEY`, and `NO_EXTERNAL_CONNECTION` values.

.agents/skills/documentation-sync/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: documentation-sync
+description: Keep Homarr's Docusaurus documentation aligned with user-facing code. Use when adding or changing integrations, widgets, APIs, environment variables, CLI commands, authentication, permissions, cron jobs, settings, or UI behavior that users must understand.
+---
+
+# Documentation Sync
+
+Update `apps/docs/` in the same change as user-facing behavior. Inspect adjacent pages and the docs types before copying a pattern; the source and docs evolve together.
+
+## Map the change
+
+| Code change                         | Documentation target                                                 |
+| ----------------------------------- | -------------------------------------------------------------------- |
+| New integration                     | `apps/docs/docs/integrations/<slug>/index.mdx` and `index.ts`        |
+| New widget                          | `apps/docs/docs/widgets/<slug>/index.mdx` and `index.ts`             |
+| Changed public or management API    | `apps/docs/docs/management/api/index.mdx`                            |
+| New or changed environment variable | Relevant page under `apps/docs/docs/advanced/` or installation docs  |
+| New or changed CLI command          | `apps/docs/docs/advanced/command-line/`                              |
+| Authentication/provider change      | Relevant SSO or authentication page under `apps/docs/docs/advanced/` |
+| UI or workflow change               | Relevant getting-started, management, widget, or integration page    |
+| Cron-job behavior                   | `apps/docs/docs/management/tasks.mdx`                                |
+| Permission behavior                 | `apps/docs/docs/management/users.mdx` and the affected feature page  |
+| Custom Widget or Workshop behavior  | Relevant Custom Widget, Assistant, or Workshop documentation         |
+
+If no existing row fits, search by the user-visible term and update the page where a user would look for the behavior:
+
+```bash
+rg -n "<term>" apps/docs/docs apps/docs/src
+```
+
+## Follow existing typed patterns
+
+For an integration:
+
+- Add or update `apps/docs/docs/integrations/<slug>/index.ts` with the local `IntegrationDefinition` pattern.
+- Add or update `index.mdx` with the established `IntegrationHeader`, `IntegrationCapabilites`, and `IntegrationSecrets` components as applicable.
+- Reuse metadata from `@homarr/definitions` when the docs app already exposes it.
+
+For a widget:
+
+- Add or update `apps/docs/docs/widgets/<slug>/index.ts` with the local `WidgetDefinition` pattern.
+- Add or update `index.mdx` with the established `WidgetHeader`, `WidgetConfig`, and `AddingWidget` components as applicable.
+- Document options, required integrations, permissions, empty states, and changed behavior that affect setup or use.
+
+## Completion criteria
+
+1. Describe the shipped behavior, not an implementation plan.
+2. Keep names, defaults, paths, screenshots, links, and prerequisites consistent with code.
+3. Update every affected page and remove superseded guidance.
+4. Run the narrowest useful docs validation. Use `pnpm turbo build --filter=@homarr/docs` when links, MDX, generated definitions, or navigation can fail; otherwise run the docs package formatter on touched files.
+5. Treat broken links and anchors as failures; Docusaurus checks them strictly.

.agents/skills/documentation-sync/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Homarr Documentation Sync"
+  short_description: "Keep user-facing docs aligned with code"
+  default_prompt: "Use $documentation-sync to map this Homarr code change to the required documentation updates."

.agents/skills/homarr-custom-widget/SKILL.md

@@ -1,36 +1,43 @@
 ---
 name: homarr-custom-widget
-description: Author safe Homarr Custom JSX v2 widgets from API documentation.
+description: Author, validate, preview, test, install, or configure API-backed Homarr Custom JSX v2 widgets.
 ---
 
 # Homarr Custom Widget
 
-Author one widget at a time. When connected to Homarr, retrieve `homarr://custom-widgets/schema` and only the component resources needed for the design. The live resources are authoritative for the installed release.
+Author one widget or a coordinated set of widgets. Load only needed release-matched context. Run lifecycle tools alone; independent reads may run together. For a set, research once and finish each widget's validation, evidence, and persistence before the next.
 
-Keep documentation retrieval targeted: fetch at most eight named component documents before the first validation, or at most four after loading a complete example. Fetch another component only when a validation issue or a concrete missing interaction requires it; never load the catalog component-by-component.
+1. Read primary API documentation. Use web search when documentation is not supplied or may have changed.
+2. Create credential-free definitions with keyed `sources`, `requests`, optional `options`, and safe JSX `template`.
+3. While drafting, use `customWidget_validateTemplate` for focused JSX diagnostics without resending the manifest.
+4. Send the definition once to `customWidget_previewCreate` and test its queries/actions. For a JSX-only fix, validate, call `customWidget_previewReviseTemplate` with its session, and retest; it inherits the manifest and resets evidence. Create a preview only for source/request/option changes.
+5. Configure deployment-specific source URLs and credentials through Homarr; never repeat plaintext.
+6. Persist each exact final tested preview with `customWidget_createFromPreview`. Do not resend a large definition through `customWidget_create` when a preview session is available.
 
-1. Read the API documentation.
-2. Create one credential-free widget with keyed `sources`, keyed `requests`, optional keyed `options`, and safe JSX `template`.
-3. Validate, preview, test queries and simulated actions, visually inspect, and iterate.
-4. Configure deployment-specific source URLs and request credentials through Homarr; never repeat plaintext.
-5. Save only after narrow/wide, light/dark, loading, empty, error, and success states work. When connected through MCP, persist the exact final tested preview with `customWidget_createFromPreview`; do not resend a large template through `customWidget_create` unless no preview session is available.
+Treat a supplied sample or successful preview response as the binding contract. Render every core requested field, guard optional arrays and nested values before indexing, and do not silently drop returned items. Humanize numeric enums with indexed literal label arrays, omit absent numeric values instead of inventing zero, and label timestamp timezones. Give recoverable load errors and empty states a clear refresh or retry path.
 
-Treat a supplied sample or successful preview response as the binding contract. Render every core requested field, guard optional arrays and nested values before indexing, and do not silently drop returned items. Show concise freshness context when the API supplies a timestamp. Give recoverable load errors and empty states a clear refresh or retry path.
+Use `{option:name}` or `$option` for saved options. Use `{param:name}` or `$param` for values supplied by `SubFetch`, `ActionButton`, or `ToggleSwitch`. Load queries cannot use invocation parameters. Render load queries from `data` and `status` with `RefreshButton`; reserve `SubFetch` for manual parameterized queries. Templates read `data`, `status`, `options`, and temporary `inputs`.
 
-Use `{option:name}` or `$option` for saved options. Use `{param:name}` or `$param` for values supplied by `SubFetch`, `ActionButton`, or `ToggleSwitch`. Load queries cannot use invocation parameters. Templates read `data`, `status`, `options`, and temporary `inputs`.
+For a bound control that depends on another input, declare its default and set `resetKey` to that scalar dependency. For example, `<Pagination bind="page" defaultValue={1} resetKey={inputs.search} />` restores page 1 when a search changes without fetching by itself.
 
-`SubFetch` with `trigger="manual"` renders its own load button. Pass a card or image through `triggerContent` with `triggerAriaLabel` when that content should launch the request. Its callback is `(result, meta)`; never author `onClick` or a fetch callback.
+`SubFetch` with `trigger="manual"` renders its own load button. Pass a card or image through `triggerContent` with `triggerAriaLabel` when that content should launch the request. Its callback is `(result, meta)`; callback names must not shadow the reserved roots `data`, `status`, `options`, or `inputs`. Never author `onClick` or a fetch callback. Use `Icon` or `TablerIcon` with a `name`; never invent an `IconFoo` component.
 
-Use standard Mantine compound names and deliberate visual hierarchy, spacing, restrained semantic color, and responsive layouts. Avoid excessive nested cards.
+Plan capabilities. Use one `customWidget_findComponents` search per job. Batch selected non-obvious binding or interaction documentation with `customWidget_getComponents`; reserve `customWidget_getComponent` for one unknown-prop repair. Failed validation reopens discovery; otherwise search only for a missing capability. The full catalog is for broad exploration; load at most one example. Context never limits composition. Prefer clear hierarchy, responsive grids, divided lists, and aligned actions over nested row cards.
 
-Aim for distinctive polish without decorative gradients or fragile custom styling: use one semantic accent, clear surface contrast, purposeful typography, and compact rows that remain scannable in narrow tiles. Give standalone icons an accessible label or pair them with visible text.
+Do not simplify a useful workflow merely because the template is interpreted. Freely compose any supported installed components with multiple sources, requests, options, `choicesFrom`, bound filters, charts, responsive detail areas, manual queries, and safe actions when they improve the user's job. Complexity must remain purposeful rather than decorative.
 
-Make initial states actionable with an example, useful hint, or clear next step. Use wrapping groups for variable-length labels and values on narrow tiles. Do not use an unlabeled decorative icon as an empty state.
+Polish with a divided list or responsive media grid. Make one metric/action asymmetrically primary; keep headers compact, identity/state clear, metadata quiet, and one badge. At base artwork fills its row and caps above xs; never combine full-width media and nowrap.
+
+Make initial states actionable and wrap variable labels/values on narrow tiles. Do not use an unlabeled decorative icon as an empty state.
 
 Do not use imports, hooks, refs, raw HTML, raw event callbacks, browser requests, arbitrary functions, eval, bigint, npm packages, authored statement blocks, IIFEs, or recursion. Do not pretend MCP tools exist in an offline chat session.
 
-To install an existing widget, use `customWidget_workshopSearch`, inspect it with `customWidget_workshopGet`, then use `customWidget_workshopInstall`. Configure each self-hosted source afterward with `customWidget_sourceConfigure`, or call `customWidget_configurationRequestUser` so the user can enter the server URL and credentials directly in Homarr.
+For a community widget, use `customWidget_workshopSearch`, `customWidget_workshopGet`, then `customWidget_workshopInstall`; configure its source securely. Preview configuration expires, so create before persisting configuration.
 
-Preview-scoped configuration expires with the preview. To persist user-entered values for a new widget, create the widget first, request configuration for its definition ID, then create a final preview with that definition ID so Homarr loads the stored credentials.
+Reference routing:
 
-When this skill is installed from the repository, optional offline details are in `references/schema.md`, `references/runtime.md`, and `references/security.md`. MCP-only clients should use the live Homarr resources instead.
+- Load `schema` once before a new manifest; otherwise only for concrete request or option ambiguity.
+- Load `runtime` for bound inputs, manual queries, actions, or other interaction.
+- Load `security` once for any authenticated source or mutation, or to resolve a URL or interpreter limitation.
+
+Repository installations expose these as files under `references/`. MCP clients can call `customWidget_getReference` or read `homarr://custom-widgets/references/{name}` instead of loading every reference.

.agents/skills/homarr-custom-widget/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Homarr Custom Widget"
+  short_description: "Build and deploy safe Custom JSX widgets"
+  default_prompt: "Use $homarr-custom-widget to author, validate, preview, and configure a safe Custom JSX v2 widget."

.agents/skills/homarr-custom-widget/references/runtime.md

@@ -1,16 +1,37 @@
 # Runtime
 
-Templates read `data.requestId`, `status.requestId`, `options.name`, and temporary `inputs.name`. Status contains `loading`, `ok`, `status`, `statusText`, and `error`.
+Templates read `data.requestId`, `status.requestId`, `options.name`, and temporary `inputs.name`. Status is `{ loading, ok, status, statusText, error }`. Render load queries directly from `data` and `status` with `RefreshButton`; never wrap them in `SubFetch`.
 
 `bind="search"` creates an in-memory input. It is never persisted. Supply invocation values only through `params`, for example:
 
 ```jsx
 <TextInput bind="search" label="Search" />
-<SubFetch requestId="search" params={{ query: inputs.search }}>
-  {(items) => <Stack>{(items ?? []).map(item => <Text key={item.id}>{item.name}</Text>)}</Stack>}
+<Pagination bind="page" resetKey={inputs.search} defaultValue={1} total={5} />
+<SubFetch requestId="search" trigger="manual" params={{ query: inputs.search }}>
+  {(result) => <Stack>{(result.results ?? []).map(item => <Text key={item.id}>{item.name}</Text>)}</Stack>}
 </SubFetch>
 ```
 
-`SubFetch` with `trigger="manual"` renders its own load button. To make a card or image launch the request, pass that node through `triggerContent` and provide `triggerAriaLabel`; Homarr supplies the click and keyboard behavior. Its optional second callback argument contains `{ ok, status, statusText, loading: false }`; loading and request failures are rendered by `SubFetch` before the callback runs. Do not author `onClick` or a fetch callback.
+Manual queries require `trigger: "manual"` on request and `SubFetch`; otherwise they run automatically. `triggerContent` with `triggerAriaLabel` makes custom content the launcher. `SubFetch` owns loading/error/retry; its child receives success plus `{ ok, status, statusText, loading: false }`. Never author `onClick` or fetch callbacks.
 
-Use expression callbacks for supported collection methods and trusted slots. Do not use callback blocks, IIFEs, authored recursion, or raw events. Bounded regex literals work only with safe string matching/replacement operations.
+`SubFetch`, `ActionButton`, and `ToggleSwitch` need literal `requestId`; validation rejects missing/computed IDs.
+
+Inside a successful manual result, `<RefreshButton requestId="search" label="Run again" />` reruns the same parameters.
+
+When a manual SubFetch request ID, parameters, or effective definition changes, Homarr immediately hides its prior result and returns to the trigger. It cannot fetch the new parameters until the user triggers it again.
+
+The `SubFetch` callback receives the entire JSON response exactly as previewed. If the response is `{ "results": [...] }`, render and map `result.results`; never map the envelope itself. Trace every rendered field from the preview response before persistence.
+
+Format timestamps with safe static helpers; never use `new Date`. Never invent a formatter component. Use `Date.toLocaleString(value, "en-US", "UTC")` plus a visible `UTC` label. Also available: `Date.toISOString`, `Date.toLocaleDateString`, and `Date.toLocaleTimeString`.
+
+For compact numeric enums, index a literal label array with a fallback:
+
+```jsx
+<Text>{["Unknown", "Pending", "Ready"][(item.status ?? 1) - 1] ?? "Unknown"}</Text>
+```
+
+Every stateful control must use `bind`, and its `inputs.<name>` value must feed a supported request/helper when it is meant to change remote data. For dependent pagination, declare `defaultValue={1}` and use `resetKey={inputs.search}` to restore page 1 when the query changes. If a control cannot affect the workflow through a binding, option, or runtime helper, render concise context instead of a dead control.
+
+Callback parameters must not shadow the reserved roots `data`, `status`, `options`, or `inputs`. Use `<Icon name="refresh" />` or `<TablerIcon name="refresh" />`; never invent components such as `<IconFoo />`.
+
+Use expression callbacks for supported collections and trusted slots. No callback blocks, IIFEs, authored recursion, or raw events. Regex is limited to safe string operations.

.agents/skills/homarr-custom-widget/references/schema.md

@@ -13,10 +13,37 @@ interface HomarrCustomWidgetV2 {
 }
 ```
 
-Sources require `default`. A request defaults to the default source, query, GET, load, inherited auth, and view permission. An action defaults to manual and modify permission. DELETE uses full permission and confirmation.
+The object key `default` is the required source ID; `default` is not a property on a source. Source properties are `name?`, `baseUrl`, `networkScope`, and `auth?`:
+
+```json
+{
+  "sources": {
+    "default": {
+      "name": "Service",
+      "baseUrl": "http://service.local:5055/api/v1",
+      "networkScope": "private",
+      "auth": { "type": "apiKeyHeader", "name": "X-Api-Key" }
+    }
+  },
+  "requests": {
+    "summary": { "path": "/summary" },
+    "search": { "trigger": "manual", "path": "/search", "query": { "q": { "$param": "query" } } },
+    "create": {
+      "kind": "action",
+      "method": "POST",
+      "path": "/items",
+      "body": { "id": { "$param": "id" } },
+      "confirmation": "Create this item?",
+      "invalidates": ["search"]
+    }
+  }
+}
+```
+
+Auth is `none`, `bearer`, `basic`, `{ "type": "apiKeyHeader", "name": "X-Api-Key" }`, or `{ "type": "apiKeyQuery", "name": "api_key" }`. A request defaults to source `default`, kind `query`, method `GET`, trigger `load`, inherited auth, and view permission. Set `trigger: "manual"` for a parameterized query. An action defaults to manual and modify permission. DELETE uses full permission and confirmation. Do not use `load: false`.
 
 Use stable real URLs for public APIs and clear suggested URLs for self-hosted services. Homarr collects the installer's server URL, network scope, and credentials as source setup; credentials remain outside the manifest.
 
-Paths use `{option:name}` and `{param:name}`. Query/body data uses `{ "$option": "name" }` and `{ "$param": "name" }`. Load queries cannot use params. Runtime parameter names and primitive values are inferred from references.
+Paths use `{option:name}` and `{param:name}`; query/body references use `{ "$option": "name" }` and `{ "$param": "name" }`. Constants stay primitive (`take: 10`); `$param` is only for manual helpers, never load queries. Names and types are inferred.
 
 Every option has `label`, `control`, and `default`. Optional fields are `description`, `choices`, `choicesFrom`, `min`, `max`, `step`, `advanced`, and `group`.

.agents/skills/mcp-integration/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: mcp-integration
+description: Expose Homarr tRPC procedures safely through MCP. Use when adding or changing tRPC procedures under packages/api, adding MCP metadata, registering an eager MCP router, shaping tool inputs and descriptions, or reviewing MCP authorization, sensitive data, and destructive actions.
+---
+
+# MCP Integration
+
+Expose a procedure only when an AI client should call it. Preserve the procedure's existing authorization and add MCP-specific safeguards for sensitive or destructive behavior.
+
+## Assess exposure
+
+Prefer:
+
+- Data queries: list, search, get, health, stats, and summaries.
+- User-requested actions with explicit permission checks and bounded inputs.
+- Serializable results that do not reveal credentials or internal-only state.
+
+Skip subscriptions, session/onboarding internals, file streams, blobs, credential values, and procedures whose authorization or audit behavior is unclear. Ask for a security review when a mutation is destructive, tenant boundaries are ambiguous, or returned data is sensitive.
+
+## Add metadata
+
+Place `.meta()` before `.input()` and `.query()` or `.mutation()`:
+
+```typescript
+getAll: protectedProcedure
+  .meta({
+    mcp: {
+      enabled: true,
+      description: "List resources the current user can access, including stable IDs used by resource_get",
+    },
+  })
+  .input(z.object({ limit: z.number().int().min(1).max(100).default(50) }))
+  .query(async ({ ctx, input }) => {
+    // Preserve normal procedure authorization.
+  });
+```
+
+No-input procedures can omit `.input()`; the MCP extractor accepts an empty object for them.
+
+For mutations, state the effect and required permission in the description:
+
+```typescript
+remove: permissionRequiredProcedure
+  .meta({
+    mcp: {
+      enabled: true,
+      description: "Delete one resource by ID. Requires full access; get the ID from resource_all",
+    },
+  })
+  .input(z.object({ id: z.string() }))
+  .mutation(async ({ ctx, input }) => {
+    // Perform the permission-scoped action.
+  });
+```
+
+## Write discoverable descriptions
+
+Include every item that applies:
+
+- What the tool returns or changes.
+- Supported integrations or services.
+- Required IDs and the tool that returns them.
+- Permission requirements and the meaning of permission fields.
+- Important bounds, confirmation semantics, or irreversible effects.
+
+Use precise domain language. A description such as `Get calendar events` is insufficient because it omits supported services, required IDs, and result scope.
+
+## Shape inputs for clients
+
+- Use a top-level `z.object({...})` for parameterized tools.
+- Bound strings, arrays, numeric ranges, pagination, and payload sizes.
+- Use defaults where a safe, unsurprising value exists.
+- Prefer explicit fields over a top-level union or discriminated union.
+- Keep identifiers stable and describe how to obtain them.
+- Keep secrets out of inputs unless the procedure is explicitly a credential-configuration flow with server-owned encryption and non-return guarantees.
+
+## Register the eager router
+
+The application router in `packages/api/src/root.ts` is lazy. MCP tool extraction is synchronous, so add an eager import and registration in `packages/api/src/mcp.ts`:
+
+```typescript
+import { resourceRouter } from "./router/resource";
+
+export const mcpRouter = createTRPCRouter({
+  resource: resourceRouter,
+});
+```
+
+Register the smallest router that owns the enabled procedures. If a parent router uses `lazy()`, import the needed subrouter directly. Metadata on a procedure is not enough; a procedure absent from `mcpRouter` is not exposed.
+
+## Validate the tool surface
+
+1. Confirm the procedure still enforces its ordinary auth and permission boundary.
+2. Confirm `packages/api/src/mcp.ts` eagerly includes the procedure.
+3. Confirm the generated tool name, description, and JSON schema are unambiguous.
+4. Run the focused API MCP spec when the tool list or extraction changes: `pnpm test packages/api/src/test/mcp.spec.ts`.
+5. Run the focused route spec when protocol or transport behavior changes: `pnpm test apps/nextjs/src/app/api/mcp/[transport]/route.spec.ts`.
+6. If manually probing `/api/mcp/<transport>`, use a scoped API key and avoid printing credentials or secret-bearing results.

.agents/skills/mcp-integration/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Homarr MCP Integration"
+  short_description: "Expose tRPC procedures safely through MCP"
+  default_prompt: "Use $mcp-integration to expose this Homarr tRPC procedure as a safe, discoverable MCP tool."

.claude/skills

@@ -0,0 +1 @@
+../.agents/skills

.cursor/rules/codebase-context.mdc

@@ -1,204 +0,0 @@
----
-description: Comprehensive Homarr codebase architecture and conventions reference
-alwaysApply: true
----
-
-# Homarr Codebase Context
-
-Homarr is an open-source, self-hosted dashboard for managing homelab services. It integrates with 50+ self-hosted apps (media servers, download clients, DNS, NAS, etc.) and provides a drag-and-drop widget-based UI.
-
-## Tech Stack
-
-- **Monorepo**: pnpm workspaces + Turborepo
-- **Framework**: Next.js (App Router, `output: "standalone"`) — T3 Stack
-- **Language**: TypeScript throughout
-- **ORM**: Drizzle (supports SQLite via better-sqlite3, MySQL, PostgreSQL)
-- **API**: tRPC (HTTP + WebSocket subscriptions) with superjson + OpenAPI bridge via `trpc-to-openapi`
-- **Auth**: NextAuth v5 (database sessions, Credentials/LDAP/OIDC providers)
-- **UI**: Mantine v9 (not Tailwind) + Tabler icons
-- **State**: Jotai (atoms), TanStack Query (server state via tRPC)
-- **Realtime**: WebSocket server (`ws`) for tRPC subscriptions, backed by Redis pub/sub
-- **Cron**: `node-cron` in a standalone Fastify service (`apps/tasks`)
-- **i18n**: next-intl with `[locale]` dynamic segment (prefix mode: `"never"`, locale from cookie)
-- **Testing**: Vitest + jsdom, Playwright for E2E
-- **Lint/Format**: oxlint + oxfmt (not ESLint/Prettier)
-- **Docs**: Docusaurus 3 in `apps/docs/` (`@homarr/docs`)
-- **Package manager**: pnpm 10.34.1, Node >= 24.16.0
-
-## Repository Structure
-
-```
-homarr/
-├── apps/
-│   ├── nextjs/          # Main Next.js application (port 3000)
-│   ├── docs/            # Docusaurus 3 documentation site (@homarr/docs)
-│   ├── tasks/           # Cron job runner + Fastify tRPC API (port 3002)
-│   └── websocket/       # Standalone tRPC WebSocket server (port 3001)
-├── packages/
-│   ├── api/             # tRPC appRouter, procedures, OpenAPI
-│   ├── auth/            # NextAuth config, providers, session, API keys
-│   ├── db/              # Drizzle schema (3 DB drivers), migrations, queries
-│   ├── core/            # Env validation, DB/Redis driver factories, logging
-│   ├── definitions/     # Domain enums: WidgetKind, IntegrationKind, permissions
-│   ├── widgets/         # All 39 dashboard widgets (definitions + components)
-│   ├── integrations/    # Integration classes (HTTP clients to external apps)
-│   ├── redis/           # Redis pub/sub channels, caching abstractions
-│   ├── translation/     # next-intl setup, locale configs, lang JSON files
-│   ├── ui/              # Shared Mantine components, theme, hooks
-│   ├── validation/      # Shared zod schemas for API/forms
-│   ├── common/          # Shared utilities, IDs, errors
-│   ├── cron-jobs/       # Cron job implementations (25+ jobs)
-│   ├── cron-jobs-core/  # Cron scheduling primitives
-│   ├── cron-job-api/    # tRPC router for job management (start/stop/trigger)
-│   ├── cron-job-status/ # Cron status via Redis
-│   ├── boards/          # Board context, edit mode, cache updater
-│   ├── modals/          # Modal primitives on Mantine
-│   ├── modals-collection/ # Feature modals (apps, boards, docker, etc.)
-│   ├── form/            # useZodForm (Mantine + zod resolver)
-│   ├── forms-collection/# Reusable form UIs (new app, icon picker, upload)
-│   ├── spotlight/       # Command palette / search with multiple modes
-│   ├── request-handler/ # Server request handlers (feeds, integrations)
-│   ├── notifications/   # Mantine notifications wrapper
-│   ├── docker/          # Dockerode-based Docker access
-│   ├── icons/           # Icon DB/repo integration
-│   ├── image-proxy/     # Image proxy + caching
-│   ├── ping/            # Reachability / ping utilities
-│   ├── analytics/       # Server-side analytics (Umami)
-│   ├── server-settings/ # Server setting keys/types
-│   ├── settings/        # User-facing settings UI context
-│   └── cli/             # Node CLI for ops (brocli)
-├── tooling/
-│   ├── typescript/      # Base tsconfig
-│   └── github/          # CI setup action
-├── development/         # Dev docker-compose (Redis, MySQL, PostgreSQL)
-├── e2e/                 # E2E test specs
-└── Dockerfile           # Multi-stage production build
-```
-
-## Three Runtime Services
-
-| Service | Port | Role |
-|---------|------|------|
-| Next.js | 3000 | Main web app (SSR + API routes) |
-| WebSocket | 3001 | tRPC subscriptions via `ws` |
-| Tasks | 3002 | Cron job runner + management API via Fastify |
-
-In Docker, nginx listens on **7575** and proxies to all three. The tasks service authenticates via `CRON_JOB_API_KEY` header.
-
-## Package Dependency Layers
-
-1. **Foundation**: `core` (env, DB drivers, Redis client, logging) → no `@homarr` deps
-2. **Domain**: `definitions` → `common` → `core`
-3. **Data**: `db` → `core`, `definitions`, `common`
-4. **Auth**: `auth` → `db`, `definitions`, `core`, `validation`
-5. **Cross-cutting**: `translation`, `validation`, `redis`, `server-settings`
-6. **Feature backends**: `integrations`, `request-handler`, `cron-jobs`, `docker`, `ping`
-7. **API surface**: `api` → pulls in auth, db, redis, integrations, etc.
-8. **UI stack**: `ui`, `modals`, `form`, `notifications`, `boards`, `spotlight`
-9. **Composed features**: `widgets`, `modals-collection`, `forms-collection`
-
-## Key Patterns
-
-### tRPC
-
-- **Server caller** (RSC): `import { api } from "@homarr/api/server"` → cached caller with auth context
-- **Client hooks**: `import { clientApi } from "@homarr/api/client"` → React Query hooks
-- **Router structure**: `packages/api/src/root.ts` defines top-level namespaces (`user`, `board`, `widget`, `integration`, `docker`, `kubernetes`, etc.)
-- **Procedures**: `publicProcedure`, `protectedProcedure`, `permissionRequiredProcedure`, `onboardingProcedure`
-- **WebSocket subscriptions**: Client uses `wsLink` when `type === "subscription"`, connects to port 3001
-
-### Multi-Database Support
-
-Drizzle schemas exist in three parallel implementations:
-- `packages/db/schema/sqlite.ts`
-- `packages/db/schema/mysql.ts`
-- `packages/db/schema/postgresql.ts`
-
-Selected at runtime via `DB_DRIVER` env (`better-sqlite3` | `mysql2` | `node-postgres`). Migrations are per-engine in `packages/db/migrations/{sqlite,mysql,postgresql}/`.
-
-### Widget System
-
-Widgets are registered in `packages/widgets/src/index.tsx` as `widgetImports` (must satisfy `Record<WidgetKind, ...>`). Each widget:
-- Has a `definition` created via `createWidgetDefinition(kind, { icon, createOptions, supportedIntegrations? })`
-- Uses `optionsBuilder.from(factory => ({ ... }))` for typed options
-- Loads dynamically via `next/dynamic`
-- Fetches data via tRPC client hooks (backed by cron job caches)
-
-### Integration System
-
-Integrations are defined in `packages/definitions/src/integration.ts` (`integrationDefs`) and instantiated via `createIntegrationAsync` in `packages/integrations/src/base/creator.ts`. Each extends abstract `Integration` class with `testConnectionAsync` and typed methods.
-
-### Cron Job System
-
-Jobs defined in `packages/cron-jobs/src/jobs/`. Each job:
-- Uses `createCronJob` with a cron expression
-- Publishes results to Redis channels
-- Widget subscriptions consume those channels via tRPC subscriptions
-- Job management (start/stop/trigger) via `cronJobApi` HTTP client to port 3002
-
-### Modals
-
-Created with `createModal(component).withOptions({ defaultTitle })` from `@homarr/modals`. Opened via `useModalAction(SomeModal)`. Feature modals live in `packages/modals-collection/`.
-
-### Forms
-
-`useZodForm` from `@homarr/form` wraps Mantine `useForm` with zod validation. Shared form UIs in `packages/forms-collection/`.
-
-### Routing (App Router)
-
-- `apps/nextjs/src/app/[locale]/` — all UI routes under locale segment
-- Route groups: `(home)`, `(content)`, `(board)` — don't affect URLs
-- Key routes: `boards/[name]`, `manage/...` (admin), `auth/login`, `init` (onboarding), `widgets/[kind]`
-- Locale driven by cookie (no URL prefix)
-
-### Auth Providers
-
-Configured via `AUTH_PROVIDERS` env. Supports: `credentials` (local), `ldap`, `oidc`. Database sessions with httpOnly cookies. API key auth for programmatic access.
-
-## Environment Variables
-
-Key env vars (from `.env.example`):
-- `DB_DRIVER`: `better-sqlite3` | `mysql2` | `node-postgres`
-- `DB_URL`: Database connection string
-- `AUTH_SECRET`: NextAuth secret
-- `SECRET_ENCRYPTION_KEY`: AES-256-CBC for integration secrets
-- `AUTH_PROVIDERS`: Comma-separated (`credentials`, `ldap`, `oidc`)
-- `CRON_JOB_API_KEY`: Shared key between Next.js and tasks service
-- `REDIS_*`: Redis connection (host, port, password)
-- `ENABLE_KUBERNETES`: Optional Kubernetes integration
-
-## Development Commands
-
-- `pnpm dev` — runs all three services in parallel via Turborepo
-- `pnpm docker:dev` — starts Redis + MySQL + PostgreSQL containers
-- `pnpm db:push` — push schema to SQLite (dev)
-- `pnpm db:studio` — Drizzle Studio
-- `pnpm test` — Vitest unit tests
-- `pnpm test:e2e` — Playwright E2E
-- `pnpm lint` / `pnpm format` — oxlint + oxfmt
-- `pnpm dev:docs` — Docusaurus docs site (port 3003)
-- `pnpm typecheck` — tsc --noEmit across all packages
-
-## Conventions
-
-- Workspace packages use `@homarr/` scope
-- All versions managed via pnpm `catalog:` in workspace
-- Path alias `~/*` → `./src/*` in Next.js app
-- Mantine for all UI (no Tailwind) — primary color is red, `autoContrast: true`
-- Icons from `@tabler/icons-react`
-- Drag-and-drop via `@dnd-kit/*`
-- `typescript.ignoreBuildErrors: true` in next.config (types checked separately via `typecheck`)
-- `serverExternalPackages`: `dockerode`, `isomorphic-dompurify`, `jsdom`
-
-## Documentation (`apps/docs`)
-
-Docusaurus 3 site at `apps/docs/`, package name `@homarr/docs`.
-
-- Run with `pnpm dev:docs` from root
-- Build with `pnpm turbo build --filter=@homarr/docs`
-- Uses Tailwind CSS 3 for custom pages (not Mantine)
-- Imports `@homarr/definitions` for type-safe integration/widget metadata
-- When adding or modifying widgets, integrations, cron jobs, API routes, env vars, or user-facing features, you MUST also update corresponding docs in `apps/docs/docs/`
-- Integration docs: `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts`
-- Widget docs: `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`
-- Strict link checking: broken links/anchors cause build failure

.cursor/rules/documentation-sync.mdc

@@ -1,50 +0,0 @@
----
-description: Keep documentation in sync with code changes
-globs:
-  - packages/definitions/src/**
-  - packages/widgets/src/**
-  - packages/integrations/src/**
-  - packages/api/src/**
-  - apps/nextjs/src/**
-  - apps/docs/**
----
-
-# Documentation Sync Rule
-
-When modifying code that affects user-facing behavior, you MUST also update the documentation in `apps/docs/`.
-
-## What triggers a doc update
-
-| Code change | Doc location |
-|---|---|
-| New integration | `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts` |
-| New widget | `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts` |
-| Changed API surface | `apps/docs/docs/management/api.mdx` |
-| New/changed env vars | `apps/docs/docs/advanced/` |
-| New CLI commands | `apps/docs/docs/advanced/command-line/` |
-| Changed auth providers | `apps/docs/docs/advanced/` SSO pages |
-| UI/UX changes | Relevant getting-started or management pages |
-| New cron job | `apps/docs/docs/management/tasks.mdx` |
-| Changed permissions | `apps/docs/docs/management/users.mdx` |
-
-## Integration doc pattern
-
-Each integration has a folder under `apps/docs/docs/integrations/<slug>/`:
-
-- `index.ts` — exports a typed `IntegrationDefinition` with name, description, iconUrl, path
-- `index.mdx` — uses shared components: `IntegrationHeader`, `IntegrationCapabilites`, `IntegrationSecrets`
-- Import metadata from `@homarr/definitions` where possible
-
-## Widget doc pattern
-
-Each widget has a folder under `apps/docs/docs/widgets/<slug>/`:
-
-- `index.ts` — exports a typed `WidgetDefinition` with icon, name, description, path, configuration
-- `index.mdx` — uses shared components: `WidgetHeader`, `WidgetConfig`, `WidgetAdding`
-
-## Development
-
-- Run docs locally: `pnpm dev:docs` from root
-- Build docs: `pnpm turbo build --filter=@homarr/docs`
-- The docs app can import from `@homarr/definitions` for type-safe integration/widget metadata
-- Docusaurus strict mode throws on broken links — fix any broken references before committing

.cursor/rules/mantine-datatable-migration.mdc

@@ -1,612 +0,0 @@
-# Migrating Tables from mantine-react-table to mantine-datatable
-
-This document captures every pattern, fix, and decision from the downloads widget rework (PR #6430). Use it as a playbook when porting other tables.
-
-## Migration Candidates
-
-Current `mantine-react-table` consumers that could be migrated:
-
-**Widgets (in `packages/widgets/`):**
-- `docker/component.tsx` — Docker container table
-- `media-server/component.tsx` — Media server sessions
-
-**Admin pages (in `apps/nextjs/src/app/[locale]/manage/`):**
-- `tools/docker/docker-table.tsx`
-- `tools/tasks/_components/tasks-table.tsx`
-- `tools/api/components/api-keys.tsx`
-- `users/_components/user-list.tsx`
-- `users/invites/_components/invite-list.tsx`
-- `tools/kubernetes/` — 8 Kubernetes resource tables
-
-**Modals:**
-- `packages/modals-collection/src/search-engines/request-media-modal.tsx`
-
-**Shared hook to remove once all migrated:**
-- `packages/ui/src/hooks/use-translated-mantine-react-table.ts`
-
----
-
-## 1. Core Migration: mantine-react-table → mantine-datatable
-
-### Import changes
-
-```typescript
-// BEFORE
-import { MantineReactTable, useMantineReactTable } from "mantine-react-table";
-import type { MRT_ColumnDef } from "mantine-react-table";
-
-// AFTER
-import { DataTable, useDataTableColumns } from "mantine-datatable";
-import type { DataTableColumn, DataTableSortStatus } from "mantine-datatable";
-```
-
-### Column definition shape
-
-```typescript
-// BEFORE (MRT)
-const columns: MRT_ColumnDef<MyRow>[] = [
-  {
-    accessorKey: "name",
-    header: "Name",
-    size: 200,
-    enableSorting: true,
-    Cell: ({ row }) => <Text>{row.original.name}</Text>,
-  },
-];
-
-// AFTER (mantine-datatable)
-const columns: DataTableColumn<MyRow>[] = [
-  {
-    accessor: "name",           // not accessorKey
-    title: "Name",              // not header
-    width: 200,                 // not size
-    sortable: true,             // not enableSorting
-    render: (record) => <Text>{record.name}</Text>,  // not Cell
-  },
-];
-```
-
-Key differences:
-- `accessorKey` → `accessor`
-- `header` → `title`
-- `size` → `width`
-- `Cell: ({ row }) =>` → `render: (record) =>`
-- `enableSorting` → `sortable`
-- `enableColumnActions` → does not exist (no column action menus)
-- `mantineTableBodyCellProps` → `cellsStyle` in `defaultColumnProps`
-
-### Table component
-
-```typescript
-// BEFORE
-const table = useTranslatedMantineReactTable({ columns, data, ... });
-return <MantineReactTable table={table} />;
-
-// AFTER
-return (
-  <DataTable
-    records={data}
-    columns={columns}
-    sortStatus={sortStatus}
-    onSortStatusChange={setSortStatus}
-    ...
-  />
-);
-```
-
-### Sorting is manual
-
-mantine-datatable does NOT sort for you. You must sort the data yourself:
-
-```typescript
-const [sortStatus, setSortStatus] = useState<DataTableSortStatus<MyRow>>({
-  columnAccessor: "name",
-  direction: "asc",
-});
-
-const sortedData = useMemo(() => {
-  const mult = sortStatus.direction === "desc" ? -1 : 1;
-  return [...data].toSorted((a, b) => {
-    const aVal = a[sortStatus.columnAccessor];
-    const bVal = b[sortStatus.columnAccessor];
-    if (typeof aVal === "string") return aVal.localeCompare(bVal as string) * mult;
-    return ((aVal as number) - (bVal as number)) * mult;
-  });
-}, [data, sortStatus]);
-
-// Pass sortedData to records, not data
-<DataTable records={sortedData} sortStatus={sortStatus} onSortStatusChange={setSortStatus} />
-```
-
----
-
-## 2. Making Tables Transparent (Widget Context)
-
-Widgets sit inside board cards that have user-controlled opacity. The table must be fully transparent so the card background shows through. mantine-datatable defaults to `var(--mantine-color-body)` which is opaque.
-
-Create a CSS file alongside the component:
-
-```css
-/* styles.css */
-.my-table,
-.my-table .mantine-datatable-table,
-.my-table .mantine-datatable-table thead,
-.my-table .mantine-datatable-table tbody,
-.my-table .mantine-datatable-table tfoot,
-.my-table th,
-.my-table td {
-  background-color: transparent !important;
-}
-
-.my-table .mantine-datatable-table tr {
-  background-color: transparent;
-}
-
-/* Hover: translucent instead of opaque */
-.my-table .mantine-datatable-table tbody tr:hover {
-  background-color: color-mix(in srgb, var(--mantine-color-default-hover) 40%, transparent) !important;
-}
-
-/* Headers: frosted glass effect */
-.my-table th {
-  white-space: nowrap;
-  background-color: color-mix(in srgb, var(--mantine-color-body) 60%, transparent) !important;
-  backdrop-filter: blur(8px);
-}
-
-/* Cell overflow */
-.my-table td {
-  white-space: nowrap;
-  overflow: hidden;
-  text-overflow: ellipsis;
-}
-
-/* Hide sort icon until hover */
-.my-table .mantine-datatable-header-cell-sortable-icon {
-  opacity: 0;
-  transition: opacity 150ms;
-}
-.my-table th:hover .mantine-datatable-header-cell-sortable-icon {
-  opacity: 1;
-}
-
-/* Row expansion area */
-.my-table .mantine-datatable-row-expansion-cell {
-  background-color: color-mix(in srgb, var(--mantine-color-body) 40%, transparent) !important;
-}
-```
-
-Import it: `import "./styles.css";` and apply via `className="my-table"`.
-
----
-
-## 3. Responsive Column Visibility
-
-Use a lookup table of width breakpoints instead of media queries. The widget receives `width` as a prop.
-
-```typescript
-interface SizeConfig {
-  fontSize: "xs" | "sm";
-  iconSize: number;
-  cellPadding: number;
-  showSpeedColumns: boolean;
-  showTimeColumn: boolean;
-  showStateColumn: boolean;
-}
-
-const SIZE_BREAKPOINTS: { maxWidth: number; config: SizeConfig }[] = [
-  { maxWidth: 300, config: { fontSize: "xs", iconSize: 12, cellPadding: 2, showSpeedColumns: false, showTimeColumn: false, showStateColumn: false } },
-  { maxWidth: 500, config: { fontSize: "xs", iconSize: 14, cellPadding: 4, showSpeedColumns: false, showTimeColumn: true, showStateColumn: false } },
-];
-
-const DEFAULT_SIZE_CONFIG: SizeConfig = { fontSize: "sm", iconSize: 14, cellPadding: 4, showSpeedColumns: true, showTimeColumn: true, showStateColumn: true };
-
-function getSizeConfig(width: number): SizeConfig {
-  for (const { maxWidth, config } of SIZE_BREAKPOINTS) {
-    if (width < maxWidth) return config;
-  }
-  return DEFAULT_SIZE_CONFIG;
-}
-
-// Usage: memoize it
-const size = useMemo(() => getSizeConfig(width), [width]);
-```
-
-Then use a visibility check lookup table for columns:
-
-```typescript
-const columnVisibilityChecks: Partial<Record<string, (ctx: ColumnContext) => boolean>> = {
-  upSpeed: (ctx) => ctx.hasTorrents && ctx.size.showSpeedColumns,
-  downSpeed: (ctx) => ctx.size.showSpeedColumns,
-  time: (ctx) => ctx.size.showTimeColumn,
-  state: (ctx) => ctx.size.showStateColumn,
-};
-
-function shouldIncludeColumn(accessor: string, ctx: ColumnContext): boolean {
-  if (!ctx.optionsColumnSet.has(accessor)) return false;
-  const check = columnVisibilityChecks[accessor];
-  if (check && !check(ctx)) return false;
-  return true;
-}
-```
-
----
-
-## 4. Column Persistence (Drag/Resize → Server)
-
-`useDataTableColumns` stores column order and widths in localStorage by default. For widgets, this must persist server-side so it works across devices.
-
-### Hidden widget options
-
-In `index.ts`, add hidden text options:
-
-```typescript
-columnOrder: factory.text({ defaultValue: "" }),
-columnWidths: factory.text({ defaultValue: "" }),
-```
-
-With visibility override:
-
-```typescript
-{
-  columnOrder: { shouldHide: () => true },
-  columnWidths: { shouldHide: () => true },
-}
-```
-
-### Translation keys required
-
-Even hidden options need translation keys or the translation test fails:
-
-```json
-"widget.mywidget.option.columnOrder.label": "Column order",
-"widget.mywidget.option.columnWidths.label": "Column widths"
-```
-
-### Dynamic storeKey
-
-Use a key that includes `itemId` and sorted column names. This prevents cross-widget localStorage bleeding:
-
-```typescript
-const storeKey = `mytable-${itemId ?? "preview"}-${[...options.columns].toSorted().join(",")}`;
-```
-
-### Hydration from server → localStorage
-
-On mount, seed `useDataTableColumns` with server-persisted values. Use a `hydrated` ref to prevent the persist effect from immediately writing defaults back:
-
-```typescript
-const { effectiveColumns, columnsOrder, columnsWidth, setColumnsOrder, setMultipleColumnWidths } =
-  useDataTableColumns<MyRow>({ key: storeKey, columns });
-
-const lastStoreKey = useRef(storeKey);
-const hydrated = useRef(false);
-
-useEffect(() => {
-  if (lastStoreKey.current !== storeKey) {
-    lastStoreKey.current = storeKey;
-    hydrated.current = false;
-  }
-  if (hydrated.current) return;
-  if (savedOrder.length > 0) setColumnsOrder(savedOrder);
-  if (Object.keys(savedWidths).length > 0) {
-    setMultipleColumnWidths(
-      Object.entries(savedWidths).map(([accessor, w]) => ({ accessor, width: w })),
-    );
-  }
-  requestAnimationFrame(() => { hydrated.current = true; });
-}, [storeKey, savedOrder, savedWidths, setColumnsOrder, setMultipleColumnWidths]);
-```
-
-### Persist localStorage → server
-
-Watch for changes and write back:
-
-```typescript
-const prevOrder = useRef(columnsOrder);
-const prevWidths = useRef(columnsWidth);
-
-useEffect(() => {
-  if (!hydrated.current) return;
-  const orderChanged = JSON.stringify(columnsOrder) !== JSON.stringify(prevOrder.current);
-  const widthsChanged = JSON.stringify(columnsWidth) !== JSON.stringify(prevWidths.current);
-  prevOrder.current = columnsOrder;
-  prevWidths.current = columnsWidth;
-
-  if (!orderChanged && !widthsChanged) return;
-
-  if (orderChanged) persistOption({ columnOrder: JSON.stringify(columnsOrder) });
-  if (widthsChanged) {
-    const widthMap: Record<string, number> = {};
-    for (const entry of columnsWidth) {
-      const key = Object.keys(entry)[0];
-      if (!key) continue;
-      const w = entry[key as keyof typeof entry];
-      if (typeof w === "number") widthMap[key] = w;
-      else if (typeof w === "string" && w.endsWith("px")) widthMap[key] = parseInt(w, 10);
-    }
-    persistOption({ columnWidths: JSON.stringify(widthMap) });
-  }
-}, [columnsOrder, columnsWidth, persistOption]);
-```
-
-The `persistOption` helper calls both `setOptions` (local state) and `saveItemOptions` (server mutation).
-
----
-
-## 5. Context Menu (Right-Click)
-
-Do NOT install `mantine-contextmenu`. Use Mantine's `Menu` + `Portal` directly:
-
-```typescript
-interface ContextMenuState {
-  x: number;
-  y: number;
-  item: MyRow;
-}
-
-const [contextMenu, setContextMenu] = useState<ContextMenuState | null>(null);
-
-const handleContextMenu = useCallback(
-  ({ record, event }: { record: MyRow; event: React.MouseEvent }) => {
-    event.preventDefault();
-    setContextMenu({ x: event.clientX, y: event.clientY, item: record });
-  },
-  [],
-);
-
-// On DataTable:
-<DataTable onRowContextMenu={handleContextMenu} />
-
-// Render:
-{contextMenu && <RowContextMenu state={contextMenu} onClose={closeContextMenu} />}
-```
-
-The menu component uses `Portal` for correct z-index:
-
-```tsx
-function RowContextMenu({ state, onClose }: { state: ContextMenuState; onClose: () => void }) {
-  return (
-    <Portal>
-      <Menu opened onClose={onClose} closeOnItemClick={false} position="right-start" offset={0}>
-        <Menu.Target>
-          <Box style={{ position: "fixed", left: state.x, top: state.y, width: 0, height: 0 }} />
-        </Menu.Target>
-        <Menu.Dropdown>
-          <Menu.Item onClick={() => { /* action */ onClose(); }}>Action</Menu.Item>
-        </Menu.Dropdown>
-      </Menu>
-    </Portal>
-  );
-}
-```
-
-**Key fix:** Use `closeOnItemClick={false}` if any menu item needs a two-step confirmation (like delete → confirm). Close the menu on scroll: `onScroll={() => { if (contextMenu) closeContextMenu(); }}`.
-
----
-
-## 6. Row Expansion
-
-```typescript
-<DataTable
-  rowExpansion={{
-    trigger: "click",
-    allowMultiple: true,
-    collapseProps: {
-      transitionDuration: 200,
-      animateOpacity: true,
-      transitionTimingFunction: "ease-out",
-    },
-    content: ({ record, collapse }) => <ExpandedRow item={record} collapse={collapse} />,
-  }}
-/>
-```
-
-**Critical:** Do NOT set `onRowClick` when using `rowExpansion` with `trigger: "click"`. They conflict and the expansion won't work.
-
----
-
-## 7. Common Pitfalls & Fixes
-
-### Status indicator dots
-
-Don't use `<Badge variant="dot" />` without children — it renders a pill with empty space. Use a plain `Box`:
-
-```tsx
-<Box
-  w={8}
-  h={8}
-  style={{
-    borderRadius: "50%",
-    backgroundColor: `var(--mantine-color-${color}-filled)`,
-    flexShrink: 0,
-  }}
-/>
-```
-
-### Tooltip overflow on long text columns
-
-When a column has `ellipsis: true`, the tooltip target element can still extend beyond the cell bounds if inner elements don't clip. Fix:
-
-```tsx
-<Tooltip position="bottom-start" ...>
-  <Group style={{ overflow: "hidden" }}>
-    ...
-  </Group>
-</Tooltip>
-```
-
-Use `position="bottom-start"` instead of `position="right"` so the tooltip never escapes the widget horizontally.
-
-### Dark mode tooltips
-
-Mantine tooltips default to the theme's tooltip color which may be white in light mode and stay white in dark mode. Always set `color="dark"` on informational tooltips inside widgets.
-
-### Division by zero
-
-Guard all ratio calculations:
-
-```typescript
-if (item.size > 0) ratio = item.sent / item.size;
-if (totalDown > 0) ratio = totalUp / totalDown;
-```
-
-### Composite idAccessor
-
-When rows can come from multiple integrations, IDs may collide. Use a composite key:
-
-```typescript
-idAccessor={(record) => `${record.integration.id}:${record.id}`}
-```
-
-### JSON option parsing
-
-Always wrap in try/catch:
-
-```typescript
-function parseJsonOption<T>(value: string | undefined, fallback: T): T {
-  if (!value) return fallback;
-  try { return JSON.parse(value) as T; }
-  catch { return fallback; }
-}
-```
-
-### Clipboard API
-
-`navigator.clipboard.writeText()` can throw in non-HTTPS contexts. Always catch:
-
-```typescript
-void navigator.clipboard.writeText(text).catch(() => {});
-```
-
-### Sync sortStatus with widget options
-
-If the widget has configurable default sort, sync it:
-
-```typescript
-useEffect(() => {
-  setSortStatus({ columnAccessor: options.defaultSort, direction: defaultSortDirection });
-}, [options.defaultSort, defaultSortDirection]);
-```
-
----
-
-## 8. Accessibility
-
-- All `ActionIcon` components need `aria-label`
-- Filter toggles (client badges, status badges) need `aria-pressed={isActive}`
-- `textSelectionDisabled` on DataTable prevents accidental text selection during drag/resize
-
----
-
-## 9. Error Handling
-
-- Every mutation needs an `onError` callback with `showErrorNotification`
-- The `saveItemOptions` mutation (column persistence) also needs `onError`
-- Check `isError` on the main query and show a fallback UI
-- Use a shared `mutationOptions` object to avoid repeating `onSettled`/`onError`:
-
-```typescript
-const mutationOptions = {
-  onSettled: () => void utils.myQuery.invalidate(),
-  onError: () => showErrorNotification({ title: t("errors.actionFailed"), message: t("errors.actionFailedMessage") }),
-};
-```
-
----
-
-## 10. i18n
-
-- No hardcoded strings. Every user-visible string goes through `useScopedI18n`
-- Column titles: `t("items.{accessor}.columnTitle")`
-- Detail labels: `t("items.{accessor}.detailsTitle")`
-- States: `t("states.{state}")`
-- Actions: `t("actions.{action}")`
-- Errors: `t("errors.{errorKey}")`
-- Hidden options still need `.label` translation keys
-
----
-
-## 11. Edit Mode
-
-Disable pointer events on the table during edit mode to prevent conflicts with the board's drag-and-drop:
-
-```typescript
-let tablePointerEvents: React.CSSProperties["pointerEvents"];
-if (isEditMode) tablePointerEvents = "none";
-
-let rowContextMenuHandler = handleContextMenu;
-if (isEditMode) rowContextMenuHandler = undefined;
-
-<DataTable style={{ pointerEvents: tablePointerEvents }} />
-```
-
----
-
-## 12. DataTable Props Reference (Commonly Used)
-
-```typescript
-<DataTable
-  records={sortedData}
-  columns={effectiveColumns}
-  storeColumnsKey={storeKey}
-  withTableBorder={false}
-  borderRadius={0}
-  highlightOnHover
-  striped="odd"
-  stripedColor={{ dark: "dark.7", light: "gray.0" }}
-  highlightOnHoverColor={{ dark: "dark.5", light: "gray.1" }}
-  verticalAlign="center"
-  fetching={isFetching && data.length === 0}
-  loaderBackgroundBlur={2}
-  fz={size.fontSize}
-  textSelectionDisabled
-  sortStatus={sortStatus}
-  onSortStatusChange={setSortStatus}
-  noRecordsText={t("errors.noItems")}
-  idAccessor={(record) => record.uniqueKey}
-  height="100%"
-  className="my-table"
-  defaultColumnProps={{
-    noWrap: true,
-    draggable: true,
-    resizable: true,
-    cellsStyle: () => ({ padding: `${size.cellPadding}px 8px` }),
-  }}
-  scrollAreaProps={{ type: "auto", scrollbarSize: 6 }}
-  rowBackgroundColor={(record) => conditionalBgMap[record.state]}
-  onRowContextMenu={handleContextMenu}
-  rowExpansion={{ ... }}
-  onScroll={() => { if (contextMenu) closeContextMenu(); }}
-/>
-```
-
----
-
-## 13. Layout Stability
-
-- Don't use `table-layout: fixed` — it fights mantine-datatable's resize logic
-- Give non-name columns explicit `width` values so only the name column flexes
-- Use `ellipsis: true` on the name column — it handles `text-overflow: ellipsis` internally
-- Names should truncate at the cell boundary, not a character count, so the layout is stable regardless of content length
-- `flexShrink: 0` on badges/icons prevents them from being squeezed by long names
-
----
-
-## 14. Checklist for Each Migration
-
-1. Replace imports (`mantine-react-table` → `mantine-datatable`)
-2. Convert column definitions (`accessorKey` → `accessor`, `header` → `title`, `Cell` → `render`, etc.)
-3. Implement manual sorting with `useState` + `useMemo`
-4. Add CSS file for transparent backgrounds (if widget context)
-5. Add responsive column visibility (if widget context)
-6. Add hidden options + hydration logic (if column persistence needed)
-7. Add translation keys (including hidden option labels)
-8. Add context menu if row actions exist
-9. Add row expansion if detail view exists
-10. Add error handling on all mutations
-11. Add accessibility attributes
-12. Test at multiple widget widths
-13. Update docs in `apps/docs/docs/widgets/` if applicable
-14. Run `pnpm turbo typecheck`
-15. Run translation spec — catches missing keys

.cursor/rules/mcp-integration.mdc

@@ -1,103 +0,0 @@
----
-description: How to expose tRPC procedures as MCP tools for AI clients
-globs: packages/api/src/router/**/*.ts
-alwaysApply: false
----
-
-# MCP Integration Guide
-
-Every new tRPC procedure that provides useful functionality should be exposed as an MCP tool so AI assistants (Claude, Cursor, etc.) can use it. This is a first-class feature of Homarr.
-
-## Adding MCP to a procedure
-
-Add `.meta({ mcp: { enabled: true, description: "..." } })` to the procedure chain:
-
-```typescript
-// Read-only tool (query)
-myProcedure: protectedProcedure
-  .meta({ mcp: { enabled: true, description: "Get all items with their status and metadata" } })
-  .input(z.object({ limit: z.number().default(50) }))
-  .query(async ({ ctx, input }) => { ... })
-
-// Write tool (mutation)
-myAction: protectedProcedure
-  .meta({ mcp: { enabled: true, description: "Delete an item by ID. Requires interact permission on the integration" } })
-  .input(z.object({ id: z.string() }))
-  .mutation(async ({ ctx, input }) => { ... })
-
-// No-input procedure (z.void) — works fine, no .input() needed
-getAll: protectedProcedure
-  .meta({ mcp: { enabled: true, description: "List all resources" } })
-  .query(async ({ ctx }) => { ... })
-```
-
-The `.meta()` call must come **before** `.input()` and `.query()`/`.mutation()` in the chain.
-
-## Writing good descriptions
-
-The description is the **only thing** an AI sees to decide when and how to use the tool. Write it like you're explaining to a colleague who has never used Homarr.
-
-**Must include:**
-- What the tool returns or does
-- Which integrations/services it works with (if applicable)
-- How to get required IDs (e.g., "Use integration_all to get the integrationId")
-- Permission requirements (if non-obvious)
-
-**Good:**
-```
-"Get calendar events for upcoming and recent media releases. Fetches from all connected Sonarr (TV), Radarr (movies), Lidarr (music), and Readarr (books) integrations. Requires integrationIds from integration_all"
-```
-
-**Bad:**
-```
-"Get calendar events"
-```
-
-**For tools that return permission fields**, explain what they mean:
-```
-"List all integrations. Returns permissions.hasUseAccess (read) and permissions.hasInteractAccess (actions) — false means the API key lacks that permission, not an error"
-```
-
-## Registering in the MCP router
-
-After adding `.meta()` to procedures, you must register the router in `packages/api/src/mcp.ts`. This file uses **eager imports** (no `lazy()`) because MCP tool extraction requires synchronous access to all procedure definitions.
-
-```typescript
-// packages/api/src/mcp.ts
-import { myNewRouter } from "./router/my-new-feature";
-
-export const mcpRouter = createTRPCRouter({
-  // ... existing routers
-  myFeature: myNewRouter,
-});
-```
-
-**If your router is nested** (e.g., widget sub-routers), import and register the sub-router directly — do not import a parent that uses `lazy()`.
-
-## What to expose vs. what to skip
-
-**Expose:**
-- Data queries (list, search, get by ID)
-- Actions users would ask an AI to do (toggle, create, delete, approve)
-- Status checks (health, stats, summaries)
-
-**Skip:**
-- Subscriptions (WebSocket-only, not supported by MCP)
-- Internal procedures (session management, onboarding steps)
-- File upload/download procedures
-- Procedures that return non-serializable data (streams, blobs)
-
-## Input schema rules
-
-- Use `z.object({...})` for inputs — this maps cleanly to MCP tool parameters
-- `z.void()` (no `.input()`) works — the MCP handler patches these to accept empty objects
-- Avoid `z.union()` or `z.discriminatedUnion()` at the top level — AI clients struggle with these
-- Use `.default()` on optional fields so the AI doesn't need to guess values
-
-## Checklist for new features
-
-1. Add `.meta({ mcp: { enabled: true, description: "..." } })` to relevant procedures
-2. Import and register the router in `packages/api/src/mcp.ts` (eager, no lazy)
-3. Write descriptions that explain what the tool does, what it needs, and what it returns
-4. If the tool requires an ID from another tool, say which one in the description
-5. Test with `curl` against `/api/mcp/mcp` to verify the tool appears in `tools/list`

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -33,6 +33,10 @@ body:
       options:
         # The below comment is used to insert a new version with on-release.yml
         #NEXT_VERSION#
+        - 1.76.2
+        - 1.76.1
+        - 1.76.0
+        - 1.75.0
         - 1.74.0
         - 1.73.0
         - 1.72.0

.github/actions/extract-build-artifact/action.yaml

@@ -20,7 +20,7 @@ runs:
   using: "composite"
   steps:
     - name: Prebuilt debian dependencies
-      uses: homarr-labs/homarr/.github/actions/prebuilt-debian@dev
+      uses: ./.github/actions/prebuilt-debian
       id: prebuilt-debian
       with:
         architecture: ${{ inputs.architecture }}

.github/actions/prebuilt-debian/action.yaml

@@ -11,9 +11,6 @@ outputs:
 runs:
   using: "composite"
   steps:
-    - uses: actions/checkout@v7
-      with:
-        persist-credentials: false
     - name: Set up Docker Buildx
       uses: docker/setup-buildx-action@v4
 

.github/workflows/autofix.yml

@@ -3,7 +3,7 @@ name: Formatting
 on:
   pull_request:
     types: [opened, synchronize, reopened]
-    branches: ["*"]
+    branches: ["**"]
 
 permissions:
   contents: read

.github/workflows/ci.yml

@@ -51,7 +51,7 @@ jobs:
     name: Fast gate
     if: github.event_name != 'pull_request_target' && (github.event_name != 'workflow_dispatch' || inputs.operation != 'cleanup')
     runs-on: ubuntu-latest
-    timeout-minutes: 15
+    timeout-minutes: 20
     env:
       TURBO_API: ${{ secrets.TURBO_API }}
       TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
@@ -320,8 +320,12 @@ jobs:
 
   publish-preview:
     name: Publish multi-platform preview image
-    needs: [preview-amd64, preview-arm64]
+    needs: [container, preview-amd64, preview-arm64]
     if: |
+      !cancelled() &&
+      needs.container.result == 'success' &&
+      needs.preview-amd64.result == 'success' &&
+      needs.preview-arm64.result == 'success' &&
       (
         (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
         (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
@@ -374,21 +378,25 @@ jobs:
           AMD64_DIGEST: ${{ needs.preview-amd64.outputs.digest }}
           ARM64_DIGEST: ${{ needs.preview-arm64.outputs.digest }}
         run: |
-          docker buildx imagetools create -t "${PREVIEW_IMAGE}:${PREVIEW_TAG}" \
+          tags=(-t "${PREVIEW_IMAGE}:${PREVIEW_TAG}")
+          docker buildx imagetools create "${tags[@]}" \
             "${PREVIEW_IMAGE}@${AMD64_DIGEST}" \
             "${PREVIEW_IMAGE}@${ARM64_DIGEST}"
 
       - name: Verify preview manifest platforms
         if: "!env.ACT"
         run: |
-          image="${PREVIEW_IMAGE}:${PREVIEW_TAG}"
-          manifest="$(docker buildx imagetools inspect "$image" --raw)"
-          for architecture in amd64 arm64; do
-            jq --exit-status --arg architecture "$architecture" \
-              'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
-              <<<"$manifest" >/dev/null
+          tags=("${PREVIEW_TAG}")
+          for tag in "${tags[@]}"; do
+            image="${PREVIEW_IMAGE}:${tag}"
+            manifest="$(docker buildx imagetools inspect "$image" --raw)"
+            for architecture in amd64 arm64; do
+              jq --exit-status --arg architecture "$architecture" \
+                'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
+                <<<"$manifest" >/dev/null
+            done
+            docker buildx imagetools inspect "$image"
           done
-          docker buildx imagetools inspect "$image"
 
   cleanup:
     name: Clean up preview image
@@ -425,6 +433,14 @@ jobs:
               core.info(`No package version found with tag "${tag}"`);
               return;
             }
+            const targetTags = target.metadata?.container?.tags ?? [];
+            const extraTags = targetTags.filter((targetTag) => targetTag !== tag);
+            if (extraTags.length > 0) {
+              core.warning(
+                `Package version ${target.id} also carries tag(s) ${extraTags.map((targetTag) => `"${targetTag}"`).join(", ")}; refusing cleanup.`,
+              );
+              return;
+            }
             await github.rest.packages.deletePackageVersionForOrg({
               package_type: "container",
               package_name: packageName,

.github/workflows/deployment-docker-image.yml

@@ -13,7 +13,7 @@ on:
         type: boolean
         required: false
         default: true
-        description: Send notifications
+        description: Send notifications when redeploying an existing release
 
 permissions:
   contents: write # Required to update package.json version
@@ -38,10 +38,10 @@ jobs:
       SKIP_RELEASE: ${{ github.event_name == 'workflow_dispatch' || github.ref_name == 'dev' || github.ref_name == 'next' }}
     outputs:
       version: ${{ steps.read-semver.outputs.version || steps.version-fallback.outputs.version }}
-      git_ref: ${{ steps.read-git-ref.outputs.ref || github.ref }}
+      git_ref: ${{ steps.read-git-ref.outputs.ref || steps.read-semver.outputs.version || github.ref }}
       skipped: ${{ env.SKIP_RELEASE }}
     steps:
-      - run: echo "Skipping release for workflow_dispatch event"
+      - run: echo "Manual dispatch redeploys the latest existing release without creating a new one"
         if: env.SKIP_RELEASE == 'true'
         # The below generated version fallback represents a normalized branch name, for example "feature/branch-name" -> "feature-branch-name"
       - run: echo "version="$(echo ${{github.ref_name}} | sed 's/[^a-zA-Z0-9\-]/-/g') >> "$GITHUB_OUTPUT"
@@ -58,8 +58,9 @@ jobs:
           permission-contents: write # required to commit package.json & changelog changes, merge them to dev / next and publish the release
 
       - uses: actions/checkout@v7
-        if: env.SKIP_RELEASE == 'false'
+        if: env.SKIP_RELEASE == 'false' || github.ref_name == 'main' || github.ref_name == 'beta'
         with:
+          fetch-depth: 0
           persist-credentials: false
       - uses: pnpm/action-setup@v6
         if: env.SKIP_RELEASE == 'false'
@@ -68,12 +69,29 @@ jobs:
         with:
           node-version: 24.18.0
           package-manager-cache: false
-      - run: npm i -g pnpm
-        if: env.SKIP_RELEASE == 'false'
-      - name: Install dependencies
+      - name: Verify major release intent
         if: env.SKIP_RELEASE == 'false'
         run: |
-          pnpm install
+          latest_tag="$(git describe --tags --abbrev=0)"
+          latest_major="${latest_tag#v}"
+          latest_major="${latest_major%%.*}"
+          package_version="$(jq --raw-output '.version' package.json)"
+          package_major="${package_version%%.*}"
+
+          if (( package_major <= latest_major )); then
+            exit 0
+          fi
+
+          if git log --format='%s%n%b' "${latest_tag}..HEAD" \
+            | grep --extended-regexp --quiet '(^[[:alnum:]-]+(\([^)]*\))?!:)|(^BREAKING[ -]CHANGE:)'; then
+            exit 0
+          fi
+
+          echo "::error::package.json declares ${package_version}, but commits since ${latest_tag} contain no breaking-change signal. Use a conventional ! commit or BREAKING CHANGE footer so Semantic Release creates the intended major version."
+          exit 1
+      - name: Install dependencies
+        if: env.SKIP_RELEASE == 'false'
+        run: pnpm install --frozen-lockfile
       - name: Run Semantic Release
         if: env.SKIP_RELEASE == 'false'
         env:
@@ -205,9 +223,14 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
+      - uses: actions/checkout@v7
+        if: needs.release.outputs.skipped == 'false'
+        with:
+          ref: ${{ needs.release.outputs.git_ref }}
+          persist-credentials: false
       - name: Extract amd64
         if: needs.release.outputs.skipped == 'false'
-        uses: homarr-labs/homarr/.github/actions/extract-build-artifact@dev
+        uses: ./.github/actions/extract-build-artifact
         with:
           digest: "${{ env.GHCR_REPO }}@${{ needs.build-amd64.outputs.digest }}"
           architecture: amd64
@@ -221,9 +244,14 @@ jobs:
     runs-on: ubuntu-24.04-arm
     timeout-minutes: 5
     steps:
+      - uses: actions/checkout@v7
+        if: needs.release.outputs.skipped == 'false'
+        with:
+          ref: ${{ needs.release.outputs.git_ref }}
+          persist-credentials: false
       - name: Extract arm64
         if: needs.release.outputs.skipped == 'false'
-        uses: homarr-labs/homarr/.github/actions/extract-build-artifact@dev
+        uses: ./.github/actions/extract-build-artifact
         with:
           digest: "${{ env.GHCR_REPO }}@${{ needs.build-arm64.outputs.digest }}"
           architecture: arm64
@@ -284,6 +312,7 @@ jobs:
           gh release edit --repo ${{ github.repository }} ${{ needs.release.outputs.version }} --draft=false
 
       - name: Discord notification
+        if: github.event_name != 'workflow_dispatch' || inputs['send-notifications']
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
         uses: Ilshidur/action-discord@0.4.0

.github/workflows/on-pr-prebuilt-debian-validate.yml

@@ -5,7 +5,7 @@ permissions:
 
 on:
   pull_request:
-    branches: ["*"]
+    branches: ["**"]
     paths: [".github/actions/prebuilt-debian/**", "deployments/prebuilt-debian/**"]
 
 jobs:

.github/workflows/on-pr-renovate-validate.yml

@@ -5,7 +5,7 @@ permissions:
 
 on:
   pull_request:
-    branches: ["*"]
+    branches: ["**"]
     paths: [".github/renovate.json5"]
 
 jobs:

.github/workflows/update-contributors.yml

@@ -15,9 +15,6 @@ jobs:
   update-contributors:
     runs-on: ubuntu-latest
     timeout-minutes: 2
-    strategy:
-      matrix:
-        node-version: [22]
     steps:
       - name: Obtain token
         id: obtainToken
@@ -34,10 +31,10 @@ jobs:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
 
       - uses: pnpm/action-setup@v6
-      - name: Use Node.js ${{ matrix.node-version }}
+      - name: Use Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: ${{ matrix.node-version }}
+          node-version: 24.18.0
           cache: "pnpm"
 
       - name: Run update script

.github/workflows/workshop.yml

@@ -8,6 +8,10 @@ on:
 permissions:
   contents: read
 
+concurrency:
+  group: ${{ github.workflow }}-${{ (github.ref_name == 'v2' || github.ref_name == 'release/v2') && 'v2-preview' || github.ref }}
+  cancel-in-progress: true
+
 jobs:
   validate:
     runs-on: ubuntu-24.04
@@ -27,37 +31,116 @@ jobs:
       - run: pnpm test:workshop
       - run: pnpm test:workshop-image
 
-  publish:
+  publish-amd64:
     if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
     needs: validate
     runs-on: ubuntu-24.04
-    timeout-minutes: 30
+    timeout-minutes: 20
     permissions:
       contents: read
       packages: write
+    outputs:
+      digest: ${{ steps.build.outputs.digest }}
     steps:
       - uses: actions/checkout@v7
-      - uses: docker/setup-qemu-action@v4
       - uses: docker/setup-buildx-action@v4
       - uses: docker/login-action@v4
         with:
           registry: ghcr.io
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
-      - uses: docker/metadata-action@v6
-        id: metadata
-        with:
-          images: ghcr.io/homarr-labs/workshop
-          tags: |
-            type=sha,prefix=sha-,format=long
-            type=raw,value=v2,enable=${{ github.ref_name == 'v2' || github.ref_name == 'release/v2' }}
-            type=raw,value=latest,enable=${{ github.ref_name == 'main' }}
       - uses: docker/build-push-action@v7
+        id: build
         with:
           context: .
           file: apps/workshop/Dockerfile
           target: production
-          platforms: linux/amd64,linux/arm64
-          push: true
-          tags: ${{ steps.metadata.outputs.tags }}
-          labels: ${{ steps.metadata.outputs.labels }}
+          platforms: linux/amd64
+          outputs: type=image,"name=ghcr.io/homarr-labs/workshop",push-by-digest=true,name-canonical=true,push=true
+          cache-from: type=gha,scope=workshop-linux-amd64
+          cache-to: type=gha,scope=workshop-linux-amd64,mode=max
+
+  publish-arm64:
+    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
+    needs: validate
+    runs-on: ubuntu-24.04-arm
+    timeout-minutes: 20
+    permissions:
+      contents: read
+      packages: write
+    outputs:
+      digest: ${{ steps.build.outputs.digest }}
+    steps:
+      - uses: actions/checkout@v7
+      - uses: docker/setup-buildx-action@v4
+      - uses: docker/login-action@v4
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      - uses: docker/build-push-action@v7
+        id: build
+        with:
+          context: .
+          file: apps/workshop/Dockerfile
+          target: production
+          platforms: linux/arm64
+          outputs: type=image,"name=ghcr.io/homarr-labs/workshop",push-by-digest=true,name-canonical=true,push=true
+          cache-from: type=gha,scope=workshop-linux-arm64
+          cache-to: type=gha,scope=workshop-linux-arm64,mode=max
+
+  publish:
+    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
+    needs: [publish-amd64, publish-arm64]
+    runs-on: ubuntu-24.04
+    timeout-minutes: 5
+    permissions:
+      contents: read
+      packages: write
+    env:
+      WORKSHOP_IMAGE: ghcr.io/homarr-labs/workshop
+    steps:
+      - uses: docker/setup-buildx-action@v4
+      - uses: docker/login-action@v4
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      - name: Verify branch head before publication
+        uses: actions/github-script@v8
+        with:
+          script: |
+            const branchName = context.ref.replace("refs/heads/", "");
+            const { data: branch } = await github.rest.repos.getBranch({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              branch: branchName,
+            });
+            if (branch.commit.sha !== context.sha) {
+              core.setFailed(`Branch ${branchName} moved from ${context.sha} to ${branch.commit.sha}.`);
+            }
+      - name: Publish multi-platform image
+        env:
+          AMD64_DIGEST: ${{ needs.publish-amd64.outputs.digest }}
+          ARM64_DIGEST: ${{ needs.publish-arm64.outputs.digest }}
+        run: |
+          tags=(-t "${WORKSHOP_IMAGE}:sha-${GITHUB_SHA}")
+          if [[ "${GITHUB_REF_NAME}" == "v2" || "${GITHUB_REF_NAME}" == "release/v2" ]]; then
+            tags+=(-t "${WORKSHOP_IMAGE}:v2")
+          fi
+          if [[ "${GITHUB_REF_NAME}" == "main" ]]; then
+            tags+=(-t "${WORKSHOP_IMAGE}:latest")
+          fi
+          docker buildx imagetools create "${tags[@]}" \
+            "${WORKSHOP_IMAGE}@${AMD64_DIGEST}" \
+            "${WORKSHOP_IMAGE}@${ARM64_DIGEST}"
+      - name: Verify multi-platform image
+        run: |
+          image="${WORKSHOP_IMAGE}:sha-${GITHUB_SHA}"
+          manifest="$(docker buildx imagetools inspect "$image" --raw)"
+          for architecture in amd64 arm64; do
+            jq --exit-status --arg architecture "$architecture" \
+              'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
+              <<<"$manifest" >/dev/null
+          done
+          docker buildx imagetools inspect "$image"

.gitignore

@@ -25,6 +25,8 @@ packages/db/migrations/*/migrate.cjs
 
 # production
 build
+tools/homarr-dev/homarr
+tools/homarr-dev/homarr-dev
 
 # misc
 .DS_Store
@@ -74,9 +76,6 @@ apps/nextjs/public/images/background.png
 .opencode
 .agents/*
 !.agents/skills/
-.agents/skills/*
-!.agents/skills/homarr-custom-widget/
-!.agents/skills/homarr-custom-widget/**
 skills-lock.json
 
 # docusaurus
@@ -92,3 +91,6 @@ homarr-backup*.zip
 *.sqlite-wal
 *.sqlite-shm
 /scripts/benchmarks/
+
+# PR description screenshots belong on the pull request, not in the repository
+.screenshots/

.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "mantine": {
+      "command": "npx",
+      "args": ["-y", "@mantine/mcp-server@9.6.0"]
+    }
+  }
+}

.oxlintrc.json

@@ -30,6 +30,26 @@
   "options": {
     "reportUnusedDisableDirectives": "off"
   },
+  "overrides": [
+    {
+      "files": ["apps/nextjs/src/**/*.ts", "apps/nextjs/src/**/*.tsx"],
+      "excludeFiles": ["**/*.spec.ts", "**/*.spec.tsx"],
+      "rules": {
+        "eslint/no-restricted-imports": [
+          "error",
+          {
+            "paths": [
+              {
+                "name": "@homarr/widgets",
+                "allowTypeImports": true,
+                "message": "Import a narrow @homarr/widgets export to preserve widget lazy loading."
+              }
+            ]
+          }
+        ]
+      }
+    }
+  ],
   "ignorePatterns": [
     "**/*.config.js",
     "**/*.config.mjs",

AGENTS.md

@@ -7,22 +7,23 @@ homarr/
 ├── apps/
 │   ├── nextjs/          # Main Next.js application (port 3000)
 │   ├── docs/            # Docusaurus 3 documentation site (@homarr/docs)
-│   ├── tasks/           # Cron job runner + Fastify tRPC API (port 3002)
-│   └── websocket/       # Standalone tRPC WebSocket server (port 3001)
+│   ├── tasks/           # Cron-job initialization and scheduling runtime
+│   ├── websocket/       # Standalone tRPC WebSocket server (port 3001)
+│   └── workshop/        # Go/PocketBase Workshop service
 ├── packages/
 │   ├── api/             # tRPC appRouter, procedures, OpenAPI
 │   ├── auth/            # NextAuth config, providers, session, API keys
 │   ├── db/              # Drizzle schema (3 DB drivers), migrations, queries
 │   ├── core/            # Env validation, DB/Redis driver factories, logging
 │   ├── definitions/     # Domain enums: WidgetKind, IntegrationKind, permissions
-│   ├── widgets/         # All 39 dashboard widgets (definitions + components)
+│   ├── widgets/         # Dashboard widget definitions and components
 │   ├── integrations/    # Integration classes (HTTP clients to external apps)
 │   ├── redis/           # Redis pub/sub channels, caching abstractions
 │   ├── translation/     # next-intl setup, locale configs, lang JSON files
 │   ├── ui/              # Shared Mantine components, theme, hooks
 │   ├── validation/      # Shared zod schemas for API/forms
 │   ├── common/          # Shared utilities, IDs, errors
-│   ├── cron-jobs/       # Cron job implementations (25+ jobs)
+│   ├── cron-jobs/       # Cron job implementations
 │   ├── cron-jobs-core/  # Cron scheduling primitives
 │   ├── cron-job-status/ # Cron status via Redis
 │   ├── boards/          # Board context, edit mode, cache updater
@@ -40,6 +41,9 @@ homarr/
 │   ├── analytics/       # Server-side analytics (Umami)
 │   ├── server-settings/ # Server setting keys/types
 │   ├── settings/        # User-facing settings UI context
+│   ├── custom-widgets/  # Custom JSX v2 schema, validation, and runtime
+│   ├── onboarding/      # Onboarding studio and setup flow
+│   ├── workshop/        # Homarr-side Workshop client and contracts
 │   └── cli/             # Node CLI for ops (brocli)
 ├── tooling/
 │   ├── typescript/      # Base tsconfig
@@ -59,7 +63,7 @@ When modifying user-facing code, you MUST also update the corresponding document
 
 - New integration → `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts`
 - New widget → `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`
-- Changed API → `apps/docs/docs/management/api.mdx`
+- Changed API → `apps/docs/docs/management/api/index.mdx`
 - New/changed env vars → `apps/docs/docs/advanced/`
 - New CLI commands → `apps/docs/docs/advanced/command-line/`
 - Auth changes → `apps/docs/docs/advanced/` SSO pages
@@ -82,9 +86,19 @@ When modifying user-facing code, you MUST also update the corresponding document
 - Lint: oxlint (not ESLint)
 - Format: oxfmt (not Prettier)
 - UI: Mantine (not Tailwind) — Tailwind is only used in docs app
+- Mantine: use the project-scoped MCP server in `.mcp.json` for current v9 APIs, and check `packages/ui/` before creating a new primitive.
 - Icons: @tabler/icons-react
 - Docs app can import from `@homarr/definitions` for shared types
 - Run `pnpm dev:cli -- dev` to browse local `homarr:*` images and remote PR images.
 - Run `pnpm dev:cli -- build <name>` from a Homarr checkout to build `homarr:<name>` with rebuild provenance.
 - Run `pnpm dev:cli -- build --pr <number>` to build a PR locally from a temporary checkout.
 - Run Go checks from `tools/homarr-dev` with `go test ./...` and `go vet ./...`.
+
+## Agent Skills
+
+Portable skills live in `.agents/skills/`. Read the relevant `SKILL.md` before working in that domain; detailed references are loaded only when needed. Claude-compatible discovery is provided through `.claude/skills`.
+
+- `codebase-context` — architecture, package boundaries, and shared utilities
+- `documentation-sync` — required user-facing documentation updates
+- `mcp-integration` — safe tRPC-to-MCP exposure
+- `homarr-custom-widget` — safe Custom JSX v2 authoring

CHANGELOG.md

@@ -1,3 +1,11 @@
+## [1.76.2](https://github.com/homarr-labs/homarr/compare/v1.76.1...v1.76.2) (2026-08-27)
+
+## [1.76.1](https://github.com/homarr-labs/homarr/compare/v1.76.0...v1.76.1) (2026-08-26)
+
+## [1.76.0](https://github.com/homarr-labs/homarr/compare/v1.75.0...v1.76.0) (2026-08-21)
+
+## [1.75.0](https://github.com/homarr-labs/homarr/compare/v1.74.0...v1.75.0) (2026-08-14)
+
 ## [1.74.0](https://github.com/homarr-labs/homarr/compare/v1.73.0...v1.74.0) (2026-08-07)
 
 ## [1.73.0](https://github.com/homarr-labs/homarr/compare/v1.72.0...v1.73.0) (2026-07-31)

MANTINE.md

@@ -1,475 +0,0 @@
-# Mantine UI - LLM Documentation
-
-This index lists Mantine documentation pages formatted for LLMs.
-Each link points to a standalone Markdown file under the /llms path.
-
-For a single consolidated file with all content, use:
-
-- https://mantine.dev/llms-full.txt
-
-## FAQ
-
-- [Are Mantine components accessible?](https://mantine.dev/llms/q-are-mantine-components-accessible.md): Learn about Mantine components accessibility features
-- [Browser zooms in when input is focused. What should I do?](https://mantine.dev/llms/q-browser-zooms-on-focus.md): Use meta tag to disable browser scaling or increase input size
-- [Can I have color schemes other than light and dark?](https://mantine.dev/llms/q-light-dark-is-not-enough.md): Learn about the difference between color scheme and theme
-- [Can I have different primary color for light and dark color schemes?](https://mantine.dev/llms/q-primary-virtual-color.md): Learn how to use virtual color with primary color in theme object
-- [Can I remove MultiSelect placeholder when the component has selected values?](https://mantine.dev/llms/q-multiselect-value-placeholder.md): Learn why MultiSelect placeholder is not removed when values are selected and how to remove it with CSS
-- [Can I use an array of strings as a list in use-form?](https://mantine.dev/llms/q-list-of-strings-in-use-form.md): Learn about use-form lists limitations
-- [Can I use Mantine components as server components?](https://mantine.dev/llms/q-server-components.md): Learn about use client directive and server components usage
-- [Can I use Mantine with Astro?](https://mantine.dev/llms/q-can-i-use-mantine-with-astro.md): No, Astro does not support React context
-- [Can I use Mantine with Create React App (CRA)?](https://mantine.dev/llms/q-can-i-use-mantine-with-cra.md): Learn how to use Mantine without postcss-preset-mantine or how to eject CRA and customize webpack.config.js and use postcss-preset-mantine
-- [Can I use Mantine with Emotion/styled-components/tailwindcss?](https://mantine.dev/llms/q-third-party-styles.md): Learn about limitations of third-party styles
-- [Can I use Mantine with Vue/Svelte/Angular/etc.?](https://mantine.dev/llms/q-vue-svelte-angular.md): No, Mantine is a React library and does not support other frameworks/libraries
-- [Can I use nested inline styles with Mantine components?](https://mantine.dev/llms/q-nested-inline-styles.md): Nested styles are supported only in CSS files
-- [Can I use PostCSS function in inline styles?](https://mantine.dev/llms/q-postcss-fns-inline.md): Learn where PostCSS functions can be used in Mantine
-- [Can I use private CSS variables to style components?](https://mantine.dev/llms/q-private-css-variables.md): No, it is not safe and will not work with future versions of Mantine.
-- [Can I use SegmentedControl with empty value?](https://mantine.dev/llms/q-segmented-control-no-value.md): SegmentedControl cannot be used without a value
-- [How can I add dynamic CSS styles?](https://mantine.dev/llms/q-dynamic-css-styles.md): Use data attributes, CSS variables or inline styles
-- [How can I add fuzzy search to Select component?](https://mantine.dev/llms/q-select-fuzzy.md): Learn how to integrate third-party fuzzy search libraries with Mantine Select component
-- [How can I add hover styles to an element?](https://mantine.dev/llms/q-how-to-add-hover-styles.md): Learn how to add hover classes to an element with CSS modules, &:hover or @mixin hover
-- [How can I apply styles to all Mantine components?](https://mantine.dev/llms/q-apply-styles-to-all.md): Learn how to use attribute selector to apply styles to all Mantine components
-- [How can I change body background color?](https://mantine.dev/llms/q-body-background.md): Use CSS to change body background color
-- [How can I change component color prop value depending on the color scheme?](https://mantine.dev/llms/q-color-scheme-color.md): Learn how to use CSS variables resolver to change color value depending on the color scheme
-- [How can I change input focus styles?](https://mantine.dev/llms/q-input-focus-styles.md): Learn how to use Styles API with Mantine inputs
-- [How can I change Tabs border color?](https://mantine.dev/llms/q-tabs-border-color.md): Learn how to use Styles API with Tabs component
-- [How can I contribute to the library?](https://mantine.dev/llms/q-how-can-i-contribute.md): There are multiple ways to contribute even without writing code
-- [How can I disable all inputs/input groups inside a form?](https://mantine.dev/llms/q-disable-all-inputs-in-form.md): Learn how to disable all inputs/input groups inside a form with the unstyled Fieldset component
-- [How can I display different elements in light and dark color schemes?](https://mantine.dev/llms/q-light-dark-elements.md): Learn how to hide/show elements based on color scheme
-- [How can I focus the first input with error with use-form?](https://mantine.dev/llms/q-focus-first-input-with-error.md): Learn how to handle focus with use-form hook
-- [How can I get current color scheme value in JavaScript?](https://mantine.dev/llms/q-how-to-get-color-scheme-value-in-js.md): How to use useMantineColorScheme and useComputedColorScheme hooks to get current color scheme value in JavaScript
-- [How can I lint CSS files?](https://mantine.dev/llms/q-how-to-setup-stylelint.md): Learn how to set up Stylelint for Mantine postcss syntax
-- [How can I load fonts in Next.js?](https://mantine.dev/llms/q-next-load-fonts.md): A guide to load custom fonts in Next.js with CSS and next/font package
-- [How can I load fonts in React Router?](https://mantine.dev/llms/q-react-router-load-fonts.md): A guide to load custom fonts in React Router
-- [How can I load fonts in Vite?](https://mantine.dev/llms/q-vite-load-fonts.md): A guide to load custom fonts in Vite
-- [How can I lock scroll in my application?](https://mantine.dev/llms/q-how-to-lock-scroll.md): Use react-remove-scroll library to lock scroll in your application
-- [How can I submit a template to Mantine documentation?](https://mantine.dev/llms/q-submit-template.md): Learn how to create and submit a template to Mantine documentation
-- [How can I test Modal/Drawer/Popover components?](https://mantine.dev/llms/q-portals-testing.md): Learn how to use react-testing-library to test components that use portals and transitions.
-- [How can I test Select/MultiSelect components?](https://mantine.dev/llms/q-combobox-testing.md): Learn how to use react-testing-library to test Select and MultiSelect components.
-- [How can I upload files from Dropzone component?](https://mantine.dev/llms/q-dropzone-upload.md): Learn how to process files dropped into Dropzone component
-- [How is that thing done on the mantine.dev website?](https://mantine.dev/llms/q-how-that-thing-is-done.md): Learn how various elements are implemented on the mantine.dev website
-- [How to align input with a button in a flex container?](https://mantine.dev/llms/q-align-input-button.md): Learn how to align Mantine inputs with buttons using Group component
-- [How to call a function when Modal/Drawer closes and animation completes?](https://mantine.dev/llms/q-how-to-call-function-when-modal-closes.md): How to use transitionProps in Modal/Drawer components
-- [How to change background color for FiveM?](https://mantine.dev/llms/q-fivem-background-color.md): Unset body background color and color-scheme styles for FiveM
-- [How to change input placeholder color?](https://mantine.dev/llms/q-inputs-placeholder-color.md): Learn how to change placeholder color with Styles API
-- [How to integrate custom input with use-form hook?](https://mantine.dev/llms/q-custom-input-use-form.md): Learn how to add use-form support for custom inputs
-- [How to prevent Modal from closing?](https://mantine.dev/llms/q-how-to-prevent-modal-from-closing.md): Learn how to prevent Modal from closing when the user clicks outside of it or presses the Escape key
-- [How to scroll to the top of the form if the form is submitted with errors?](https://mantine.dev/llms/q-scroll-to-the-top-of-the-form.md): Learn how to call a function when the form is submitted with errors
-- [How to update Mantine dependencies?](https://mantine.dev/llms/q-how-to-update-dependencies.md): Learn how to update `@mantine/*`, `@mantinex/*` and `postcss-preset-mantine` dependencies manually or with ncu script
-- [How to use Dropzone with @mantine/form?](https://mantine.dev/llms/q-how-to-use-dropzone-with-form.md): Learn how to use Dropzone with @mantine/form to handle file selection state
-- [How to use Mantine template on GitHub?](https://mantine.dev/llms/q-templates-usage.md): Learn how to create a new repository based on Mantine template
-- [I get hydration warning about data-mantine-color-scheme attribute, what does it mean?](https://mantine.dev/llms/q-color-scheme-hydration-warning.md): Learn how hydration works and how to fix warnings
-- [Is there a comparison with other libraries?](https://mantine.dev/llms/q-other-libs.md): Comparison with other libraries is not provided, you are trusted to make your own decision based on documentation examples
-- [Is there a floating action button component?](https://mantine.dev/llms/q-floating-action-button.md): No, but you can build it with Affix and ActionIcon components
-- [Is there DataGrid component that I can use with Mantine?](https://mantine.dev/llms/q-data-grid-i-need.md): A list of community packages that provide DataGrid component that can be used with Mantine.
-- [It is not possible to pinch to zoom when a Modal is opened. What should I do?](https://mantine.dev/llms/q-pinch-to-zoom-modal.md): Use removeScrollProps to configure react-remove-scroll options
-- [MantineProvider was not found in component tree. What should I do?](https://mantine.dev/llms/q-mantine-provider-missing.md): Learn how to resolve MantineProvider issues
-- [My buttons are transparent and the background is visible only on hover, what is wrong?](https://mantine.dev/llms/q-transparent-buttons.md): You have installed a third-party library that overrides Mantine styles
-- [My Popover dropdown closes when I click on the dropdown of a nested Popover](https://mantine.dev/llms/q-nested-popover-closes.md): Popover dropdown is closed when it detects click-outside events
-- [My styles are broken with disabled JavaScript. What should I do?](https://mantine.dev/llms/q-disabled-js.md): Learn how to use Mantine without JavaScript enabled
-- [My styles are overridden by Mantine components styles, what should I do?](https://mantine.dev/llms/q-styles-order.md): Learn how to use CSS layers to control styles order and prevent Mantine components from overriding your styles
-- [Native browser validation does not work in some components, what should I do?](https://mantine.dev/llms/q-native-required.md): Learn why native browser validation does not work in some components
-- [The use-local-storage hook returns the real value only after mounting. Is it a bug?](https://mantine.dev/llms/q-local-storage-effect.md): Learn how Mantine retrieves local storage value
-- [What is the difference between searchable Select and Autocomplete?](https://mantine.dev/llms/q-select-autocomplete-difference.md): Searchable Select and Autocomplete are similar components, but they serve different purposes.
-- [Where can I find the roadmap?](https://mantine.dev/llms/q-roadmap.md): The roadmap is private and only available to the team.
-- [Why are my Carousel slides in vertical orientation?](https://mantine.dev/llms/q-carousel-missing-styles.md): You forgot to import carousel styles
-- [Why are my notifications displayed at the wrong position?](https://mantine.dev/llms/q-notifications-missing-styles.md): Because you did not import styles
-- [Why can I not use one polymorphic component in the component prop of another polymorphic component?](https://mantine.dev/llms/q-polymorphic-in-polymorphic.md): Learn how polymorphic components types work
-- [Why can I not use value/label data structure with Autocomplete/TagsInput?](https://mantine.dev/llms/q-autocomplete-value-label.md): Learn the difference between Autocomplete and Select components
-- [Why can VSCode not autoimport the Text component?](https://mantine.dev/llms/q-why-vscode-cannot-autoimport-text.md): It is confused by the native Text constructor
-- [Why do I see color scheme flickering on page load?](https://mantine.dev/llms/q-color-scheme-flickering.md): Color scheme flickering is caused by incorrect usage of ColorSchemeScript
-- [Why do my dates components look broken?](https://mantine.dev/llms/q-dates-missing-styles.md): Because you did not import styles
-- [Why does FileButton not work in Menu?](https://mantine.dev/llms/q-file-button-in-menu.md): Learn how to use FileButton in Menu component
-- [Why is it required to have 10 shades per color?](https://mantine.dev/llms/q-ten-shades-per-color.md): Learn how Mantine uses theme colors
-- [Why is my screen completely empty after I](https://mantine.dev/llms/q-notifications-empty-screen.md): You have used Notifications component incorrectly
-
-## Core
-
-- [Accordion](https://mantine.dev/llms/core-accordion.md): Divide content into collapsible sections
-- [ActionIcon](https://mantine.dev/llms/core-action-icon.md): Icon button
-- [Affix](https://mantine.dev/llms/core-affix.md): Renders children inside portal at fixed position
-- [Alert](https://mantine.dev/llms/core-alert.md): Attract user attention with important static message
-- [AlphaSlider](https://mantine.dev/llms/core-alpha-slider.md): Slider component for selecting alpha channel in color pickers (0 – 1)
-- [Anchor](https://mantine.dev/llms/core-anchor.md): Display link with theme styles
-- [AngleSlider](https://mantine.dev/llms/core-angle-slider.md): Pick angle value between 0 and 360
-- [AppShell](https://mantine.dev/llms/core-app-shell.md): Responsive shell for your application with header, navbar, aside and footer
-- [AspectRatio](https://mantine.dev/llms/core-aspect-ratio.md): Maintain responsive consistent width/height ratio
-- [Autocomplete](https://mantine.dev/llms/core-autocomplete.md): Autocomplete user input with any list of options
-- [Avatar](https://mantine.dev/llms/core-avatar.md): Display user profile image, initials or fallback icon
-- [BackgroundImage](https://mantine.dev/llms/core-background-image.md): Displays image as background
-- [Badge](https://mantine.dev/llms/core-badge.md): Display badge, pill or tag
-- [Blockquote](https://mantine.dev/llms/core-blockquote.md): Blockquote with optional cite
-- [Box](https://mantine.dev/llms/core-box.md): Base component for all Mantine components
-- [Breadcrumbs](https://mantine.dev/llms/core-breadcrumbs.md): Separates list of react nodes with given separator
-- [Burger](https://mantine.dev/llms/core-burger.md): Open/close navigation button
-- [Button](https://mantine.dev/llms/core-button.md): Button component to render button or link
-- [Card](https://mantine.dev/llms/core-card.md): Card with sections
-- [Cascader](https://mantine.dev/llms/core-cascader.md): Select a path from hierarchical data with cascading columns
-- [Center](https://mantine.dev/llms/core-center.md): Centers content vertically and horizontally
-- [Checkbox](https://mantine.dev/llms/core-checkbox.md): Capture boolean input from user
-- [Chip](https://mantine.dev/llms/core-chip.md): Pick one or multiple values with inline controls
-- [CloseButton](https://mantine.dev/llms/core-close-button.md): Button with close icon
-- [Code](https://mantine.dev/llms/core-code.md): Inline and block code
-- [Collapse](https://mantine.dev/llms/core-collapse.md): Animate presence with slide down/up transition
-- [ColorInput](https://mantine.dev/llms/core-color-input.md): Capture color from user
-- [ColorPicker](https://mantine.dev/llms/core-color-picker.md): Pick colors in hex(a), rgb(a), hsl(a) and hsv(a) formats
-- [ColorSwatch](https://mantine.dev/llms/core-color-swatch.md): Displays color
-- [Combobox](https://mantine.dev/llms/core-combobox.md): Create custom select, autocomplete or multiselect inputs
-- [ComboboxPopover](https://mantine.dev/llms/core-combobox-popover.md): Add combobox dropdown to any button element
-- [Container](https://mantine.dev/llms/core-container.md): Center content with padding and max-width
-- [CopyButton](https://mantine.dev/llms/core-copy-button.md): Copies given text to clipboard
-- [CorePackage](https://mantine.dev/llms/core-package.md)
-- [DataList](https://mantine.dev/llms/core-data-list.md): Display label-value pairs as a description list
-- [Dialog](https://mantine.dev/llms/core-dialog.md): Display a fixed overlay dialog at any side of the screen
-- [Divider](https://mantine.dev/llms/core-divider.md): Horizontal line with optional label or vertical divider
-- [Drawer](https://mantine.dev/llms/core-drawer.md): Display overlay area at any side of the screen
-- [EmptyState](https://mantine.dev/llms/core-empty-state.md): Display a placeholder for no data, empty results and first-run states
-- [Fieldset](https://mantine.dev/llms/core-fieldset.md): Group related elements in a form
-- [FileButton](https://mantine.dev/llms/core-file-button.md): Open file picker with a button click
-- [FileInput](https://mantine.dev/llms/core-file-input.md): Capture files from user
-- [Flex](https://mantine.dev/llms/core-flex.md): Compose elements in a flex container
-- [FloatingIndicator](https://mantine.dev/llms/core-floating-indicator.md): Display a floating indicator over a group of elements
-- [FloatingWindow](https://mantine.dev/llms/core-floating-window.md): Draggable floating area
-- [FocusTrap](https://mantine.dev/llms/core-focus-trap.md): Trap focus at child node
-- [Grid](https://mantine.dev/llms/core-grid.md): Responsive 12 columns grid system
-- [Group](https://mantine.dev/llms/core-group.md): Compose elements and components in a horizontal flex container
-- [Highlight](https://mantine.dev/llms/core-highlight.md): Highlight given part of a string with mark
-- [HoverCard](https://mantine.dev/llms/core-hover-card.md): Display popover section when target element is hovered
-- [HueSlider](https://mantine.dev/llms/core-hue-slider.md): Slider component for selecting hue channel in color pickers (0 – 360 degrees)
-- [Image](https://mantine.dev/llms/core-image.md): Image with optional fallback
-- [Indicator](https://mantine.dev/llms/core-indicator.md): Display element at the corner of another element
-- [Input](https://mantine.dev/llms/core-input.md): Base component to create custom inputs
-- [JsonInput](https://mantine.dev/llms/core-json-input.md): Capture json data from user
-- [Kbd](https://mantine.dev/llms/core-kbd.md): Display keyboard key
-- [List](https://mantine.dev/llms/core-list.md): Display ordered or unordered list
-- [Loader](https://mantine.dev/llms/core-loader.md): Indicate loading state
-- [LoadingOverlay](https://mantine.dev/llms/core-loading-overlay.md): An overlay with centered loader
-- [Mark](https://mantine.dev/llms/core-mark.md): Highlight part of the text
-- [Marquee](https://mantine.dev/llms/core-marquee.md): Create continuous scrolling animation for content
-- [MaskInput](https://mantine.dev/llms/core-mask-input.md): Input with mask pattern for formatted text entry
-- [Menu](https://mantine.dev/llms/core-menu.md): Combine a list of secondary actions into single interactive area
-- [Menubar](https://mantine.dev/llms/core-menubar.md): Desktop application style menubar with a row of menu triggers
-- [Modal](https://mantine.dev/llms/core-modal.md): An accessible overlay dialog
-- [MultiSelect](https://mantine.dev/llms/core-multi-select.md): Custom searchable multi select
-- [NativeSelect](https://mantine.dev/llms/core-native-select.md): Native select element based on Input
-- [NavLink](https://mantine.dev/llms/core-nav-link.md): Navigation link
-- [Notification](https://mantine.dev/llms/core-notification.md): Show dynamic notifications and alerts to user, part of notifications system
-- [NumberFormatter](https://mantine.dev/llms/core-number-formatter.md): Format number with thousands/decimal separators and suffix/prefix
-- [NumberInput](https://mantine.dev/llms/core-number-input.md): Capture number from user
-- [OverflowList](https://mantine.dev/llms/core-overflow-list.md): Hide items that do not fit in a container and display them as a single collapsed item
-- [Overlay](https://mantine.dev/llms/core-overlay.md): Overlays parent element with div element with any color and opacity
-- [Pagination](https://mantine.dev/llms/core-pagination.md): Display active page and navigate between multiple pages
-- [Paper](https://mantine.dev/llms/core-paper.md): Renders white or dark background depending on color scheme
-- [PasswordInput](https://mantine.dev/llms/core-password-input.md): Capture password data from user
-- [Pill](https://mantine.dev/llms/core-pill.md): Removable and non-removable tags
-- [PillsInput](https://mantine.dev/llms/core-pills-input.md): Base component for custom tags inputs and multi selects
-- [PinInput](https://mantine.dev/llms/core-pin-input.md): Capture pin code or one time password from the user
-- [Popover](https://mantine.dev/llms/core-popover.md): Display popover section relative to given target element
-- [Portal](https://mantine.dev/llms/core-portal.md): Renders component outside of parent element tree
-- [Progress](https://mantine.dev/llms/core-progress.md): Give user feedback for status of the task
-- [Radio](https://mantine.dev/llms/core-radio.md): Wrapper for input type radio
-- [RangeSlider](https://mantine.dev/llms/core-range-slider.md): RangeSlider component
-- [Rating](https://mantine.dev/llms/core-rating.md): Pick and display rating
-- [RingProgress](https://mantine.dev/llms/core-ring-progress.md): Give user feedback for status of the task with circle diagram
-- [RollingNumber](https://mantine.dev/llms/core-rolling-number.md): Animate value changes with rolling digits
-- [ScrollArea](https://mantine.dev/llms/core-scroll-area.md): Area with custom scrollbars
-- [Scroller](https://mantine.dev/llms/core-scroller.md): Horizontal scroll container with navigation controls
-- [SegmentedControl](https://mantine.dev/llms/core-segmented-control.md): A linear set of two or more segments
-- [Select](https://mantine.dev/llms/core-select.md): Custom searchable select
-- [SemiCircleProgress](https://mantine.dev/llms/core-semi-circle-progress.md): Represent progress with semi circle diagram
-- [SimpleGrid](https://mantine.dev/llms/core-simple-grid.md): Responsive grid in which each item takes equal amount of space
-- [Skeleton](https://mantine.dev/llms/core-skeleton.md): Indicate content loading state
-- [Slider](https://mantine.dev/llms/core-slider.md): Slider component
-- [Space](https://mantine.dev/llms/core-space.md): Add horizontal or vertical spacing from theme
-- [Splitter](https://mantine.dev/llms/core-splitter.md): Resizable split pane layout
-- [Spoiler](https://mantine.dev/llms/core-spoiler.md): Hide long sections of content under a spoiler
-- [Stack](https://mantine.dev/llms/core-stack.md): Compose elements and components in a vertical flex container
-- [Stepper](https://mantine.dev/llms/core-stepper.md): Display content divided into a steps sequence
-- [Switch](https://mantine.dev/llms/core-switch.md): Capture boolean input from user
-- [Table](https://mantine.dev/llms/core-table.md): Render table with theme styles
-- [TableOfContents](https://mantine.dev/llms/core-table-of-contents.md): Renders a list of headings on the page and tracks current heading visible in the viewport
-- [Tabs](https://mantine.dev/llms/core-tabs.md): Switch between different views
-- [TagsInput](https://mantine.dev/llms/core-tags-input.md): Capture a list of values from user with free input and suggestions
-- [Text](https://mantine.dev/llms/core-text.md): Display text
-- [Textarea](https://mantine.dev/llms/core-textarea.md): Autosize or regular textarea
-- [TextInput](https://mantine.dev/llms/core-text-input.md): Capture string input from user
-- [ThemeIcon](https://mantine.dev/llms/core-theme-icon.md): Render icon inside element with theme colors
-- [Timeline](https://mantine.dev/llms/core-timeline.md): Display list of events in chronological order
-- [Title](https://mantine.dev/llms/core-title.md): h1-h6 heading
-- [Tooltip](https://mantine.dev/llms/core-tooltip.md): Renders tooltip at given element on mouse over or other event
-- [Transition](https://mantine.dev/llms/core-transition.md): Animate presence of component with pre-made animations
-- [Tree](https://mantine.dev/llms/core-tree.md): Display a Tree structure
-- [TreeSelect](https://mantine.dev/llms/core-tree-select.md): Select with hierarchical tree data
-- [Typography](https://mantine.dev/llms/core-typography.md): Styles provider for html content
-- [UnstyledButton](https://mantine.dev/llms/core-unstyled-button.md): Unstyled polymorphic button
-- [VisuallyHidden](https://mantine.dev/llms/core-visually-hidden.md): Hide element visually but keep it accessible for screen readers
-
-## Hooks
-
-- [HooksPackage](https://mantine.dev/llms/hooks-package.md)
-- [use-element-size](https://mantine.dev/llms/hooks-use-element-size.md): Returns element width and height and observes changes with ResizeObserver
-- [useClickOutside](https://mantine.dev/llms/hooks-use-click-outside.md)
-- [useClipboard](https://mantine.dev/llms/hooks-use-clipboard.md)
-- [useCollapse](https://mantine.dev/llms/hooks-use-collapse.md)
-- [useColorScheme](https://mantine.dev/llms/hooks-use-color-scheme.md)
-- [useCounter](https://mantine.dev/llms/hooks-use-counter.md)
-- [useDebouncedCallback](https://mantine.dev/llms/hooks-use-debounced-callback.md)
-- [useDebouncedState](https://mantine.dev/llms/hooks-use-debounced-state.md)
-- [useDebouncedValue](https://mantine.dev/llms/hooks-use-debounced-value.md)
-- [useDidUpdate](https://mantine.dev/llms/hooks-use-did-update.md)
-- [useDisclosure](https://mantine.dev/llms/hooks-use-disclosure.md)
-- [useDocumentTitle](https://mantine.dev/llms/hooks-use-document-title.md)
-- [useDocumentVisibility](https://mantine.dev/llms/hooks-use-document-visibility.md)
-- [useDrag](https://mantine.dev/llms/hooks-use-drag.md)
-- [useEventListener](https://mantine.dev/llms/hooks-use-event-listener.md)
-- [useEyeDropper](https://mantine.dev/llms/hooks-use-eye-dropper.md)
-- [useFavicon](https://mantine.dev/llms/hooks-use-favicon.md)
-- [useFetch](https://mantine.dev/llms/hooks-use-fetch.md)
-- [useFileDialog](https://mantine.dev/llms/hooks-use-file-dialog.md)
-- [useFloatingWindow](https://mantine.dev/llms/hooks-use-floating-window.md)
-- [useFocusReturn](https://mantine.dev/llms/hooks-use-focus-return.md)
-- [useFocusTrap](https://mantine.dev/llms/hooks-use-focus-trap.md)
-- [useFocusWithin](https://mantine.dev/llms/hooks-use-focus-within.md)
-- [useForceUpdate](https://mantine.dev/llms/hooks-use-force-update.md)
-- [useFullscreen](https://mantine.dev/llms/hooks-use-fullscreen.md)
-- [useHash](https://mantine.dev/llms/hooks-use-hash.md)
-- [useHeadroom](https://mantine.dev/llms/hooks-use-headroom.md)
-- [useHotkeys](https://mantine.dev/llms/hooks-use-hotkeys.md)
-- [useHover](https://mantine.dev/llms/hooks-use-hover.md)
-- [useId](https://mantine.dev/llms/hooks-use-id.md)
-- [useIdle](https://mantine.dev/llms/hooks-use-idle.md)
-- [useInputState](https://mantine.dev/llms/hooks-use-input-state.md)
-- [useIntersection](https://mantine.dev/llms/hooks-use-intersection.md)
-- [useInterval](https://mantine.dev/llms/hooks-use-interval.md)
-- [useInViewport](https://mantine.dev/llms/hooks-use-in-viewport.md)
-- [useIsFirstRender](https://mantine.dev/llms/hooks-use-is-first-render.md)
-- [useIsomorphicEffect](https://mantine.dev/llms/hooks-use-isomorphic-effect.md)
-- [useListState](https://mantine.dev/llms/hooks-use-list-state.md)
-- [useLocalStorage](https://mantine.dev/llms/hooks-use-local-storage.md)
-- [useLogger](https://mantine.dev/llms/hooks-use-logger.md)
-- [useLongPress](https://mantine.dev/llms/hooks-use-long-press.md)
-- [useMap](https://mantine.dev/llms/hooks-use-map.md)
-- [useMask](https://mantine.dev/llms/hooks-use-mask.md)
-- [useMediaQuery](https://mantine.dev/llms/hooks-use-media-query.md)
-- [useMergedRef](https://mantine.dev/llms/hooks-use-merged-ref.md)
-- [useMounted](https://mantine.dev/llms/hooks-use-mounted.md)
-- [useMouse](https://mantine.dev/llms/hooks-use-mouse.md)
-- [useMove](https://mantine.dev/llms/hooks-use-move.md)
-- [useMutationObserver](https://mantine.dev/llms/hooks-use-mutation-observer.md)
-- [useNetwork](https://mantine.dev/llms/hooks-use-network.md)
-- [useOrientation](https://mantine.dev/llms/hooks-use-orientation.md)
-- [useOs](https://mantine.dev/llms/hooks-use-os.md)
-- [usePageLeave](https://mantine.dev/llms/hooks-use-page-leave.md)
-- [usePagination](https://mantine.dev/llms/hooks-use-pagination.md)
-- [usePrevious](https://mantine.dev/llms/hooks-use-previous.md)
-- [useQueue](https://mantine.dev/llms/hooks-use-queue.md)
-- [useRadialMove](https://mantine.dev/llms/hooks-use-radial-move.md)
-- [useReducedMotion](https://mantine.dev/llms/hooks-use-reduced-motion.md)
-- [useResizeObserver](https://mantine.dev/llms/hooks-use-resize-observer.md)
-- [useRovingIndex](https://mantine.dev/llms/hooks-use-roving-index.md)
-- [useScrollDirection](https://mantine.dev/llms/hooks-use-scroll-direction.md)
-- [useScroller](https://mantine.dev/llms/hooks-use-scroller.md)
-- [useScrollIntoView](https://mantine.dev/llms/hooks-use-scroll-into-view.md)
-- [useScrollSpy](https://mantine.dev/llms/hooks-use-scroll-spy.md)
-- [useSelection](https://mantine.dev/llms/hooks-use-selection.md)
-- [useSet](https://mantine.dev/llms/hooks-use-set.md)
-- [useSetState](https://mantine.dev/llms/hooks-use-set-state.md)
-- [useShallowEffect](https://mantine.dev/llms/hooks-use-shallow-effect.md)
-- [useSplitter](https://mantine.dev/llms/hooks-use-splitter.md)
-- [useStateHistory](https://mantine.dev/llms/hooks-use-state-history.md)
-- [useTextSelection](https://mantine.dev/llms/hooks-use-text-selection.md)
-- [useThrottledCallback](https://mantine.dev/llms/hooks-use-throttled-callback.md)
-- [useThrottledState](https://mantine.dev/llms/hooks-use-throttled-state.md)
-- [useThrottledValue](https://mantine.dev/llms/hooks-use-throttled-value.md)
-- [useTimeout](https://mantine.dev/llms/hooks-use-timeout.md)
-- [useToggle](https://mantine.dev/llms/hooks-use-toggle.md)
-- [useUncontrolled](https://mantine.dev/llms/hooks-use-uncontrolled.md)
-- [useValidatedState](https://mantine.dev/llms/hooks-use-validated-state.md)
-- [useViewportSize](https://mantine.dev/llms/hooks-use-viewport-size.md)
-- [useWindowEvent](https://mantine.dev/llms/hooks-use-window-event.md)
-- [useWindowScroll](https://mantine.dev/llms/hooks-use-window-scroll.md)
-
-## Form
-
-- [Form context](https://mantine.dev/llms/form-create-form-context.md): Add context support to use-form with createFormContext
-- [formActions](https://mantine.dev/llms/form-actions.md)
-- [formAllInputs](https://mantine.dev/llms/form-all-inputs.md)
-- [formErrors](https://mantine.dev/llms/form-errors.md)
-- [formGetInputProps](https://mantine.dev/llms/form-get-input-props.md)
-- [formNested](https://mantine.dev/llms/form-nested.md)
-- [FormPackage](https://mantine.dev/llms/form-package.md)
-- [formRecipes](https://mantine.dev/llms/form-recipes.md)
-- [formSchemaValidation](https://mantine.dev/llms/form-schema-validation.md)
-- [formStatus](https://mantine.dev/llms/form-status.md)
-- [formUncontrolled](https://mantine.dev/llms/form-uncontrolled.md)
-- [formValidation](https://mantine.dev/llms/form-validation.md)
-- [formValidators](https://mantine.dev/llms/form-validators.md)
-- [formValues](https://mantine.dev/llms/form-values.md)
-- [use-field](https://mantine.dev/llms/form-use-field.md): use-field hook – manage single field state
-- [use-form](https://mantine.dev/llms/form-use-form.md): Manage form state
-
-## Dates
-
-- [Calendar](https://mantine.dev/llms/dates-calendar.md): Base component for custom date pickers
-- [DateInput](https://mantine.dev/llms/dates-date-input.md): Free form date input
-- [DatePicker](https://mantine.dev/llms/dates-date-picker.md): Inline date, multiple dates and dates range picker
-- [DatePickerInput](https://mantine.dev/llms/dates-date-picker-input.md): Date, multiple dates and dates range picker input
-- [DateTimePicker](https://mantine.dev/llms/dates-date-time-picker.md): Capture datetime from the user
-- [GettingStartedDates](https://mantine.dev/llms/dates-getting-started.md)
-- [InlineDateTimePicker](https://mantine.dev/llms/dates-inline-date-time-picker.md): Inline date and time picker with range support
-- [MiniCalendar](https://mantine.dev/llms/dates-mini-calendar.md): Compact calendar to display a small number of days in a row
-- [MonthPicker](https://mantine.dev/llms/dates-month-picker.md): Inline month, multiple months and months range picker
-- [MonthPickerInput](https://mantine.dev/llms/dates-month-picker-input.md): Month, multiple months and months range picker input
-- [TimeGrid](https://mantine.dev/llms/dates-time-grid.md): Captures time value from the user with a predefined set of options
-- [TimeInput](https://mantine.dev/llms/dates-time-input.md): Capture time from the user
-- [TimePicker](https://mantine.dev/llms/dates-time-picker.md): Captures time value from the user
-- [TimeValue](https://mantine.dev/llms/dates-time-value.md): Display a formatted time value
-- [YearPicker](https://mantine.dev/llms/dates-year-picker.md): Inline year, multiple years and years range picker
-- [YearPickerInput](https://mantine.dev/llms/dates-year-picker-input.md): Inline year, multiple years and years range picker
-
-## Charts
-
-- [AreaChart](https://mantine.dev/llms/charts-area-chart.md): Area chart component with stacked, percent and split variants
-- [BarChart](https://mantine.dev/llms/charts-bar-chart.md): Bar chart component with stacked and percent variants
-- [BarsList](https://mantine.dev/llms/charts-bars-list.md): Display a list of bars with names and values
-- [BubbleChart](https://mantine.dev/llms/charts-bubble-chart.md): Bubble chart component
-- [BulletChart](https://mantine.dev/llms/charts-bullet-chart.md): Compact KPI chart with value, target, and qualitative ranges
-- [CompositeChart](https://mantine.dev/llms/charts-composite-chart.md): Composed chart with support for Area, Bar and Line charts
-- [DonutChart](https://mantine.dev/llms/charts-donut-chart.md): Donut chart component
-- [FunnelChart](https://mantine.dev/llms/charts-funnel-chart.md): Funnel chart component
-- [GettingStartedCharts](https://mantine.dev/llms/charts-getting-started.md)
-- [Heatmap](https://mantine.dev/llms/charts-heatmap.md): Heatmap chart component
-- [LineChart](https://mantine.dev/llms/charts-line-chart.md): Line chart component
-- [PieChart](https://mantine.dev/llms/charts-pie-chart.md): Pie chart component
-- [RadarChart](https://mantine.dev/llms/charts-radar-chart.md): Radar chart component
-- [RadialBarChart](https://mantine.dev/llms/charts-radial-bar-chart.md): Radial bar chart component
-- [SankeyChart](https://mantine.dev/llms/charts-sankey-chart.md): Sankey diagram component
-- [ScatterChart](https://mantine.dev/llms/charts-scatter-chart.md): Scatter chart component
-- [Sparkline](https://mantine.dev/llms/charts-sparkline.md): Simplified area chart to show trends
-- [SunburstChart](https://mantine.dev/llms/charts-sunburst-chart.md): Sunburst chart component for hierarchical data
-- [Treemap](https://mantine.dev/llms/charts-treemap.md): Treemap chart component
-
-## Schedule
-
-- [AgendaView](https://mantine.dev/llms/schedule-agenda-view.md): Vertical list view of events grouped by date
-- [DayView](https://mantine.dev/llms/schedule-day-view.md): Standalone schedule day view component
-- [GettingStartedSchedule](https://mantine.dev/llms/schedule-getting-started.md)
-- [MobileMonthView](https://mantine.dev/llms/schedule-mobile-month-view.md): Mobile-optimized schedule month view component
-- [MonthView](https://mantine.dev/llms/schedule-month-view.md): Standalone schedule month view component
-- [RecurringEventsSchedule](https://mantine.dev/llms/schedule-recurring-events.md)
-- [ResourcesDayView](https://mantine.dev/llms/schedule-resources-day-view.md): Day view with resource columns for scheduling across resources
-- [ResourcesMonthView](https://mantine.dev/llms/schedule-resources-month-view.md): Month view with resource lanes for scheduling across resources
-- [ResourcesSchedule](https://mantine.dev/llms/schedule-resources-schedule.md): Schedule wrapper component that combines resource day, week and month views
-- [ResourcesWeekView](https://mantine.dev/llms/schedule-resources-week-view.md): Week view with resource rows for scheduling across resources
-- [Schedule](https://mantine.dev/llms/schedule-schedule.md): Schedule component with day, week, month and year views
-- [ScheduleEventsData](https://mantine.dev/llms/schedule-events-data.md)
-- [WeekView](https://mantine.dev/llms/schedule-week-view.md): Standalone schedule week view component
-- [YearView](https://mantine.dev/llms/schedule-year-view.md): Standalone schedule year view component
-
-## Guides
-
-- [ControlledVsUncontrolled](https://mantine.dev/llms/guides-controlled-vs-uncontrolled.md)
-- [CustomComponents](https://mantine.dev/llms/guides-custom-components.md)
-- [EightToNine](https://mantine.dev/llms/guides-8x-to-9x.md)
-- [FunctionsReference](https://mantine.dev/llms/guides-functions-reference.md)
-- [Gatsby](https://mantine.dev/llms/guides-gatsby.md)
-- [Icons](https://mantine.dev/llms/guides-icons.md)
-- [JavaScript](https://mantine.dev/llms/guides-javascript.md)
-- [Jest](https://mantine.dev/llms/guides-jest.md)
-- [LLMDocumentation](https://mantine.dev/llms/guides-llms.md)
-- [NextJs](https://mantine.dev/llms/guides-next.md)
-- [Polymorphic](https://mantine.dev/llms/guides-polymorphic.md)
-- [ReactRouter](https://mantine.dev/llms/guides-react-router.md)
-- [Redwood](https://mantine.dev/llms/guides-redwood.md)
-- [SevenToEight](https://mantine.dev/llms/guides-7x-to-8x.md)
-- [SixToSeven](https://mantine.dev/llms/guides-6x-to-7x.md)
-- [Storybook](https://mantine.dev/llms/guides-storybook.md)
-- [Tiptap3Migration](https://mantine.dev/llms/guides-tiptap-3-migration.md)
-- [TypeScript](https://mantine.dev/llms/guides-typescript.md)
-- [Vite](https://mantine.dev/llms/guides-vite.md)
-- [Vitest](https://mantine.dev/llms/guides-vitest.md)
-
-## Theming
-
-- [Colors](https://mantine.dev/llms/theming-colors.md)
-- [ColorSchemes](https://mantine.dev/llms/theming-color-schemes.md)
-- [DefaultProps](https://mantine.dev/llms/theming-default-props.md)
-- [MantineProvider](https://mantine.dev/llms/theming-mantine-provider.md)
-- [ThemeObject](https://mantine.dev/llms/theming-theme-object.md)
-- [Typography](https://mantine.dev/llms/theming-typography.md): Styles provider for html content
-
-## Styles
-
-- [ColorFunctions](https://mantine.dev/llms/styles-color-functions.md)
-- [CSSFilesList](https://mantine.dev/llms/styles-css-files-list.md)
-- [CSSModules](https://mantine.dev/llms/styles-css-modules.md)
-- [CssVariables](https://mantine.dev/llms/styles-css-variables.md)
-- [CSSVariablesList](https://mantine.dev/llms/styles-css-variables-list.md)
-- [DataAttributes](https://mantine.dev/llms/styles-data-attributes.md)
-- [Emotion](https://mantine.dev/llms/styles-emotion.md)
-- [GlobalStyles](https://mantine.dev/llms/styles-global-styles.md)
-- [MantineStyles](https://mantine.dev/llms/styles-mantine-styles.md)
-- [PostCSSPreset](https://mantine.dev/llms/styles-postcss-preset.md)
-- [Rem](https://mantine.dev/llms/styles-rem.md)
-- [ResponsiveStyles](https://mantine.dev/llms/styles-responsive.md)
-- [Rtl](https://mantine.dev/llms/styles-rtl.md)
-- [StyleProp](https://mantine.dev/llms/styles-style.md)
-- [StyleProps](https://mantine.dev/llms/styles-style-props.md)
-- [StylesApi](https://mantine.dev/llms/styles-styles-api.md)
-- [StylesOverview](https://mantine.dev/llms/styles-styles-overview.md)
-- [StylesPerformance](https://mantine.dev/llms/styles-styles-performance.md)
-- [UnstyledComponents](https://mantine.dev/llms/styles-unstyled.md)
-- [UsageWithSass](https://mantine.dev/llms/styles-sass.md)
-- [VanillaExtract](https://mantine.dev/llms/styles-vanilla-extract.md)
-- [VariantsAndSizes](https://mantine.dev/llms/styles-variants-sizes.md)
-
-## X
-
-- [Carousel](https://mantine.dev/llms/x-carousel.md): Embla based carousel component
-- [CodeHighlight](https://mantine.dev/llms/x-code-highlight.md): Highlight code with shiki or highlight.js
-- [Dropzone](https://mantine.dev/llms/x-dropzone.md): Capture files from user with drag and drop
-- [ExtensionsPackage](https://mantine.dev/llms/x-extensions.md)
-- [Modals manager](https://mantine.dev/llms/x-modals.md): Centralized modals manager with option to handle state of multi-step modals
-- [NavigationProgress](https://mantine.dev/llms/x-nprogress.md): Navigation progress bar
-- [Notifications system](https://mantine.dev/llms/x-notifications.md): Mantine notifications system
-- [Rich text editor](https://mantine.dev/llms/x-tiptap.md): Tiptap based rich text editor
-- [Spotlight](https://mantine.dev/llms/x-spotlight.md): Command center for your application
-
-## Other
-
-- [About](https://mantine.dev/llms/about.md)
-- [AllReleases](https://mantine.dev/llms/changelog-all-releases.md)
-- [BrowserSupport](https://mantine.dev/llms/browser-support.md)
-- [Changelog700](https://mantine.dev/llms/changelog-7-0-0.md)
-- [Changelog710](https://mantine.dev/llms/changelog-7-1-0.md)
-- [Changelog7100](https://mantine.dev/llms/changelog-7-10-0.md)
-- [Changelog7110](https://mantine.dev/llms/changelog-7-11-0.md)
-- [Changelog7120](https://mantine.dev/llms/changelog-7-12-0.md)
-- [Changelog7130](https://mantine.dev/llms/changelog-7-13-0.md)
-- [Changelog7140](https://mantine.dev/llms/changelog-7-14-0.md)
-- [Changelog7150](https://mantine.dev/llms/changelog-7-15-0.md)
-- [Changelog7160](https://mantine.dev/llms/changelog-7-16-0.md)
-- [Changelog7170](https://mantine.dev/llms/changelog-7-17-0.md)
-- [Changelog720](https://mantine.dev/llms/changelog-7-2-0.md)
-- [Changelog730](https://mantine.dev/llms/changelog-7-3-0.md)
-- [Changelog740](https://mantine.dev/llms/changelog-7-4-0.md)
-- [Changelog750](https://mantine.dev/llms/changelog-7-5-0.md)
-- [Changelog760](https://mantine.dev/llms/changelog-7-6-0.md)
-- [Changelog770](https://mantine.dev/llms/changelog-7-7-0.md)
-- [Changelog780](https://mantine.dev/llms/changelog-7-8-0.md)
-- [Changelog790](https://mantine.dev/llms/changelog-7-9-0.md)
-- [Changelog800](https://mantine.dev/llms/changelog-8-0-0.md)
-- [Changelog810](https://mantine.dev/llms/changelog-8-1-0.md)
-- [Changelog820](https://mantine.dev/llms/changelog-8-2-0.md)
-- [Changelog830](https://mantine.dev/llms/changelog-8-3-0.md)
-- [Changelog900](https://mantine.dev/llms/changelog-9-0-0.md)
-- [Changelog910](https://mantine.dev/llms/changelog-9-1-0.md)
-- [Changelog920](https://mantine.dev/llms/changelog-9-2-0.md)
-- [Changelog930](https://mantine.dev/llms/changelog-9-3-0.md)
-- [Changelog940](https://mantine.dev/llms/changelog-9-4-0.md)
-- [Changelog950](https://mantine.dev/llms/changelog-9-5-0.md)
-- [Contribute](https://mantine.dev/llms/contribute.md)
-- [GettingStarted](https://mantine.dev/llms/getting-started.md)
-- [NotFound](https://mantine.dev/llms/404.md)
-- [OxcConfig](https://mantine.dev/llms/oxc-config-mantine.md)
-- [PreviousChangelogs](https://mantine.dev/llms/changelog-previous-versions.md)
-- [Support](https://mantine.dev/llms/support.md)

apps/docs/README.md

@@ -108,4 +108,5 @@ pnpm verify:search
 
 ## Contributing
 
-When making changes to the homarr codebase that affect user-facing behavior, **always update the corresponding documentation in this app**. See `.cursor/rules/documentation-sync.mdc` for the complete mapping of code changes to doc locations.
+When a Homarr change affects user-facing behavior, update the corresponding documentation in this app. See the
+[documentation-sync skill](../../.agents/skills/documentation-sync/SKILL.md) for the code-to-documentation mapping.

apps/docs/docs/advanced/command-line/development/index.mdx

@@ -1,43 +1,175 @@
 # Developer Docker CLI
 
-The host-side developer CLI builds and runs local Homarr images and pull-request previews. Run it directly from a checkout with `pnpm dev:cli -- ...`; no shell-specific setup script is required. It is separate from the recovery CLI included in production images.
+The host-side developer CLI builds and runs local Homarr images and pull-request previews with non-blocking background operations. Run it directly from a checkout with `pnpm dev:cli -- ...`; no shell-specific setup script is required. It is separate from the recovery CLI included in production images.
 
-To install an optional `homarr` binary, run `pnpm dev:cli:install` and make your Go bin directory available on `PATH`. GitHub CLI authentication is only needed for pull-request features.
+To install an optional `homarr` binary, run `pnpm dev:cli:install` and make your Go bin directory available on `PATH`. GitHub CLI authentication (`gh auth login`) is only needed for pull-request features.
 
-## Browse development images
+## Requirements
+
+- Docker or OrbStack
+- Go 1.25+ (when building the CLI from source)
+- GitHub CLI authenticated with `gh auth login` (for pull-request and CI features)
+- A [Nerd Font](https://www.nerdfonts.com/) enabled in your terminal (recommended for icons, status indicators, and TUI glyphs)
+
+## Interactive Development Browser
 
 ```bash
 pnpm dev:cli --
+# or with global binary:
+homarr
 ```
 
-The main screen combines local `homarr:*` images with open pull requests and their GHCR preview status. Select an image to start or stop it, use `R` to build a remote pull request locally in the background or rebuild a local image, or use `p` to force a remote preview pull. Press `d` to switch to the instance dashboard and `d` again to return without losing the browser state. The explicit `dev` and `dash` subcommands start on either screen.
+The main browser combines local `homarr:*` images with open pull requests and their GHCR preview status. Select an image to start or stop it, use `R` to build a remote pull request locally in the background or rebuild a local image, or use `p` to force a remote preview pull. Press `d` (or `1`/`2`) to toggle between the image browser and the instance dashboard.
 
-A locally built PR image is folded into its remote PR row only when its recorded revision exactly matches the current GitHub head SHA. The row is marked `◆ local`, and starting it prefers that local image without a registry pull. Outdated local builds remain separate rows. Navigation and dashboard switching remain available during background builds.
+A locally built PR image is folded into its remote PR row only when its recorded revision matches the current GitHub head SHA (marked `◆ local`). When the matching GHCR image is also available, pressing `Enter` opens a local/remote selector with local preselected. Outdated local builds remain separate rows.
 
-## Build images
+### Multi-Source Sidebar
+
+Press `Tab` to cycle between sidebar tabs:
+
+- **`[logs]`**: Live container output streams (press `f` to follow/pause, `L` to pin to the selected container, `Page Up`/`Page Down` to scroll).
+- **`[build]`**: Real-time BuildKit step streaming for active local builds.
+- **`[ci]`**: GitHub Actions CI check statuses, run duration, and workflow links for pull requests.
+
+### Background Task Overlay
+
+Pulls and builds run asynchronously in the background. Press `t` to open the tasks overlay, showing:
+
+- Layer-by-layer download progress and transfer speeds (via Docker Engine API).
+- Active build stages and logs.
+- Task cancellation and status.
+
+### Browser Shortcuts
+
+| Key                    | Action                                                                                        |
+| ---------------------- | --------------------------------------------------------------------------------------------- |
+| `/`                    | Filter rows by PR number, title, author, branch, CI, image, state, or port                    |
+| `↑` / `↓` or `j` / `k` | Navigate rows                                                                                 |
+| `Enter` or `Space`     | Start the available image; choose local or remote when both exist; stop if running            |
+| `R`                    | Build locally in background (or rebuild local image)                                          |
+| `p`                    | Pull remote PR image in background and start container                                        |
+| `m`                    | Manage mode (`b` rebuild, `i` delete image, `d` delete data, `c` remove container, `p` prune) |
+| `t`                    | Toggle background tasks overlay                                                               |
+| `Tab`                  | Cycle sidebar tabs (`[logs]`, `[build]`, `[ci]`)                                              |
+| `l` / `L`              | Toggle sidebar visibility / Pin logs to selected instance                                     |
+| `f`                    | Follow or pause logs                                                                          |
+| `M`                    | Toggle demo mode for next launch                                                              |
+| `b`                    | Toggle bot pull requests                                                                      |
+| `o` / `a`              | Open PR on GitHub / Open running instance in browser                                          |
+| `c`                    | Copy instance URL to clipboard                                                                |
+| `r`                    | Refresh data                                                                                  |
+| `1` / `2` / `d`        | Switch screen (development browser / instance dashboard)                                      |
+| `?` / `q`              | Help overlay / Quit (cancels active background tasks)                                         |
+
+## Instance Dashboard
 
 ```bash
-pnpm dev:cli -- build <name>
-pnpm dev:cli -- build --pr <number> [name]
+homarr dash
+# or
+pnpm dev:cli -- dash
 ```
 
-The first command builds the current checkout as `homarr:<name>`. The pull-request form uses a depth-one clone in a temporary directory and defaults to `homarr:pr-<number>` when `name` is omitted.
+The instance dashboard displays all running and stopped Homarr containers, published ports, health states, and resource volumes.
 
-## Rebuild images
+| Key                | Action                                   |
+| ------------------ | ---------------------------------------- |
+| `Enter` or `Space` | Start or stop selected instance          |
+| `s` / `S`          | Stop / Restart instance                  |
+| `x`                | Remove container (preserves data volume) |
+| `m`                | Manage mode for selected instance        |
+| `R`                | Rebuild from recorded build provenance   |
+
+## CLI Commands
+
+The commands below use the installed `homarr` binary. Without global installation, prefix each command with `pnpm dev:cli --` (for example, `pnpm dev:cli -- list`).
+
+### Launch Instances
 
 ```bash
-pnpm dev:cli -- rebuild <name>
+homarr run dev
+homarr run --detach dev
+homarr run --pr 6441
+homarr run --pr 6441 --demo
+homarr --pr 6441 --env WORKSHOP_WEB_URL=https://app-v2.preview.homarr.dev/
 ```
 
-Images built by this CLI record their source checkout, revision, and optional pull-request number. Rebuild uses that provenance to select the original checkout or create a fresh temporary pull-request checkout.
+- `--pr <number>`: Pull and run a PR image from GHCR (shorthand: `homarr --pr <number>`).
+- `--demo` (`-m`): Start with mock integrations and sample data.
+- `--detach`: Start container in background.
+- `--env` (`-e`): Pass additional environment variables (repeatable: `--env KEY=VALUE`).
 
-## Run images
+### Build & Rebuild
 
 ```bash
-homarr --pr <number> --env HOMARR_WEBSITE_URL=https://app-v2.preview.homarr.dev/
-homarr run <name>
-homarr run --pr <number>
+# Build current checkout as homarr:<name>
+homarr build feature
+
+# Build a pull request locally in a temporary checkout
+homarr build --pr 6441
+
+# Rebuild an existing image from recorded provenance
+homarr rebuild feature
 ```
 
-The direct `homarr --pr <number>` form is shorthand for `homarr run --pr <number>`. Add `--detach` to run in the
-background, `--demo` to enable demo data, or repeat `--env KEY=VALUE` to provide additional environment variables.
+Images built with the CLI record their source checkout, revision SHA, and optional PR number. `homarr rebuild` reads this provenance to reconstruct the build without manual configuration.
+
+### GitHub CI Checks
+
+```bash
+# View CI checks for a specific PR
+homarr ci 6441
+
+# View CI checks for the current branch
+homarr ci
+
+# Watch CI checks until completion
+homarr ci 6441 --watch
+```
+
+### Interactive Shell
+
+```bash
+# Open interactive shell in running container
+homarr shell homarr-dev
+
+# Run specific command in container
+homarr shell homarr-dev pnpm db:migration:sqlite:run
+```
+
+### Image & Volume Management
+
+```bash
+# List local images with build provenance (source, revision, PR)
+homarr images
+
+# Delete local image
+homarr images rm feature
+
+# List data volumes with owner PR/tag and in-use status
+homarr data
+
+# Delete data volume (safely stops and removes owning container first)
+homarr data rm homarr_feature_data
+
+# Remove stopped containers (prompts without --force)
+homarr prune --force
+```
+
+### Instance Operations & Diagnostics
+
+```bash
+# List instances in a script-friendly table
+homarr list
+
+# Follow container logs
+homarr logs homarr-dev
+
+# Stop, restart, remove, or open container in browser
+homarr stop homarr-dev
+homarr restart homarr-dev
+homarr remove homarr-dev
+homarr open homarr-dev
+
+# Verify Docker daemon, Engine API, GHCR access, and gh CLI authentication
+homarr doctor
+```

apps/docs/docs/advanced/command-line/index.mdx

@@ -1,27 +1,46 @@
 # Command line interface
 
-The Homarr image ships with a built-in recovery tool. This can be useful, if you do not have access to Homarr or if something is not working.
-Please note that the CLI is an _emergency tool_, not an API tool.
+The Homarr image includes a recovery CLI for operations that cannot be completed in the web interface. It is not an
+application API; use the [API](/docs/management/api) or [MCP endpoint](/docs/management/mcp) for automation.
 
-:::caution
+Back up the database and stop Homarr before running a command that changes data.
 
-Using the recovery CLi tool can cause problems when requests are being sent to Homarr while the tool is running. \
-You should also create a backup of the database, in case you break something.
+## Run the recovery CLI
 
-:::
+Open a shell in the container, then pass a command to `homarr`:
 
-## Execute CLI with Docker
+```sh
+docker exec -it <container-id> /bin/bash
+homarr <command>
+```
 
-1. Execute `docker ps | grep homarr` on the root system with Docker to find the container ID of your Homarr container.
-2. Run `docker exec -it <container-id> /bin/bash homarr <your-command-goes-here>`. \
-   Replace `<container-id>` with your container ID from step 1. \
-   Replace `<your-command-goes-here>` with the command you want to execute (see sub-pages).
+In QNAP Container Station, open the Homarr container's **Execute** action and select `/bin/bash`.
 
-## Execute CLI with QNAP
+See the pages in this section for available commands.
 
-1. Open Container Station in the QNAP Web Interface ![](img/334116069-e7ec4726-3df7-4dc6-a3e0-b745e7eef17f.png)
-2. Select Containers in the menu bar on the left ![](img/334116205-aa09ce40-0701-4f7d-b9f9-b431b9d207c5.png)
-3. Select your Homarr Container ![](img/334116303-714b5e07-b9de-4ec0-a2bc-def7ee38750f.png)
-4. Click "Execute" in the top right of the Window. ![](img/334116411-df1482f9-3aa9-4686-b77f-e0dca09e60b2.png)
-5. Select /bin/bash and click Execute ![](img/334116518-e1ddb515-99c7-4159-81bf-76e889d1e808.png)
-6. Run the Homarr command and press enter (eg. homarr reset-owner-password) ![](img/334116642-08c4f204-5cd0-4e4e-a785-0142e1b279ca.png)
+## Build a local branch harness
+
+The repository's host-side CLI can build the current checkout and run it as a named Docker harness:
+
+![Homarr developer CLI showing pull requests, local images, and PR CI status](./img/homarr-dev-cli.png)
+
+```sh
+pnpm cli harness setup feature-board
+```
+
+This creates `homarr:feature-board`, starts it with persistent demo data, and prints the assigned URL. Query the port
+again with:
+
+```sh
+pnpm cli harness port feature-board
+```
+
+Pass environment overrides with repeated `--env` options:
+
+```sh
+pnpm cli harness setup feature-board \
+  --env WORKSHOP_WEB_URL=https://example.test \
+  --env FEATURE_FLAG=true
+```
+
+Related commands are `harness build <name>`, `harness run <name>`, and `harness stop <name>`.

apps/docs/docs/advanced/development/getting-started.mdx

@@ -58,7 +58,7 @@ Use `pnpm docker:dev:up` instead when you only need Redis in the background. Run
 default data; use `pnpm db:seed` to seed it explicitly later.
 
 Workshop contributors can set up PocketBase and Docusaurus with the dedicated
-[Workshop development guide](../../workshop/development).
+[Workshop development guide](./workshop).
 
 ### Useful commands
 

apps/docs/docs/advanced/development/widgets-and-integrations.mdx

@@ -0,0 +1,102 @@
+---
+title: Widgets and integrations
+tags:
+  - Developer
+  - Technical documentation
+  - Widgets
+  - Integrations
+sidebar_position: 2
+---
+
+Homarr keeps feature registration explicit and typed. Feature registration has no generator or generated registry.
+A new feature is available when its typed metadata and lazy loader are registered.
+
+## Add a widget
+
+Keep the UI, options, helpers, and tests together in `packages/widgets/src/<widget>/`. The usual folder only needs an
+`index.ts` definition and a lazily imported `component.tsx`; complex widgets can add local files as needed.
+
+1. Add the stable kind to `packages/definitions/src/widget.ts` and its documentation slug to the direct typed map in
+   `packages/definitions/src/docs/widget-doc-slugs.ts`.
+2. Export `definition` and `componentLoader` from `packages/widgets/src/<widget>/index.ts` with
+   `createWidgetDefinition`. The local definition owns its icon, query keys, refresh interval, options, matchers, and
+   errors. Keep the component behind `withDynamicImport` so adding a widget does not load it on every dashboard.
+3. For an integration-backed widget, add its integration kinds and selection rules once to
+   `packages/definitions/src/widget-integration-map.ts`, then spread `getWidgetIntegrationConfig(kind)` into the local
+   definition. This server-safe config is also the API authorization boundary, avoiding a package cycle without
+   duplicating widget metadata.
+4. Register the widget in both explicit literal loader maps and the type-only module map in
+   `packages/widgets/src/registry.ts`, then add its icon to `packages/ui/src/widget-icons.ts`. The module and component
+   loaders must both use literal import paths. Keeping them separate lets a cold widget load request its definition
+   and component chunks in parallel; the type-only map preserves exact option and component inference. Keep all three
+   maps in the same order so drift is obvious in review.
+5. If the widget needs server data, add its tRPC router under `packages/api/src/router/widgets/` and add its explicit
+   lazy import to `packages/api/src/router/widgets/index.ts`. Keep upstream requests and Redis response caching in
+   `@homarr/request-handler`. Use the widget integration middleware for integration-backed procedures.
+6. Add canonical documentation in `apps/docs/docs/widgets/<slug>/`.
+
+Weather is the small integration-free example. Downloads shows integration selection, polling, server caching,
+mutations, partial upstream failures, and a larger options surface.
+
+## Add an integration
+
+Keep the HTTP client and its capability-specific types in `packages/integrations/src/<integration>/`.
+
+1. Add the typed definition to `packages/definitions/src/integration.ts`, including credential alternatives,
+   categories, documentation slug, ports, Docker aliases, and onboarding metadata when relevant.
+2. Add an explicit lazy creator to `packages/integrations/src/base/creator.ts`. The literal import keeps the
+   implementation out of the initial server bundle and makes the registration easy to find.
+3. Implement only the interfaces required by the widgets that use the service.
+4. Add canonical documentation in `apps/docs/docs/integrations/<slug>/`. Its `index.ts` must satisfy
+   `IntegrationDefinition` so invalid metadata fails type checking without widening the object. Use a type-only import
+   and `satisfies IntegrationDefinition`; do not cast the object.
+
+Beszel is a compact example with several widgets sharing one integration client.
+
+## Write user documentation
+
+Write for technically capable self-hosters. Keep each page short and operational.
+
+- Start with one sentence describing what the integration or widget adds to Homarr.
+- Include prerequisites, credentials, permissions, destructive actions, and non-obvious limits only when they matter.
+- Use numbered steps only when order matters. Prefer the exact UI labels a user must select.
+- Do not add marketing, implementation history, architecture internals, or explanations of basic self-hosting concepts.
+- End when the user can configure and verify the feature; do not repeat the same information in a summary.
+
+The usual page needs only an introduction and a `Configuration` section. Add `Notes` or `Troubleshooting` only for
+real caveats.
+
+## Data and errors
+
+- TanStack Query owns browser caching and refresh behavior. Redis owns shared server response caching for bounded key
+  spaces. Public handlers whose keys come from arbitrary URLs, domains, symbols, or coordinates stay in the bounded
+  process-local cache.
+- Cache raw service responses, never authorization decisions or decrypted credentials. Integration-backed cache keys
+  include keyed credential fingerprints and the complete integration identity, and are invalidated after mutations.
+  The fingerprints change with credentials without exposing their values in Redis keys.
+- Give upstream requests a finite deadline and pass the request handler's `AbortSignal` into clients that support it.
+  Admission is bounded per handler. Request deduplication and distributed lock ownership remain active until the
+  upstream settles or a bounded cleanup grace expires, while unresolved upstream work stays separately capped.
+- Keep validation and authorization on the server. Client-side checks improve UX but do not replace tRPC guards.
+- Use the shared logger with safe identifiers, operation names, duration, and the original error cause. Never log
+  secrets or full upstream payloads.
+- Multi-integration reads should return successful providers when one service fails and surface a clear error when all
+  providers fail.
+
+Registration files intentionally contain boring, explicit imports. This small amount of repetition preserves exact
+TypeScript inference, gives Next.js discoverable lazy chunks, and keeps Ctrl+click navigation reliable.
+
+## Registry imports
+
+Use `@homarr/widgets/manifest` to load registered widgets. `loadWidgetDefinition` is the metadata-only path;
+`loadWidgetComponent` loads only the UI module; and `loadWidgetResources` requests both paths in parallel. These
+loaders cache in-flight and successful promises and remove rejected promises so a later request can retry.
+
+The former root `widgetImports` and `loadWidgetDynamic` exports are intentionally not compatibility aliases.
+`widgetImports` synchronously imported every widget module, and `loadWidgetDynamic` depended on that eager map.
+Restoring them at the package root would defeat lazy definition chunks or add client-only runtime dependencies to
+every root consumer. Migrate metadata consumers to `loadWidgetDefinition`, renderers to `loadWidgetResources`, and
+type-only registry consumers from the removed internal `WidgetImportRecord` helper to the root `WidgetImports` type.
+
+`@homarr/widgets/catalog` remains as a deprecated compatibility subpath for `widgetCatalogIcons`. New imports should
+use `@homarr/ui/widget-icons`, which is the canonical server-safe icon catalog.

apps/docs/docs/advanced/development/workshop-operator.mdx

@@ -0,0 +1,67 @@
+---
+title: Workshop operator guide
+sidebar_label: Operator guide
+sidebar_position: 3
+tags:
+  - Workshop
+  - Deployment
+  - Environment variables
+  - PocketBase
+---
+
+# Workshop operator guide
+
+Workshop uses PocketBase. The production image serves the Workshop website and API from one origin and stores state in
+`/pb_data`.
+
+## Environment variables
+
+| Variable                               | Purpose                                      | Default                        |
+| -------------------------------------- | -------------------------------------------- | ------------------------------ |
+| `HOMARR_WEBSITE_URL`                   | Documentation/site base used by Homarr links | `https://homarr.dev`           |
+| `WORKSHOP_API_URL`                     | PocketBase API used by Homarr and docs       | `HOMARR_WEBSITE_URL`           |
+| `WORKSHOP_WEB_URL`                     | Public Workshop URL                          | `HOMARR_WEBSITE_URL/workshop`  |
+| `WORKSHOP_PUBLIC_ORIGIN`               | PocketBase-generated links and email         | Required in production         |
+| `PB_ALLOWED_ORIGINS`                   | Allowed browser origins                      | `*`                            |
+| `GITHUB_CLIENT_ID`                     | GitHub OAuth application ID                  | —                              |
+| `GITHUB_CLIENT_SECRET`                 | GitHub OAuth application secret              | —                              |
+| `OPENROUTER_API_KEY`                   | Enables the Homarr Assistant provider        | Provider disabled when empty   |
+| `HOMARR_AI_DAILY_REQUEST_LIMIT`        | Per-user daily request allowance             | `50`                           |
+| `HOMARR_AI_GLOBAL_DAILY_REQUEST_LIMIT` | Shared daily request ceiling                 | `10000`                        |
+| `HOMARR_AI_OPENROUTER_BASE_URL`        | OpenRouter-compatible upstream               | `https://openrouter.ai/api/v1` |
+| `HOMARR_AI_OPENROUTER_MODEL`           | Upstream model behind `homarr/model`         | Selected by the Homarr team    |
+
+Public URL variables accept HTTP(S) origins without embedded credentials, query strings, or fragments. Restart the
+container after changing runtime configuration.
+
+## Authentication and email
+
+Configure both GitHub OAuth variables and use `https://<workshop-host>/api/oauth2-redirect` as the callback. Supplying
+only one OAuth variable is a startup error. Configure SMTP for comment, report, and removal notifications.
+
+For the central community, `PB_ALLOWED_ORIGINS=*` permits requests from self-hosted Homarr origins. A private deployment
+can use a comma-separated allowlist.
+
+## Homarr provider
+
+`OPENROUTER_API_KEY` enables the [Homarr provider](/docs/workshop/homarr-provider). The Workshop server chooses the upstream model and
+enforces per-user and global daily limits. It requests zero-data-retention routing, disables data-collecting providers,
+and does not retain prompts or responses.
+
+Keep an OpenRouter account-level credit limit as the monetary backstop; request limits are not cost limits.
+
+## Deployment
+
+The v2 image is `ghcr.io/homarr-labs/workshop:v2`; immutable `sha-<commit>` tags are preferable for promotion. The
+service listens on port 8090.
+
+When using a reverse proxy, forward the complete hostname, including `/api`, `/_/`, and
+`/workshop-runtime-config.js`. Use a dedicated hostname when Homarr already occupies the intended origin.
+
+Verify `/api/health`, the Workshop page, a public listing request, GitHub sign-in, and one installation after deployment.
+
+## Backup and restore
+
+Stop writes and copy `/pb_data` for a consistent backup. A restore replaces the selected PocketBase data directory, so
+preserve the current volume and verify that the backup contains `data.db` first. Rehearse the restore outside production
+and verify sign-in and one installation afterward.

apps/docs/docs/advanced/development/workshop.mdx

@@ -0,0 +1,41 @@
+---
+title: Workshop development
+sidebar_position: 4
+tags:
+  - Workshop
+  - Developer
+  - Docusaurus
+  - PocketBase
+---
+
+# Workshop development
+
+See the [main development guide](./getting-started) for repository prerequisites.
+
+Start PocketBase:
+
+```sh
+cp apps/workshop/.env.example apps/workshop/.env
+docker compose --env-file apps/workshop/.env -f apps/workshop/docker-compose.yml up --build workshop
+```
+
+Start Docusaurus in another terminal:
+
+```sh
+WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
+```
+
+PocketBase runs at `http://127.0.0.1:8090`; create the first superuser under `/_/`. Workshop is available at
+`http://127.0.0.1:3003/workshop`.
+
+To connect a local Homarr instance, set:
+
+```dotenv
+HOMARR_WEBSITE_URL=http://127.0.0.1:3003
+WORKSHOP_API_URL=http://127.0.0.1:8090
+WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
+```
+
+Restart the affected development process after changing these variables. See
+[`apps/workshop/README.md`](https://github.com/homarr-labs/homarr/blob/HEAD/apps/workshop/README.md) for OAuth,
+moderation, tests, and service maintenance.

apps/docs/docs/advanced/environment-variables/index.mdx

@@ -38,7 +38,27 @@ Using the `PUID` and `PGID` will require you to set the correct permissions on t
 | `WORKSHOP_WEB_URL`       | Public Workshop website used by links in Homarr, Custom Widgets, onboarding, and assistant context.                                                                                                                                    | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
 
 Workshop service operators can find its server-only configuration in the
-[Workshop operator guide](../../workshop/operator#environment-variables).
+[Workshop operator guide](/docs/advanced/development/workshop-operator#environment-variables).
+
+### Workshop service
+
+These variables configure the separate Workshop service, not the Homarr application container.
+
+| Environment Variable                        | Description                                                               | Default                           |
+| ------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------- |
+| `WORKSHOP_PUBLIC_ORIGIN`                    | Public origin used in PocketBase links and email                          | Required in production            |
+| `PB_ALLOWED_ORIGINS`                        | Browser origins allowed to call PocketBase                                | `*` for the public community      |
+| `WORKSHOP_IMAGE`                            | Workshop image used by the staging Compose file                           | `ghcr.io/homarr-labs/workshop:v2` |
+| `WORKSHOP_EXPOSE_PORT`                      | Host port for the combined staging service                                | `8090`                            |
+| `PB_EXPOSE_PORT`                            | Host port for local PocketBase development                                | `8090`                            |
+| `DOCS_EXPOSE_PORT`                          | Host port for local documentation development                             | `3003`                            |
+| `GITHUB_CLIENT_ID` / `GITHUB_CLIENT_SECRET` | Optional GitHub OAuth application credentials                             | -                                 |
+| `OPENROUTER_API_KEY`                        | Server-only upstream key that enables the Homarr Assistant provider       | Provider disabled                 |
+| `HOMARR_AI_DAILY_REQUEST_LIMIT`             | Daily Assistant request units per user                                    | `50`                              |
+| `HOMARR_AI_GLOBAL_DAILY_REQUEST_LIMIT`      | Daily Assistant request units shared by all users                         | `10000`                           |
+| `HOMARR_AI_OPENROUTER_BASE_URL`             | OpenRouter-compatible provider endpoint                                   | `https://openrouter.ai/api/v1`    |
+| `HOMARR_AI_OPENROUTER_MODEL`                | Upstream model exposed through the stable `homarr/model` alias            | Selected by the Homarr team       |
+| `HOMARR_AI_ALLOW_INSECURE_UPSTREAM`         | Allows an HTTP upstream for local provider tests; never use in production | `false`                           |
 
 ## Authentication
 
@@ -58,12 +78,12 @@ A random secret can be generated by using the following command: `openssl rand -
 
 ## Docker
 
-| Environment Variable  | Description                                                                                                                                                                                               | Possible values                                         | Default |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------- |
-| `DOCKER_ENDPOINTS`    | JSON array of named, capability-scoped Docker or Podman endpoints. Supports socket, explicitly insecure TCP, and TLS transports. See the [Docker and Podman integration guide](/docs/integrations/docker) | A JSON array of endpoint descriptors                    | -       |
-| `DOCKER_HOSTNAMES`    | Legacy comma-separated list of plaintext TCP hostnames. Ignored when `DOCKER_ENDPOINTS` is set                                                                                                            | For example `localhost,docker.example.com`              | -       |
-| `DOCKER_PORTS`        | Legacy comma-separated list of plaintext TCP ports. Ignored when `DOCKER_ENDPOINTS` is set                                                                                                                | For example `2375,2376`                                 | -       |
-| `DOCKER_SOCKET_PATHS` | Legacy comma-separated list of mounted Docker-compatible socket paths. Ignored when `DOCKER_ENDPOINTS` is set                                                                                             | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
+| Environment Variable  | Description                                                                                                                                                                                                          | Possible values                                         | Default |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------- |
+| `DOCKER_SOCKET_PATHS` | Comma-separated mounted Docker-compatible socket paths. Homarr discovers each path as a selectable Docker environment                                                                                                | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
+| `DOCKER_HOSTNAMES`    | Comma-separated plaintext TCP hostnames. Pair each hostname with the port in the same position in `DOCKER_PORTS`                                                                                                     | For example `localhost,docker.example.com`              | -       |
+| `DOCKER_PORTS`        | Comma-separated plaintext TCP ports paired with `DOCKER_HOSTNAMES`                                                                                                                                                   | For example `2375,2376`                                 | -       |
+| `DOCKER_ENDPOINTS`    | Optional advanced JSON configuration for custom names, TLS, or restricted capabilities. It takes precedence over the simple variables above. See the [Docker and Podman connection guide](/docs/integrations/docker) | A JSON array of endpoint descriptors                    | -       |
 
 ## Database
 

apps/docs/docs/advanced/keyboard-shortcuts/index.mdx

@@ -6,19 +6,34 @@ tags:
 
 Homarr has the following keyboard shortcuts:
 
-| Shortcut                                        | Description                                                                                                                |
-| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| `MOD` + `K`                                     | Opens the search bar                                                                                                       |
-| `MOD` + `J`                                     | Toggles Dark Mode                                                                                                          |
-| `MOD` + `E`                                     | Toggles Edit Mode                                                                                                          |
-| Hold `Shift` for 500 ms over a supported widget | Opens its temporary advanced view                                                                                          |
-| `Shift` + `Enter` on a supported widget         | Opens its advanced view until it is closed                                                                                 |
-| `Esc`                                           | Stops keyboard tile editing, cancels an active pointer or touch move/resize, or closes an open advanced view or board menu |
+| Shortcut                                            | Description                                                                                                                |
+| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `MOD` + `K`                                         | Opens search, including local apps, boards, integrations, pages, commands, and preferences                                 |
+| `MOD` + `P`                                         | Opens app search                                                                                                           |
+| `MOD` + `/`                                         | Opens Homarr Assistant inside search                                                                                       |
+| `MOD` + `Shift` + `/` (`MOD` + `?`)                 | Opens preference search                                                                                                    |
+| `Shift` + `A`                                       | Opens the full Homarr Assistant                                                                                            |
+| `MOD` + `J`                                         | Toggles Dark Mode                                                                                                          |
+| `MOD` + `E`                                         | Toggles Edit Mode                                                                                                          |
+| Hold `Shift` for 500 ms over a supported widget     | Opens its temporary advanced view                                                                                          |
+| Hold `Shift` + `Ctrl`/`Cmd` over a supported widget | Keeps its advanced view open until it is closed                                                                            |
+| `Esc`                                               | Stops keyboard tile editing, cancels an active pointer or touch move/resize, or closes an open advanced view or board menu |
+
+## Search and commands
+
+Search is designed as the fastest route to Homarr. Start typing after `MOD` + `K` to find local apps, boards,
+integrations, pages, commands, and preferences without entering a separate mode first. Local Homarr results appear
+before configured search-engine actions and Assistant fallbacks. Commands include opening the board switcher without
+leaving the keyboard. Type `!` to enter Web mode when you want to browse configured engine shortcuts or discover
+DuckDuckGo bangs; bang discovery is excluded from ordinary Search results.
+
+Use the dedicated shortcuts above to start in apps, Assistant, or preferences. Inside search, choose a mode to narrow
+the same query when needed. Media request search is available only when a supported Seerr integration is configured.
 
 ## Widget advanced view
 
-Supported widgets open a temporary advanced view when you hold `Shift` over them for 500 ms. Focus a widget and press
-`Shift` + `Enter`, or use its menu, to keep the advanced view open.
+Supported widgets open a temporary advanced view when you hold `Shift` over them for 500 ms. Hold `Shift` plus `Ctrl`
+on Windows/Linux or `Cmd` on macOS over the widget to keep the advanced view open, or use its menu.
 
 ## Board editing
 

apps/docs/docs/advanced/proxy/index.mdx

@@ -143,7 +143,7 @@ networks:
 ```
 
 :::important
-Homarr needs to be on the same network so you will need to add the following property to your homarr install:
+Homarr and Caddy must share the same Docker network:
 
 ```yaml
 homarr:

apps/docs/docs/advanced/styling/index.mdx

@@ -1,102 +1,37 @@
 # Styling
 
-:::tip
+Homarr uses Mantine and supports custom CSS at two scopes:
 
-This page is directed at more experienced users with knowledge about CSS and browsers.
-We recommend you to [look into the board customizations instead](/docs/management/boards#appearance),
-if you do not have experience with writing custom styles or CSS.
+- **Global:** **Management → Settings → Instance branding → Custom CSS**.
+- **Board:** **Board settings → Custom CSS**. Board CSS loads after the global stylesheet and can override it.
 
-:::
+Both editors accept direct CSS and Workshop imports.
 
 :::warning
 
-Our support specifically excludes custom CSS, and we will not help you to write CSS.
-However, we may help you by adding new CSS classes if required.
+Custom CSS can break after updates and is not an authorization boundary. Hidden controls remain accessible to users who
+have permission to use them.
 
 :::
 
-Homarr uses https://mantine.dev/ under the hood. You can change the look & feel of Homarr
-using custom CSS, that extends or overwrites the styles from Mantine.
+## Target elements
 
-## Getting into CSS
+Use browser developer tools to inspect the element and test a selector. Prefer stable semantic or Mantine class names;
+avoid generated classes such as `mantine-Card-x2fske`, which change between builds.
 
-If you don't have any experience with CSS,
-we strongly recommend you to go through the courses here: https://www.w3schools.com/css/.
-Due to the infinite scenarios and setups possible with custom CSS,
-our support team will not provide any support with your own written CSS.
+To target one widget, add a custom class under **Edit item → Advanced options** and use that class in the board CSS.
 
-## Limitations and dangers
+Use `!important` only when the existing cascade requires it.
 
-When using custom CSS, you can break the page or certain functionalities.
-Although CSS can improve the design & feel of the page, it **<ins>cannot do any of the following</ins>**:
+## Theme variables
 
-- Implement new features, widgets or integrations
-- Securely hide elements you don't want users to interact / have permission to
-- Completely revamp the design of the page, only smaller changes are possible
-
-Here are some dangers of using custom CSS:
-
-- Updates may contain breaking changes in the structure, built-in styling or how styling is processed. Therefore,
-  custom CSS may break unexpectedly without any warning
-- Custom CSS may make certain elements invisible or not possible to click / interact with
-- Custom CSS could make readability and accessibility worse for impaired people
-
-## How to inspect the page
-
-When styling the page, you can use the `Inspector` to inspect elements on the page and try out styles.
-This may vary depending on your browser and operating system, but the workflow usually goes like this:
-
-- Open the Homarr page
-- Press `Ctrl` + `Shift` + `I` at the same time.
-  Alternatively, right-click on the page and choose `Inspect` or `Inspect element`.
-- Open the tab `Elements` if it isn't open yet.
-- Search the element you want to change in the DOM tree or use the element picker (usually at the top left)
-  to select it by clicking on the page.
-- Experiment by changing the CSS code on the right side
-
-When writing custom CSS, it is important to also remember or create a selector, which tells the browser
-which element to apply the styles to. If you accidentally broke something or want to revert your changes in the inspector,
-simply reload the page.
-
-## Using Homarr's classes
-
-Homarr's elements will already have a lot of classes and styles pre-applied.
-You can reuse those classes to apply additional styles or overwrite them.
-When overwriting, remember to add the `!important` flag to your CSS property to tell the browser to use our instruction instead.
-
-Classes with random number suffixes, such as `mantine-Card-x2fske`, should be avoided, since those are dynamic
-CSS classes that will change with every build. This means, every time you update Homarr,
-your styles will no longer apply to them
-
-## Defining custom classes for widgets
-
-If you want to apply the styles only for one widget, you can define custom class names only for that widget.
-To do that, enter edit mode on your board, click the three dots of your widget, click `Edit item` and click `Advanced options`.
-Then, you can enter as many custom classes as you'd like:
-
-![](./img/widget-custom-classes.png)
-
-To save them, click `Save changes` on both modals and exit edit mode.
-
-## Where to enter custom CSS
-
-After you wrote your custom CSS, it is time to permanently save it, so you don't need to use the inspector anymore.
-To do this, enter the board settings:
-
-![](./img/enter-board-settings.png)
-
-Scroll to the **Custom CSS** section on the board settings page. It is part of the unified settings form; enter your CSS
-there and save the board settings to apply it to that board.
-
-![](./img/custom-css-setting.png)
-
-## Using variables
-
-You can also change the values of the theme variables, which are located here: https://mantine.dev/styles/css-variables-list/.
-To do this, see the following example CSS:
+Mantine exposes [CSS variables](https://mantine.dev/styles/css-variables-list/) that can be overridden globally or per
+board:
 
 ```css
 :root {
   --mantine-primary-color-filled: #ffbb00;
 }
 ```
+
+CSS changes presentation only; use widgets, integrations, permissions, or application code for behavior.

apps/docs/docs/community/donate.mdx

@@ -8,22 +8,7 @@ tags:
 
 # Donate
 
-## Why to donate
+Donations fund Homarr's development infrastructure and community services.
 
-Our team of 4 developers is working on Homarr in their free time.
-Homarr has become a big part of our daily things we work on - and therefore we invest a lot of time into maintaining Homarr,
-providing support and implementing new features.
-We also incur monetary costs while developing Homarr for the tools that we need.
-A few examples include:
-
-- Renting for a Cloud VPS for our cloud services (status page, monitoring, email, analytics, [demo instance](https://demo.homarr.dev/), ...)
-- Paying for (IDE-) licenses
-
-Using a donation, you help us to cover these expenses and enable the development of Homarr.
-Homarr is completely free to use. We'd highly appreciate if you consider donating, especially if you use Homarr in a commercial environment.
-
-## Where to donate
-
-We accept donations on our official [OpenCollective](https://opencollective.com/homarr).
-You may also sponsor us directly by providing a useful service / product to us other means.
-You can get into contact with us [here](/docs/community/get-in-touch).
+Support the project through [OpenCollective](https://opencollective.com/homarr). For sponsorships or donated services,
+use the private contact listed on [Get in touch](/docs/community/get-in-touch).

apps/docs/docs/community/faq.mdx

@@ -5,106 +5,46 @@ tags:
   - Help
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
+### Can Homarr run on a Raspberry Pi?
 
-### Can I install Homarr on a Raspberry Pi?
+Yes, when the device uses a supported `linux/arm64` operating system. `linux/arm/v7` is not supported. See
+[Prerequisites](/docs/getting-started).
 
-Yes, Homarr is compatible with the architecture of the Raspberry Pi. Have a look in our <a href="/docs/category/installation-1">installation guide</a> on how to do so.
+### Can I use custom app icons?
 
-### I have a suggestion / idea for improvement or want to report a bug
+Yes. Use a direct image URL, one of Homarr's icon sources, or upload an image. See [Icons](/docs/advanced/icons).
 
-You can report issues, suggestions, or ideas for improvements <a href="https://github.com/homarr-labs/homarr/issues/new/choose">here</a>.
+### Can I create widgets?
 
-### Can I use my own custom icons for apps?
+Yes. [Custom Widgets](/docs/management/custom-widgets) use server-side API requests and safe JSX. They can be written in
+the workbench or created with an MCP-connected agent.
 
-Yes, check out our guide on <a href="/docs/advanced/customizations/icons">how to add your custom icons</a>.
+### Can Homarr be exposed to the internet?
 
-### Some of my online icons are not working (anymore)
+Homarr supports authenticated and public deployments. Terminate HTTPS at a reverse proxy, keep Homarr updated, and grant
+public board access only when anonymous viewing is intended. See [Board access control](/docs/management/boards#access-control)
+and [Single sign-on](/docs/advanced/single-sign-on).
 
-It seems the `cdn.jsdelivr.net` database of icon sometimes appear in the lists for DNS-Holes (PiHole, AdGuard Home...). <br />
-So make sure to manually whitelist this address.
+### Where are the logs?
 
-### Can I add my own widgets? Do I need programming skills?
+Use **Management → Tools → Logs** for retained and live application logs. Container startup failures and older events are
+available through the deployment platform, for example `docker container logs homarr`.
 
-Yes. A [Custom Widget](/docs/management/custom-widgets) can read a public or private HTTP API.
+Use the browser developer console only for client-side failures. Review logs before sharing them because URLs and other
+deployment details may be present.
 
-It can show responsive Mantine JSX. It can also use widget options and actions with board permission checks.
+### Why can Homarr not reach a service behind Gluetun?
 
-Custom JSX v2 is the only Custom Widget format. Write the JSON and JSX in the workbench.
+Gluetun's firewall blocks traffic that is not explicitly allowed. Configure its
+[`FIREWALL_OUTBOUND_SUBNETS`](https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md) for the relevant
+LAN or Docker subnet, and use an address reachable from the Homarr container.
 
-You can also use the AI copy prompt. An MCP agent can validate and preview a definition before it saves the definition.
+### Where do I report a bug or request a feature?
 
-The workbench reads a pasted AI response. It shows request capabilities and redacted diagnostics.
+Use the [GitHub issue templates](https://github.com/homarr-labs/homarr/issues/new/choose). For community support, see
+[Get in touch](/docs/community/get-in-touch).
 
-A template cannot import packages or run arbitrary JavaScript. It cannot call browser `fetch`.
+### Can Homarr be used commercially?
 
-Named requests use the Homarr server. The server applies board permissions and the network policy.
-
-Before installation, examine the origins, methods, permissions, and actions. Use the same review before publication.
-
-### Is it secure to expose Homarr to the web?
-
-Yes, since v0.14.0, we are confident that Homarr is secure enough to be exposed to the web.
-Make sure to enable the "allow anonymous access" [option in the settings](/docs/management/boards#access-control), if you want to allow people without an account to be able to see your dashboard (not edit)
-
-### How do I open the console / log?
-
-There are two different sources of information:
-
-- console: This is your client (browser). It can tell us, if there is an issue on the client (crash, bug, ...).
-- log: This is your server. It will tell us, if there are issues with connections for the integrations, crashes and errors.
-
-Both variants _can_ contain personal data. It's recommended, that you don't post them publicly or remove personal data from it.
-
-<Tabs>
-  <TabItem value="apple" label="Read console" default>
-
-> Note: This will not work on most mobile browsers.
-
-Open your browser and ensure, that Homarr is your current tab.
-Press `CTRL` + `SHIFT` + `I` on your keyboard. If this shortcut doesn't work, please use one of the alternatives: https://developer.chrome.com/docs/devtools/open/.
-Click on `Console` in the new window, that opened. There, you should see white, orange and sometimes red messages. You can use the Windows Snip & Sketch tool (or your respective tool on Linux / MacOS) to screenshot those messages.
-
-> Please never execute any commands in the console. Scammers are using the console to let you execute harmful commands. If you want to resolve an issue in Homarr, **you'll never have to execute any commands here**
-
-  </TabItem>
-  <TabItem value="orange" label="Read log">
-
-This depends on your installation method. If you use Unraid, you can simply click on the App and on `Log`. If you have a bare Docker install, use `docker container logs homarr`. If you used a different name than `homarr` for your container, you need to replace said argument. Here is some additional information about the command: https://geekflare.com/check-docker-logs/.
-
-  </TabItem>
-</Tabs>
-
-### How do I post logs?
-
-Please check [the section above](#how-do-i-open-the-console--log), on how to obtain logs. Logs should always be posted to https://pastebin.com/ or https://rentry.co/.
-
-### Can I use Homarr at my company?
-
-Yes, you can! But please consider a donation, if our work has been useful to you.
-
-### I think I found a bug. What can I do?
-
-If you think, that you found a bug, please create an issue <a href="https://github.com/homarr-labs/homarr/issues/new/choose">here</a>.
-
-### Why can't I use my custom icons?
-
-You need to restart the Homarr Docker container after adding icons.
-
-### Why can't homarr see/ping containers running locally behind GluetunVPN?
-
-This is because GluetunVPN, and many other docker VPN services, secure their VPN connections with strict firewalls. These firewalls often block access to local containers, even on the same docker network. The workaround for <a href="https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md">GluetunVPN</a> is to add "- FIREWALL_OUTBOUND_SUBNETS=192.168.1.0/24" into the environmental variables of the docker compose file. If you are using a firewall on your system, you will need to add a rule that allows requests from ip's in the range of 192.168.xxx.xxx . If you are using UFW the command would be "sudo ufw allow from 192.168.0.0/16".
-Tip: If you are running your torrent client behind a VPN, and running Sonarr (or something similar) normally, make sure to open your torrent client's port in your firewall. If you don't, Sonarr will not be able to see it. Furthermore, use your machines IP (192.168.x.x) rather then 127.0.0.1 or localhost.
-
-### Can I get in touch with you?
-
-Yes, go <a href="/docs/community/get-in-touch">here</a> to get with us in touch.
-
-<hr />
-
-:::tip
-
-Haven't found the solution to your problem / question? We are eager to help you on [our Discord](/docs/community/get-in-touch#discord) or in a [GitHub Issue](https://github.com/homarr-labs/homarr/issues/new/choose).
-
-:::
+Yes. Homarr is licensed under the [Apache License 2.0](/docs/community/license). Commercial users can support development
+through [OpenCollective](/docs/community/donate).

apps/docs/docs/community/get-in-touch.mdx

@@ -1,24 +1,23 @@
 ---
-title: Get In Touch
-description: Still have a question? Click here!
+title: Get in touch
+description: Community, support, and private contact channels.
 tags:
   - Help
   - Community
 ---
 
-We're happy to talk with you! Shoot us a message at the following places:
+# Get in touch
 
-## E-Mail
+## GitHub
 
-We are open to discuss sponsorships, security vulnerabilities and other private requests through our email.
-Please do not report any bugs / feature requests here - they will be ignored and deleted.
-
-[homarr-labs@proton.me](mailto:homarr-labs@proton.me)
+Use the [issue templates](https://github.com/homarr-labs/homarr/issues/new/choose) for bugs and feature requests.
 
 ## Discord
 
-We have a Discord Server, where we announce new releases, discuss features and bugs and show off our dashboards.
-There are over 4'000 members and we're happy to answer your questions or concerns.
-You're also open to discuss new / upcoming features and any offtopic selfhosting content.
+Use the [Homarr Discord server](https://discord.gg/aCsmEV5RgA) for community support, release discussion, and dashboard
+showcases.
 
-[_![](https://discordapp.com/api/guilds/972958686051962910/widget.png?style=banner2)_](https://discord.gg/aCsmEV5RgA)
+## Email
+
+Use [homarr-labs@proton.me](mailto:homarr-labs@proton.me) for security reports, sponsorships, and other private matters.
+Bug reports and feature requests belong on GitHub.

apps/docs/docs/community/translations.mdx

@@ -5,51 +5,24 @@ tags:
   - Translations
 ---
 
-We want to make Homarr accessible for everyone.
-But to do that, we need your help.
-We are running a community program that enables everyone to translate Homarr into their language – no programming required.
-We are using [Crowdin](https://crowdin.com/) to manage our translations.
-You can find the translations [here](https://translate.homarr.dev/).
+# Translations
 
-## How to translate
+Homarr translations are managed on [Crowdin](https://translate.homarr.dev/). Select a language, translate strings in
+context, and submit them for proofreading. Approved translations ship with a later Homarr release.
 
-### Using crowdin's online platform
+## Translate from Homarr
 
-Go to the [Crowdin translations](https://translate.homarr.dev/) and select a language you want to translate.
-You can then enter the translation mode and start translating.
-After you've submitted your translations, a Proofreader will review your changes.
-After a translation has been approved, it will be merged to the language development branch.
-We merge this one periodically to the development branch.
-After the next update of Homarr, all changes from the development branch will be merged, including the changes in the translations.
+Select **Crowdin (live translations)** as the application language, connect a Crowdin account, and choose the target
+language. Select text in Homarr or use Crowdin's in-context panel to edit a string.
 
-### Using live translate
-
-You can also help translate homarr directly from the app!
-For this you can simply change your language to "Crowdin (live translations)"
-
-![](./img/crowdin-language-select.png)
-
-Then you'll be prompted to connect to your Crowdin account and choose the language in which you want to transalte.
-You can then start translating directly from the app by selecting some text on the app.
-If some text cannot be selected to be edited with the live translation tool, you can still translate it inside of the In-Context popup at the Home tab, it will be red if it's not translated yet.
-
-![](./img/crowdin-live-translate.png)
-
-:::caution
-Although you are translating directly from the app, your translations will not be directly be available inside of your language, they will be in the next update of Homarr, because we have to push the new translations to a new docker image.
-
-If you really want to use them you can enable the "preview transaltions" option in the live translate settings, but be aware that this is not recommended for performance reasons.
-:::
-
-:::tip
-
-Do you want to become a proofreader? [Let us know on our Discord](/docs/community/get-in-touch#discord)! We will add you to the proofreader team. You can then review the translations and approve them. **Note:** You must speak the language fluently, have it as your native language or lots of experience with it.
-
-:::
+Live translation submits changes to Crowdin; it does not update the installed Homarr image. Crowdin's preview option can
+show pending translations before the next Homarr release.
 
 ## Guidelines
 
-1. Translate with context: Some translations can't be translated 1:1 - they need context. Ensure that your translations make sense in the context.
-2. Keep things simple and original - no additional characters are needed.
-3. Don't translate the same thing twice - if you see a translation that is already translated, don't translate it again unless you have a better translation.
-4. Keep your translations as close to the original as possible.
+- Preserve the meaning and context of the English source.
+- Keep terminology consistent with existing translations.
+- Do not add punctuation, formatting, or explanatory text that is absent from the source.
+- Improve an existing translation only when the replacement is more accurate.
+
+Contact the [Discord community](/docs/community/get-in-touch#discord) to help proofread a language.

apps/docs/docs/getting-started/after-the-installation.mdx

@@ -6,393 +6,76 @@ tags:
   - Configuration
 ---
 
-import manageBoardNoApp from "./img/manage-board-no-app.png";
-import currentKeyboardTileEditing from "../management/boards/img/keyboard-tile-editing.png";
-import boardDesktopCurrent from "./img/onboarding-board-desktop-current.png";
-import boardEditModeCurrent from "./img/onboarding-board-edit-mode-current.png";
-import addContentMenuCurrent from "./img/onboarding-add-content-menu-current.png";
-import chooseItemCurrent from "./img/onboarding-choose-item-current.png";
-import editItemCurrent from "./img/onboarding-edit-item-current.png";
-import boardsHomeMobileMenu from "./img/onboarding-boards-home-mobile-menu.png";
-import moveResizeMenuCurrent from "./img/onboarding-move-resize-menu-current.png";
-import currentBoardMobileView from "./img/onboarding-board-mobile-current.png";
+On first launch, onboarding creates the administrator, connects optional services, and builds the first board. A
+compatible SQLite backup can also be restored from the welcome screen.
 
-:::tip
+If onboarding returns after a restart, check that `/appdata` is writable and persisted. See the
+[Docker installation guide](/docs/getting-started/installation/docker).
 
-Read our [glossary](/docs/getting-started/glossary) if you are new to Homarr.
+## Core concepts
 
-:::
+### Boards
 
-Congratulations on installing Homarr. Now it's time to get yourself familiar with the concepts of Homarr and how to use it.
+A **board** is a dashboard page containing apps, widgets, and Containers. Boards can be public or restricted to users
+and groups. Each user can choose a home board.
 
-## Onboarding
+![Board management with board previews](./img/after-installation-boards.png)
 
-Onboarding appears the first time Homarr starts. Its goal is to create a useful responsive board, not merely an
-administrator account. The setup uses one guided studio, so you can keep the safe defaults and finish quickly or review
-every detected service before anything is added to the board.
+See [Boards](/docs/management/boards) for responsive layouts, access control, appearance, and home-board settings.
 
-:::note
+### Apps
 
-If you see this screen repeatedly after restarting the Homarr container, your Docker mounting paths may be missing,
-incorrect or read-only. Read [our installation instructions](/docs/getting-started/installation/docker) again to fix this issue.
+An **app** is a saved shortcut: a name, URL, icon, and optional status check. Add an App tile or a Bookmarks widget to
+show apps on a board.
 
-:::
+![App management with saved shortcuts](./img/after-installation-apps.png)
 
-### Restore or start fresh
+See [Apps](/docs/management/apps) or [Icons](/docs/advanced/icons).
 
-SQLite installations can restore a complete Homarr database backup from the welcome screen. This restores current
-boards, people, apps, integrations, and settings. The pre-1.0 ZIP importer is no longer included.
+### Integrations
 
-For a new installation, Homarr first creates either a credentials administrator or an administrator group matching your
-LDAP/OIDC provider. The browser that starts setup claims the first-run session; refreshes are safe, while another browser
-cannot change credentials or integrations during that setup.
+An **integration** is a server-side connection from Homarr to a supported service such as Sonarr, Home Assistant, or
+Docker. Integrations provide data and actions to widgets. They can also be linked to apps.
 
-### Setup studio
+![Integration catalog with compatible widgets](./img/after-installation-integrations.png)
 
-The studio keeps related choices together:
+See [Managing integrations](/docs/management/integrations) and the
+[integration catalog](/docs/category/integrations).
 
-1. **Essentials** sets the default language, color scheme, analytics preference, and the usual host, IP address, domain, or reverse-proxy path used by your services. URL suggestions can use separate ports, subdomains, or one path per service.
-2. **Discover** checks the actual database, Docker-compatible sockets, Kubernetes configuration, Workshop, and Assistant capabilities. Unavailable sources never block manual setup.
-3. **Connect** shows detected integrations and apps first, identifying whether each app came from an explicit [`homarr.*` or Homepage Docker label](/docs/integrations/docker-labels) or image matching. Select several integrations and apps at once, review every URL, and use the service-specific link to open its API-key settings when one is available. If a container has no published port or URL label, add its HTTP or HTTPS address before importing it.
-4. **Board** previews the Base layout, colors, widget radius, sidebars, selected apps, and widgets inferred from integrations or Docker labels. Choose 8 columns for a focused board, 10 for a balanced board, 12 for a wide board, or use the slider for a custom width up to 24 columns. Homarr still creates and reflows the protected Mobile layout automatically. A fast setup adds the integration-free Clock, Weather, and Bookmarks starter widgets.
-5. **Extend** explains and optionally configures Homarr Assistant, the community Workshop, and the separate Homarr MCP endpoint.
-6. **Review** tests the selected connections, then saves integrations, apps, widgets, settings, and the exact first board together. If any part fails, the database changes are rolled back and your form stays available to correct.
+### Widgets
 
-Docker discovery reports each configured host separately. Results from reachable hosts remain selectable if another socket
-is unavailable, which is useful for remote Docker, rootless Docker, Synology, and mixed deployments. On Kubernetes or
-bare-metal installations without a Docker socket, enter services manually and use the same integration catalog.
+A **widget** is a board tile. Some widgets work on their own; others require one or more integrations. Configuration,
+supported integrations, and non-obvious limitations are documented on each widget page.
 
-After setup, **Open my board** takes you directly to the configured board. The in-product tour then introduces edit mode,
-responsive layouts, widgets, and search without delaying completion.
+![Board in edit mode with the add-content menu](./img/after-installation-widgets.png)
 
-## Creating another board
+See the [widget catalog](/docs/category/widgets).
 
-In Homarr, you organize your apps and widgets on boards.
-Boards use fixed-size tiles so the same widget keeps the same proportions on every screen.
-Drag, resize, and section controls are available in edit mode.
-Onboarding already created the first board. To create another one, navigate to `Manage` > `Boards` > `New board`:
-![](./img/manage-create-board-button.png)
+### Containers and rails
 
-A board must always have a name and can either be public or private.
-Public boards are also accessible for users, that are not logged in ([see access control for boards](/docs/management/boards/#access-control)).
+A **Container** groups board items and can be nested. A **rail** reserves a fixed area at the left or right of a
+responsive layout. Both are configured in board edit mode.
 
-![](./img/manage-create-board-modal.png)
+![Board layout settings with fixed sidebars](./img/after-installation-containers-rails.png)
 
-Congratulations - you've just created another board. You can see the boards you have access to on this page:
+See [Boards](/docs/management/boards#containers-and-rails).
 
-<figure>
-  <img
-    src={boardsHomeMobileMenu}
-    alt="Boards management page showing a Home badge and separate desktop and mobile home-board menu entries"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>The Boards page selects the board opened from Home separately for desktop and mobile.</figcaption>
-</figure>
+### Users, groups, and permissions
 
-The board marked **Home** is the board opened from the desktop Home route. **Set as your mobile board** selects which board
-opens on phones. This is separate from the **Mobile** layout: the home-board setting chooses a board, while **Mobile** and
-**Base** are responsive layouts inside that board. A phone can therefore open a different home board and still use that
-board's Mobile layout.
+Users inherit permissions and default boards from their groups. Resource-specific access can further restrict boards
+and integrations.
 
-New boards start with **Mobile** and **Base** responsive layouts automatically, so you can edit the board for phones and
-desktops without creating extra layouts first. Mobile starts at `0px` with 3 columns and Base at `768px` with 10 columns.
-Each layout keeps its own tile positions and sizes.
+![Group permission settings](./img/after-installation-users-permissions.png)
 
-## Add your first app to Homarr
+See [Users and groups](/docs/management/users) and [single sign-on](/docs/advanced/single-sign-on).
 
-To add links to your dashboard, you must first add them as an "app".
-Navigate to this page to add an app:
+## Explore further
 
-![](./img/manage-navigate-apps.png)
+- [Server settings](/docs/management/settings)
+- [Assistant](/docs/management/assistant)
+- [Custom Widgets](/docs/management/custom-widgets)
+- [Community Workshop](/docs/workshop)
+- [API](/docs/management/api) and [MCP](/docs/management/mcp)
+- [Keyboard shortcuts](/docs/advanced/keyboard-shortcuts)
 
-Next, click on the `New app` button. You'll need to provide a name and an icon to create an app.
-The name must be at least one character long but you can provide any image URL for the icon.
-Homarr ships with over 11K icons - so you can just search by entering a search text instead.
-
-![](./img/manage-add-app-form.png)
-
-After you created the app, you'll see in on the apps page:
-
-![](./img/manage-created-app.png)
-
-## Arrange and organize your board
-
-Let's add your freshly created app, from the previous step, to the board.
-To do this, edit your previously created board by clicking on the big `Open board` button:
-
-<figure>
-  <img src={boardDesktopCurrent} alt="Current Homarr board opened from the Boards page" style={{ maxWidth: "100%" }} />
-  <figcaption>Open a board to view its dashboard, then enter edit mode to arrange its content.</figcaption>
-</figure>
-
-Here you have the following options in the header:
-
-![](./img/manage-board-header.png)
-
-- **Search**: Here you can search for data. You can search for integrations, boards, actions, sites and much more. Some actions may be context dependent (eg. will only show when certain widgets are on your page)
-- **Edit board**: Clicking this button will toggle edit mode. In this mode you can edit the contents of your board.
-- **Settings**: Clicking this button will redirect you to a settings page where you can adjust the board settings (page title, colors, ...).
-- **Board switcher**: Use this button to open another board that you can access.
-- **Profile**: This avatar will be visible on every page. Clicking it will show a menu with actions.
-
-When entering the edit mode, you'll get some additional buttons to work with:
-
-<figure>
-  <img
-    src={boardEditModeCurrent}
-    alt="Current Homarr board editor with tile controls visible"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>The current editor keeps the board visible while its editing controls are available.</figcaption>
-</figure>
-
-- **Add board content**: Click this button to create a new item, app, integration, or Container.
-- **Save board**: Click this button to save your changes and leave edit mode. If you leave with unsaved changes, Homarr asks whether to discard them.
-
-Outside edit mode, right-click a widget for its live status, refresh, settings, quick options, and supported actions.
-Hold `Shift` while hovering a widget that supports advanced view to expand it in place while the rest of the board
-stays visible but dimmed. Release `Shift` to close it. You can also focus that widget and press `Shift` + `Enter` to
-keep its advanced view open until you close it. Widgets without a distinct advanced experience adapt in place.
-
-To continue, click **New item** in the add-content menu. New content is placed at the first available position on the main
-canvas; it is not inserted at a clicked empty cell or directly into a rail or Container:
-
-<figure>
-  <img
-    src={addContentMenuCurrent}
-    alt="Current add board content menu with item, app, integration, and Container actions"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>The add-content menu provides the four supported ways to place new content on the board.</figcaption>
-</figure>
-
-Next, you can choose what item you'd like to add.
-We will discuss the other options in the following sections - for now choose "App" to continue.
-
-<figure>
-  <img
-    src={chooseItemCurrent}
-    alt="Current item picker showing the App card and other item types"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>Choose the App item from the current picker to add an app tile.</figcaption>
-</figure>
-
-As soon as you chose the app, the modal will close and you'll get the following item on your board:
-
-<img src={manageBoardNoApp} alt="Screenshot of the No app element on the board" />
-
-This is expected, because you haven't told Homarr what app it should show in this item.
-To configure this, click on the small 3 dots at the top of the item in the edit mode and choose "Edit item" in the menu.
-
-<figure>
-  <img
-    src={moveResizeMenuCurrent}
-    alt="Current board tile menu showing Edit item and Move or resize item"
-    style={{ maxWidth: "450px" }}
-  />
-  <figcaption>The tile menu contains the item editor and the separate move-and-resize tools.</figcaption>
-</figure>
-
-In the modal you can edit the app that you want to display:
-
-<figure>
-  <img src={editItemCurrent} alt="Current Edit item modal for an App tile" style={{ maxWidth: "620px" }} />
-  <figcaption>Use the Edit item modal to choose the app and configure how its tile is displayed.</figcaption>
-</figure>
-
-As soon as you save your changes, the tile on the board will refresh and display your app.
-Resize from any visible edge or corner handle. For a Container, activate its top-left grip before using its resize handles.
-Press and hold a handle, move the pointer, and release it when the tile has the size you want.
-
-To move a tile in edit mode, press and hold its inert content area, move it to the desired position, and release it.
-Widget content is disabled while editing so its controls do not intercept the drag; use the tile's settings button for edit actions.
-The tile snaps to the grid. A single compatible collision may swap the two items when both resulting placements fit;
-otherwise the collision chain reflows neighboring tiles automatically.
-
-Every `1 × 1` tile has a logical content size of `200 × 200` pixels.
-Larger tiles use multiples of that fixed unit, with a consistent gap between cells.
-Homarr scales the complete board uniformly, like zooming a page.
-The complete canvas always fits the available width without horizontal board scrolling. Below 100%, Homarr preserves the
-widget's readable typography and control density instead of shrinking each widget independently.
-It does not squeeze or reflow the content of individual widgets, so a widget keeps the same design and proportions across screen sizes.
-
-On a narrow screen, Homarr uses the **Mobile layout** for the selected board and stacks the board content vertically while
-preserving each widget's fixed logical proportions:
-
-<figure>
-  <img
-    src={currentBoardMobileView}
-    alt="Homarr's Mobile layout in a 390-pixel-wide viewport, with tiles scaled to fit and stacked vertically"
-    style={{ maxWidth: "390px" }}
-  />
-  <figcaption>
-    At phone width, the selected board uses its Mobile layout and fits the complete canvas to the viewport.
-  </figcaption>
-</figure>
-
-:::note
-
-Viewing a board initially uses the lightweight, non-interactive layout.
-For users with edit access, Homarr prepares drag-and-drop and resize controls in the background after the board becomes interactive.
-If you enter edit mode before that finishes, the existing board stays visible until the editor is ready.
-
-:::
-
-:::tip
-
-We recommend you to experiment for a few minutes, before you start building your actual dashboard.
-This helps you to explore the capabilities of Homarr before you build your board in a suboptimal way.
-
-:::
-
-Keyboard users can focus a tile, press Enter or Space, then use arrow keys to move and Shift plus arrow keys to resize
-within its current canvas, rail, or Container. Press Escape to stop keyboard editing. Touch dragging starts after a short
-hold of about `200 ms`; resize handles accept direct touch input. During a pointer or touch move or resize, press Escape
-to cancel and restore the previous layout. For cross-grid moves or precise numeric controls, choose **Move / resize item**
-from the tile's edit menu.
-Keyboard commands at a grid boundary or minimum tile size are ignored and announced; they do not move or shrink the tile.
-
-<img src={currentKeyboardTileEditing} alt="A board tile focused for keyboard editing" style={{ maxWidth: "100%" }} />
-
-Open **Move / resize item** from the tile menu to move the tile to another section or rail and enter precise numeric
-coordinates and dimensions. After making changes, click **Save board** to persist them and leave edit mode.
-
-## Adding your first integration
-
-Now it's time to integrate some basic data into your board.
-To do this, we first need to create an integration.
-An integration is a connection between Homarr and a third party application - usually something that you run and deploy yourself.
-
-Navigate to `Manage` > `Integrations` (for example via your user menu).
-As an example, we are going to use the public demo instance of **Dash.** - a popular application to monitor CPU / hardware usage.
-Choose the **Dash.** integration from the list of available integrations:
-
-![](./img/choose-integration.gif)
-
-Next, choose a name (or leave it at default), enter `https://dash.mauz.dev/` as the URL in the form and click on `Test connection and create`.
-Pressing the save button will perform a test request to the integration, to confirm that the networking setup is working as expected.
-Sometimes invalid configurations, firewalls and other mistakes can lead to connectivity problems - [follow this guide here](/docs/management/integrations/#troubleshooting-connection) if you experience issues.
-
-If connection was successful, you will be redirect back to the list of integrations.
-Now let's embed it to your board (see next section).
-
-:::note
-
-Some integrations may require additional configuration, such as a username, password or API tokens.
-Depending on your networking setup and applications, the connection from Homarr might also get blocked by firewalls,
-the target application or your router.
-
-:::
-
-## Embed integration data using widgets
-
-Let's add your integration, that you have configured in the section above, as a widget to your board.
-First, navigate back to your board that you want to add it to.
-Next, enter edit mode again and add another item to your board:
-
-<figure>
-  <img
-    src={addContentMenuCurrent}
-    alt="Current add board content menu with item, app, integration, and Container actions"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>Use the same add-content menu to place an integration widget on the board.</figcaption>
-</figure>
-
-Instead of choosing an app, let's choose `System Health Monitoring` this time.
-Click on "Add to board":
-
-![](./img/manage-board-header-choose-system-health.png)
-
-Resize the item slightly and then edit it using the three dots menu at the top:
-
-![](./img/edit-system-health-widget.gif)
-
-Next, choose your newly created Dash. integration in the integrations dropdown:
-
-![](./img/manage-board-edit-system-health.png)
-
-:::note
-
-Some widgets may support multiple integrations at the same time.
-If they do not support multiple integrations, you will be unable to select more than one.
-
-:::
-
-Confirm your changes by pressing save.
-Editing a widget will trigger a data update and data will soon appear:
-
-![](./img/widget-system-health.png)
-
-As with every change, click **Save board** to persist your board changes and leave edit mode.
-
-## Organizing items with Containers
-
-Containers are resizable areas for apps, widgets, and nested Containers.
-The same Container works on the main canvas, inside a fixed rail, or inside another Container.
-Each Container can configure:
-
-- Its label and whether that label is visible.
-- Allow or disable collapsing.
-- Show or hide **Open all in new tabs**.
-- Change its border color and custom CSS classes.
-
-Open the add-content menu and choose **New container**.
-In edit mode, move and resize it like any other item, then drag items into or out of it.
-Nested content stays within the Container's bounds.
-While resizing, the solid outline follows the pointer continuously and the dashed grid preview shows the size that will be saved on release.
-
-### Collapsing and opening apps
-
-Users can collapse an eligible Container like an accordion in view mode without changing its saved expanded size.
-The full-width header becomes the compact expansion bar, so the half-row state has no empty pill-shaped spacer.
-Expanding it restores its bounds and makes room for its contents.
-If **Open all in new tabs** is enabled, the Container menu can open every app link it contains.
-
-### Fixed rails
-
-Open the board's **Layout** settings to enable the left or right rail for each responsive layout.
-Choose one, two, or three columns with the slider and use the preview to check the remaining canvas width.
-The rail reserves those columns from the dashboard, so Homarr moves canvas items into the next available positions.
-Rail content stays visible while the page scrolls and remains editable.
-Each responsive layout keeps its own rail widths, item positions, and item sizes.
-
-## Guided tours
-
-After completing the onboarding, Homarr provides interactive guided tours to help you discover key features.
-
-### Management tour
-
-When you first visit the management area (`/manage`), Homarr walks you through the main pages: boards, apps, integrations, and users (admin only).
-Each page highlights the list view and the create action so you know where to find and add things.
-
-### Board tour
-
-When you first open a board, a tour highlights the board header elements: search, edit mode, settings, board switcher, and user menu.
-
-### Tour controls
-
-- Press **Enter** (or click **Next**) to advance through tour steps
-- Tours auto-start on first visit and do not repeat once completed
-- Tours are skipped on mobile screens (below `sm` breakpoint)
-- You can **reset tours** from the user settings page under **Manage > Users > [Your user] > General**
-
-## Next steps
-
-You're done with the basic setup 🔥. Now it's time to organize and customize even more.
-We highly recommend you to experiment with different options, styles and configurations.
-See these curated pages for your next steps:
-
-- Create new apps using the [apps management](/docs/management/apps/)
-- Customize your board or add more boards using the [boards management](/docs/management/boards/)
-- Integrate software that you use using the [integrations management](/docs/management/integrations/)
-- Choose from our beautiful and interactive [widgets](/docs/category/widgets)
-- See [all supported integrations](/docs/category/integrations)
-- Integrate with Homarr with your own application using [the API](/docs/management/api/)
-
-:::danger
-
-The Homarr Team will never ask for your credentials. Do not send people your credentials, as they manage the access to your applications and can cause harm to your device if they are abused.
-
-:::
+See the [glossary](/docs/getting-started/glossary) for a compact list of Homarr terms.

apps/docs/docs/getting-started/glossary.mdx

@@ -2,12 +2,19 @@
 
 This glossary explains Homarr's main components and the terms used for them.
 
-| Term        | Definition                                                                              |
-| ----------- | --------------------------------------------------------------------------------------- |
-| Apps        | A piece of software that you or a third party hosts (for example, Google)               |
-| Integration | A connection to a service outside of Homarr                                             |
-| Container   | A resizable area that can hold apps, widgets, and nested Containers                     |
-| Widget      | A tile that uses your integrations to display data or enables you to interact with them |
-| Edit mode   | A temporary state where you can drag, resize, edit, or customize your board             |
-| Board       | A customizable page where apps, widgets, and Containers are arranged                    |
-| Tasks       | Workloads that are performed in the background, even if no user is present              |
+| Term            | Definition                                                                       |
+| --------------- | -------------------------------------------------------------------------------- |
+| App             | A saved shortcut with a name, destination, icon, and optional status check       |
+| Assistant       | A conversation interface that can use model responses and Homarr tools           |
+| Board           | A dashboard page where apps, widgets, and Containers are arranged                |
+| Container       | A resizable board area containing apps, widgets, or nested Containers            |
+| Custom Widget   | A validated definition for an API-backed board tile                              |
+| Edit mode       | The board state used to add, move, resize, configure, or remove content          |
+| Homarr provider | An Assistant provider routed through Workshop with a per-user allowance          |
+| Integration     | A server-side connection from Homarr to a supported service                      |
+| Layout          | An arrangement of board items selected for a viewport width                      |
+| Provider        | The model API selected for Assistant                                             |
+| Rail            | A fixed area at the left or right of a non-Mobile board layout                   |
+| Task            | A background workload that runs without an active browser session                |
+| Widget          | A board tile that displays information or provides actions                       |
+| Workshop        | A separate community service for sharing Custom Widget definitions and board CSS |

apps/docs/docs/getting-started/index.mdx

@@ -1,45 +1,31 @@
 ---
-title: Prerequisites
+title: Getting started
 sidebar_position: 1
 tags:
   - Getting Started
   - Installation
-  - Docker
-  - Unraid
 ---
 
-import Link from "@docusaurus/Link";
-import { IconArrowRight } from "@tabler/icons-react";
+import {
+  GettingStartedOverview,
+  InstallationPaths,
+} from "@site/src/components/pages/getting-started/getting-started-overview";
 
-Before you try to install Homarr, please review if your device meets the requirements.
-Installing on an unsupported device may lead to unstable behaviour and no support will be provided.
+<GettingStartedOverview />
 
-## Hardware
+## Requirements
 
-- At least 500MB RAM
-- At least 600MB of free disk space for the Docker image. SSD is preferred.
-- Single or dual core CPU
-- Stable network connection, Wi-Fi use is not recommended
+- `linux/amd64` or `linux/arm64`;
+- 500 MB RAM;
+- 600 MB free disk space for the container image;
+- a persistent writable `/appdata` directory.
 
-## Architecture
+`linux/arm/v7` is not supported.
 
-We build Homarr for a bunch of different architectures, including ARM. Please ensure that your device architecture is supported by Homarr. We won't be able to provide support for unusual or outdated architectures.
+## Choose an installation method
 
-| Architecture | Supported        |
-| ------------ | ---------------- |
-| linux/amd64  | ✅ Supported     |
-| linux/arm64  | ✅ Supported     |
-| linux/arm/v7 | ❌ Not supported |
+<InstallationPaths />
 
-## Getting started with installation
-
-<Link
-  data-attr="Go to installation"
-  className={"button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800"}
-  to="/docs/category/installation-1"
->
-  <div className={"flex items-center gap-3"}>
-    <span className={"dark:text-gray-200"}>Go to Installation</span>
-    <IconArrowRight className={"dark:text-gray-200"} size={20} />
-  </div>
-</Link>
+After Homarr starts, open it in a browser and complete onboarding. Then continue with
+[After the installation](/docs/getting-started/after-the-installation) for the core concepts and the most useful next
+links.

apps/docs/docs/getting-started/installation/docker.mdx

@@ -2,106 +2,52 @@ import { DockerInstallSnippet } from "@site/src/components/pages/installation/do
 
 # Docker
 
-Docker is our recommended installation method for beginners and professionals.
-It is easy to use, ships with all dependencies inside a single container and is easy to use and maintain.
-It requires at least some basic knowledge of [Docker](https://www.docker.com/).
-We recommend [NetworkChuck's Docker Containers 101](https://www.youtube.com/watch?v=eGz9DS-aIeY) as a good start for complete beginners.
+Docker Compose is the recommended installation method. Install
+[Docker Engine](https://docs.docker.com/engine/install/) and the
+[Compose plugin](https://docs.docker.com/compose/install/).
 
-## Docker compose
-
-### Prerequisites
-
-- A Linux or Windows based system that meets the [hardware prerequisites](/docs/getting-started/#hardware) and [architecture prerequisites](/docs/getting-started/#architecture).
-- [Docker](https://docs.docker.com/get-docker/)
-- [Docker Compose](https://docs.docker.com/compose/install/) - _preinstalled on many systems nowadays_
-
-### Installation
+## Docker Compose
 
 <DockerInstallSnippet data-visual-test="blackout" />
-Finally, run ``docker compose up -d`` in the same directory. This will start the Homarr container in the background.
 
-:::caution
+Start Homarr from the directory containing `docker-compose.yaml`:
 
-Docker compose creates a network by default. Some integrations may not work (specifically Dash.) when the network internal hostname is used since clients do not know this name. It is recommended that you either use a local network wide hostname or the IP directly. An alternative is to create a DNS record with the same internal compose stack hostname for all clients outside.
+```sh
+docker compose up -d
+```
 
-:::
+Persist `/appdata`; it contains the database and configuration. Mount the Docker socket only when Homarr needs Docker
+discovery or management.
 
-### Updating
+Integration URLs must be reachable from the Homarr container. Browser-facing app URLs may use a different hostname;
+see [Managing integrations](/docs/management/integrations#configuration).
 
-To update, navigate to the directory with the `docker-compose.yaml` located.
+### Update
 
-- Stop Homarr using `docker compose down`
-- Pull the newest image of Homarr using `docker compose pull`
-- Start Homarr again using `docker compose up -d` (`-d` for detached mode - start in background)
-- Delete the old image using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+```sh
+docker compose pull
+docker compose up -d
+```
 
-You can automate this process using [Watchtower](https://containrrr.dev/watchtower/).
+### Uninstall
 
-### Uninstalling
+`docker compose down` removes the containers and Compose network. Delete the configured `/appdata` host directory or
+volume only when the Homarr data is no longer needed.
 
-To uninstall, navigate to the directory with the `docker-compose.yaml` located.
+## Docker CLI
 
-- Stop Homarr using `docker compose down`
-- Delete the created directories & files on your root file system (check `docker-compose.yaml` file for your specific locations)
-- Delete compose file using `rm docker-compose.yaml`
-- Prune unused Docker images using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
-- (Optional): Prune any network or volumes if you use any.
-- (Optional): Remove Homarr from your reverse proxy, VPNs or tunnels if you use any.
+The equivalent standalone container is:
 
-## Docker standalone
-
-:::caution
-
-[Docker Compose](#docker-compose) is easier and recommended for beginners. Consider using compose instead.
-
-:::
-
-### Prerequisites
-
-- A Linux or Windows based system that meets the [hardware prerequisites](/docs/getting-started/#hardware) and [architecture prerequisites](/docs/getting-started/#architecture).
-- [Docker](https://docs.docker.com/get-docker/)
-
-### Installation
-
-To install Homarr using Docker, simply run the following command.
-
-```bash
-docker run  \
+```sh
+docker run \
   --name homarr \
   --restart unless-stopped \
   -p 7575:7575 \
   -v /var/run/docker.sock:/var/run/docker.sock \
-  -v <your-path>/homarr/appdata:/appdata \
+  -v /absolute/path/to/homarr/appdata:/appdata \
   -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' \
   -d ghcr.io/homarr-labs/homarr:latest
 ```
 
-:::note
-
-Docker will mount the configuration files and icons to your host machine. Please make sure to replace `<your-path>` from the docker run command with your desired storage location. The path must be absolute.
-
-:::
-
-### Updating
-
-To update Homarr, you must remove your container first. Make sure that you've mounted your data and that you have access to it, so your configuration doesn't get lost.
-
-1. Run `docker rm homarr` to remove the container.
-2. Pull the latest Homarr image `docker pull ghcr.io/homarr-labs/homarr:latest`.
-3. Re-run the command you used to install Homarr.
-
-This process can get tideous, if you update frequently. Thus, we recommend [using docker-compose](#docker-compose)
-
-:::tip
-
-Want to update all your containers automatically? Checkout [Watchtower](https://containrrr.dev/watchtower/) a service which will automatically update your containers on a set interval.
-
-:::
-
-### Uninstalling
-
-1. Obtain the container ID of your Homarr container using `docker ps | grep homarr`.
-2. Delete the container using `docker rm <your-container-id>`
-3. Prune unused Docker images using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
-4. (Optional): Prune any network or volumes if you use any.
-5. (Optional): Remove Homarr from your reverse proxy, VPNs or tunnels if you use any.
+Remove the Docker socket mount when it is not required. To update, pull the current image, recreate the container with
+the same arguments, and keep the `/appdata` mount and `SECRET_ENCRYPTION_KEY` unchanged.

apps/docs/docs/getting-started/installation/helm.md

@@ -2,9 +2,9 @@
 
 <img src="https://raw.githubusercontent.com/homarr-labs/charts/refs/heads/main/charts/homarr/icon.svg" align="right" width="92" alt="homarr logo">
 
-![Version: 8.26.0](https://img.shields.io/badge/Version-8.26.0-informational?style=flat)
+![Version: 8.28.1](https://img.shields.io/badge/Version-8.28.1-informational?style=flat)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat)
-![AppVersion: v1.74.0](https://img.shields.io/badge/AppVersion-v1.74.0-informational?style=flat)
+![AppVersion: v1.76.1](https://img.shields.io/badge/AppVersion-v1.76.1-informational?style=flat)
 
 A Helm chart to deploy homarr for Kubernetes
 
@@ -437,7 +437,7 @@ All available values are listed on the [artifacthub](https://artifacthub.io/pack
 | httproute.rules[0].matches[0].path.value           | string | `"/"`                                                                                                                                                                                                                                            | Path value to match                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | image.pullPolicy                                   | string | `"IfNotPresent"`                                                                                                                                                                                                                                 | Image pull policy                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 | image.repository                                   | string | `"ghcr.io/homarr-labs/homarr"`                                                                                                                                                                                                                   | Image repository                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| image.tag                                          | string | `"v1.74.0"`                                                                                                                                                                                                                                      | Overrides the image tag whose default is the chart appVersion                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| image.tag                                          | string | `"v1.76.1"`                                                                                                                                                                                                                                      | Overrides the image tag whose default is the chart appVersion                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | imagePullSecrets                                   | list   | `[]`                                                                                                                                                                                                                                             | Secrets for Docker registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | ingress.annotations                                | object | `{}`                                                                                                                                                                                                                                             | Ingress annotations                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | ingress.enabled                                    | bool   | `false`                                                                                                                                                                                                                                          | Enable ingress                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |

apps/docs/docs/getting-started/installation/portainer.mdx

@@ -1,14 +1,8 @@
 # Portainer
 
-## Portainer Stacks
+## Install with a stack
 
-### Prerequisites
-
-- [Portainer Stacks](https://www.portainer.io/blog/stacks-docker-compose-the-portainer-way)
-
-### Installing
-
-To install Homarr using Portainer Stacks, simply create a new stack and paste the following code into it.
+Create a Portainer stack with this Compose file:
 
 ```yml title="docker-compose.yml"
 #---------------------------------------------------------------------#
@@ -28,21 +22,12 @@ services:
       - "7575:7575"
 ```
 
-:::note
-Portainer will mount the files to your host machine. Please make sure to replace `<your-path>` from the docker run command with your desired storage location. The path must be absolute.
-:::
-
-Then, click on `Deploy the stack` and wait until the container has started.
-
-:::tip
-
-If you're unsure how to create a stack, checkout the [Portainer Documentation](https://docs.portainer.io/user/docker/stacks/add).
-
-:::
+Replace `<your-path>` with an absolute host path, generate `SECRET_ENCRYPTION_KEY`, then deploy the stack. See
+[Portainer's stack documentation](https://docs.portainer.io/user/docker/stacks/add) for Portainer-specific options.
 
 ### Updating
 
-To update Homarr using Docker Compose or Portainer Stacks, simply pull the latest image and restart the container.
+Pull the current image and redeploy the stack:
 
 1. Run `docker pull ghcr.io/homarr-labs/homarr:latest` to pull the latest image.
 2. Re-run `docker-compose up -d` or re-deploy the stack in Portainer.

apps/docs/docs/getting-started/installation/qnap.mdx

@@ -1,9 +1,11 @@
 # QNAP
 
 :::caution
-QNAP installation guide has not updated to 1.0 yet. There guide is still for 0.15.10.
+
+The available QNAP guides target Homarr 0.15.10 and have not been updated for 1.0.
+
 :::
 
-When installing on QNAP, we recommend you to install Homarr using [Container Station](https://www.qnap.com/en/software/container-station) or [this third-party image](https://www.myqnap.org/product/homarr/).
-
-There is also a guide available, but note that it is written in Chinese: https://post.smzdm.com/p/awzm7op2/
+Run Homarr with [Container Station](https://www.qnap.com/en/software/container-station) or the
+[third-party QNAP package](https://www.myqnap.org/product/homarr/). A community
+[Container Station guide](https://post.smzdm.com/p/awzm7op2/) is available in Chinese.

apps/docs/docs/getting-started/installation/runtipi.mdx

@@ -1,33 +1,12 @@
 # Runtipi
 
-Runtipi is a self-hosted orchestrator that makes it easy to manage and run multiple services on a single server. It is based on Docker and comes with a simple web interface to manage your services. Runtipi is designed to be easy to use, so you don't have to worry about manual configuration or networking.
+Homarr is available in the default [Runtipi](https://runtipi.io) app store.
 
-https://runtipi.io
+## Installation
 
-## Prerequisites
+Install **Homarr** from the Runtipi app store and select either a port or domain for access.
 
-- [Runtipi](https://runtipi.io/docs/getting-started/installation)
+Runtipi manages start, stop, update, backup, and log operations under **My apps → Homarr**. Use a
+[user-config](https://runtipi.io/docs/guides/customize-app-config) to override the generated Compose configuration.
 
-# Installation
-
-Installing Homarr is pretty untuitive, the app is available in the default appstore :
-
-1. Search for **"Homarr"** in the App-Store page and select it
-2. Click on **"Install"**.
-3. Choose the method you want to access Homarr, through any port or domain name then select **"Install"**
-
-# Maintenance
-
-After installation, all you need is available from the WebUI in **"My apps"** > **"Homarr"** :
-
-- Start/Stop
-- Update
-- Backup
-- Logs
-
-If you like to tinker with your apps, you can also edit your app's docker-compose with a [user-config](https://runtipi.io/docs/guides/customize-app-config).
-
-# Getting help
-
-- If you are looking for help with anything in Runtipi. They provide support on their [Discord](https://discord.gg/Bu9qEPnHsc) and [forums](https://forums.runtipi.io/). If you found vulnerabilities or bugs, [create a new issue here](https://github.com/runtipi/runtipi-appstore/issues).
-- If you are looking to report a bug, vulnerability or request a new feature for Homarr, use https://github.com/homarr-labs/homarr . You can ask for help on our Discord.
+See the [Runtipi installation documentation](https://runtipi.io/docs/getting-started/installation) for host setup.

apps/docs/docs/integrations/beszel/index.ts

@@ -1,9 +1,9 @@
-import { IntegrationDefinition } from "@site/src/types";
+import type { IntegrationDefinition } from "@site/src/types";
 
-export const beszelIntegration: IntegrationDefinition = {
+export const beszelIntegration = {
   name: "Beszel",
   description:
     "Beszel is a lightweight server monitoring platform with Docker stats, historical data, and alert functions.",
   iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/svg/beszel.svg",
   path: "../../integrations/beszel",
-};
+} satisfies IntegrationDefinition;

apps/docs/docs/integrations/docker/index.mdx

@@ -1,306 +1,132 @@
 ---
 title: "Docker"
-description: "Docker is a platform where you can run your applications in containers, allowing for easy deployment and management of applications."
+description: "Connect Homarr to Docker-compatible container engines."
 hide_title: true
 ---
 
 import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IconBrandDocker, IconTool } from "@tabler/icons-react";
 import { dockerIntegration } from ".";
 import { dockerContainersWidget } from "@site/docs/widgets/docker-containers";
 
 <IntegrationHeader integration={dockerIntegration} categories={["Containers"]} />
 
-### Widgets & Capabilities
+### Widgets and capabilities
 
-<IntegrationCapabilites
-  items={[
-    {
-      widget: dockerContainersWidget,
-      note: "This widget can only be used with administrator privileges",
-    },
-  ]}
-/>
+<IntegrationCapabilites items={[{ widget: dockerContainersWidget, note: "Requires administrator access" }]} />
 
-## Enabling the Docker integration
+Docker endpoints are configured with environment variables rather than under **Management → Integrations**.
 
-This integration must first be enabled.
-If you directly run on the host system and you have docker installed, it will be enabled by default.
-Otherwise, you'll need to mount the [docker socket](https://docs.docker.com/engine/security/protect-access/) to the Homarr container,
-so Homarr can interact with the Docker service.
+## Local socket
 
-In Docker Compose, you can simply add this line:
+Mount the Docker socket into the Homarr container:
 
-```yaml {10}
-#---------------------------------------------------------------------#
-#     Homarr - A simple, yet powerful dashboard for your server.      #
-#---------------------------------------------------------------------#
+```yaml
 services:
   homarr:
-    container_name: homarr
     image: ghcr.io/homarr-labs/homarr:latest
-    restart: unless-stopped
     volumes:
-      - /var/run/docker.sock:/var/run/docker.sock # <--- add this line here!
+      - /var/run/docker.sock:/var/run/docker.sock
       - ./homarr/appdata:/appdata
-    environment:
-      - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
-    ports:
-      - "7575:7575"
 ```
 
-With docker run, add this parameter: `-v /var/run/docker.sock:/var/run/docker.sock`.
-In Windows, you'll need to adjust the slashes: `-v //var/run/docker.sock:/var/run/docker.sock`
+`/var/run/docker.sock` is the default. For other in-container paths, set a comma-separated list:
 
-### Using Podman
+```yaml
+environment:
+  DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
+```
 
-On Linux, Homarr can connect to Podman's [Docker-compatible API](https://docs.podman.io/en/latest/markdown/podman-system-service.1.html).
-The Podman API socket must be running and mounted into the Homarr container.
-The socket grants full access to Podman, including arbitrary code execution as the user running the API, so only mount it into trusted containers.
+## Podman
 
-For rootless Podman, enable the socket for the user that runs Homarr:
+Homarr uses Podman's Docker-compatible API. Start the Podman socket, mount it, and include its in-container path in
+`DOCKER_SOCKET_PATHS`.
 
-```bash
+For rootless Podman:
+
+```sh
 systemctl --user enable --now podman.socket
-```
-
-The rootless socket is located at `$XDG_RUNTIME_DIR/podman/podman.sock` (usually `/run/user/<uid>/podman/podman.sock`).
-You can confirm the path with:
-
-```bash
 podman info --format '{{.Host.RemoteSocket.Path}}'
 ```
 
-Mount that socket into the Homarr container and point `DOCKER_SOCKET_PATHS` to its path **inside** the container:
+Run Homarr as the user that owns the socket. On SELinux systems, Podman may require `security_opt: [label=disable]` for
+the Homarr container. Rootful Podman normally exposes `/run/podman/podman.sock`.
+
+## Remote endpoints
+
+For Docker socket proxies, list aligned hostnames and ports:
 
 ```yaml
-services:
-  homarr:
-    container_name: homarr
-    image: ghcr.io/homarr-labs/homarr:latest
-    restart: unless-stopped
-    volumes:
-      - ${XDG_RUNTIME_DIR}/podman/podman.sock:/var/run/podman.sock
-      - ./homarr/appdata:/appdata
-    environment:
-      SECRET_ENCRYPTION_KEY: your_64_character_hex_string
-      DOCKER_SOCKET_PATHS: /var/run/podman.sock
-    ports:
-      - "7575:7575"
+environment:
+  DOCKER_HOSTNAMES: docker-proxy-home,docker-proxy-lab
+  DOCKER_PORTS: 2375,2375
 ```
 
-Start Homarr with `podman compose up -d`.
-Run the compose project as the same user that owns the rootless Podman socket so `$XDG_RUNTIME_DIR` resolves to the correct path.
-To keep the user socket available after logout and across reboots, enable lingering with `loginctl enable-linger <user>`.
+:::warning Plaintext Docker API
 
-For rootful Podman, enable the system socket with `sudo systemctl enable --now podman.socket`.
-Its default path is `/run/podman/podman.sock`; mount that path instead and start Homarr with `sudo podman compose up -d`.
-
-:::note SELinux
-On systems with SELinux enabled, Podman's documentation recommends disabling label separation for a container that accesses the API socket.
-Add the following to the Homarr service:
-
-```yaml
-security_opt:
-  - label=disable
-```
+Unauthenticated Docker TCP provides control of the Docker host. Keep a socket proxy on a private network or use TLS.
 
 :::
 
-You can connect Homarr to multiple Docker-compatible sockets by mounting each socket and listing their in-container paths, separated by commas:
+Use `DOCKER_ENDPOINTS` for named endpoints, TLS, or restricted capabilities:
 
 ```yaml
-services:
-  homarr:
-    image: ghcr.io/homarr-labs/homarr:latest
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock
-      - ${XDG_RUNTIME_DIR}/podman/podman.sock:/var/run/podman.sock
-    environment:
-      DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
+environment:
+  DOCKER_ENDPOINTS: >-
+    [
+      {
+        "id": "local",
+        "name": "Local Docker",
+        "kind": "docker",
+        "transport": { "type": "socket", "path": "/var/run/docker.sock" },
+        "capabilities": ["inventory", "logs", "lifecycle", "remove"]
+      },
+      {
+        "id": "production",
+        "name": "Production inventory",
+        "kind": "docker",
+        "transport": {
+          "type": "tls",
+          "host": "docker.example.com",
+          "port": 2376,
+          "caPath": "/run/secrets/docker-ca.pem"
+        },
+        "capabilities": ["inventory", "logs"]
+      }
+    ]
 ```
 
-For named endpoints, transport security, or least-privilege actions, prefer `DOCKER_ENDPOINTS`. It is a JSON array where every endpoint declares its identity, transport, and capabilities:
+Each endpoint requires a stable `id`, display `name`, `kind` (`docker` or `podman`), transport, and the `inventory`
+capability. Optional capabilities are `logs`, `lifecycle`, and `remove`.
 
-```yaml
-services:
-  homarr:
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock
-      - ./docker-ca.pem:/run/secrets/docker-ca.pem:ro
-    environment:
-      DOCKER_ENDPOINTS: >-
-        [
-          {
-            "id": "local",
-            "name": "Local Docker",
-            "kind": "docker",
-            "transport": { "type": "socket", "path": "/var/run/docker.sock" },
-            "capabilities": ["inventory", "logs", "lifecycle", "remove"]
-          },
-          {
-            "id": "remote-read-only",
-            "name": "Production inventory",
-            "kind": "docker",
-            "transport": {
-              "type": "tls",
-              "host": "docker.example.com",
-              "port": 2376,
-              "caPath": "/run/secrets/docker-ca.pem"
-            },
-            "capabilities": ["inventory", "logs"]
-          }
-        ]
-```
+| Transport | Required values                                                                     |
+| --------- | ----------------------------------------------------------------------------------- |
+| `socket`  | Absolute in-container `path`                                                        |
+| `tls`     | `host`, `port`, absolute `caPath`; optional `certPath` and `keyPath` for mutual TLS |
+| `tcp`     | `host`, `port`, and `allowInsecure: true`                                           |
 
-The stable `id` keeps containers from different endpoints distinct. `name` is shown in the interface, and `kind` can be `docker` or `podman`. Every endpoint must include the `inventory` capability; optionally add `logs`, `lifecycle`, and `remove`. Homarr hides or disables actions the endpoint does not allow and also enforces the same capabilities on the server.
+`DOCKER_ENDPOINTS` takes precedence over the socket, hostname, and port lists.
 
-Supported transports are:
+## Use in Homarr
 
-- `socket`: an absolute in-container `path`
-- `tls`: `host`, `port`, and an absolute `caPath`; add both `certPath` and `keyPath` for mutual TLS
-- `tcp`: `host`, `port`, and the explicit acknowledgement `allowInsecure: true`
+The Docker management page lists containers from every configured endpoint and can show logs, resource use, and
+permitted lifecycle actions. The Docker widget can include all endpoints or a selected subset.
 
-:::warning[Plaintext TCP]
-Plaintext Docker TCP can grant unauthenticated control of the Docker host. Prefer a local socket, a least-privilege socket proxy, or TLS. The structured configuration refuses TCP unless `allowInsecure` is explicitly set to `true`.
-:::
+Assisted setup compares discovered containers with existing apps and integrations. Discovery is read-only; creating or
+updating a Homarr resource still requires confirmation. If one endpoint is unavailable, containers from healthy
+endpoints remain visible.
 
-When `DOCKER_ENDPOINTS` is set, it takes precedence over the legacy `DOCKER_SOCKET_PATHS`, `DOCKER_HOSTNAMES`, and `DOCKER_PORTS` variables.
+The `homarr.hide` label excludes a container. Other `homarr.*` labels can provide apps, integrations, groups, and widgets
+during onboarding; see [Docker label discovery](../docker-labels).
 
-### Managing your Docker containers within Homarr
+## Security
 
-Homarr allows you to interact with Docker containers running on your system.
-The **Service setup** section compares the visible containers with your existing Homarr apps and integrations. It keeps every service distinct by Docker endpoint and container ID, including multiple containers that use the same integration type.
+A Docker or Podman socket grants extensive host control. Prefer a least-privilege socket proxy when lifecycle access is
+not required.
 
-Homarr can show a service as:
+Homarr needs `CONTAINERS=1` for inventory and `POST=1` for standard lifecycle actions with common proxies. LSIO's proxy
+can instead expose `ALLOW_START=1`, `ALLOW_STOP=1`, and `ALLOW_RESTARTS=1` while keeping `POST=0`; removal is then
+unavailable.
 
-- **Ready to connect** when its image or name matches a supported integration
-- **New service** when it can be added as an app but no integration is recognized
-- **Already represented** or **Linked** when an app or integration already matches
-- **Address changed** when a service appears to match an integration but its reachable address has changed
-
-Suggested addresses are ranked and explain where they came from. A published address or Docker endpoint host is normally usable from a browser; a container-name address is server-only and requires Homarr to share the container network. Wildcard addresses such as `0.0.0.0` are never offered as browser destinations. You can edit every suggestion before continuing.
-
-:::info[Review before changing]
-Service discovery is read-only. Homarr never creates or changes an app or integration automatically; use the action on an individual suggestion to review and confirm its setup.
-:::
-
-Use the inbox filters to focus on services that need attention or those already represented in Homarr. Refresh runs discovery again. Dismissed suggestions are stored in the current browser using their endpoint-qualified service identity and can be restored from the same panel. If multiple existing items could match, Homarr marks the result as ambiguous and does not choose one automatically.
-
-The health badges are an evidence-based projection across Docker, integration configuration, app representation, and persisted widget links. Authentication, API request success, and widget query execution are labeled **Not observed** because Homarr does not currently retain trustworthy last-run results for these layers. Use the suggested integration test or board action to diagnose them live; **Not observed** is never presented as healthy.
-
-If one Docker endpoint is unavailable, Homarr reports that endpoint while continuing to show services from healthy endpoints. An unavailable endpoint is not treated as an empty Docker installation.
-
-Each container row has an action menu with the following options:
-
-- **View logs** - opens a dedicated logs page with a live terminal
-- **Start** - start a stopped container
-- **Stop** - stop a running container
-- **Restart** - restart a container
-- **Remove** - remove a container
-- **Add to Homarr** - create a bookmark app from the container
-
-You can also search and filter containers by **container** or **image** name:
-
-![Container and Image Search](img/container-and-image-search.png)
-
-#### Viewing container logs
-
-You can view the real-time logs of any container by selecting **View logs** from the row action menu.
-This opens a dedicated page with an xterm.js terminal that streams the container's log output.
-
-#### CPU and Memory columns
-
-The Docker management table supports optional **CPU usage** and **Memory usage** columns.
-These columns are hidden by default and can be toggled on from the table column visibility settings.
-
-#### Add apps from containers
-
-Homarr also lets you add apps from containers. You can simply select all containers you want to add an app for and then click the `Add to Homarr` button.
-This will open a dialog where you can specify the web addresses for all of them:
-
-![Dialog for addding apps to Homarr](img/add-to-homarr-dialog.png)
-
-Once you've changed the web addresses, click the `Add` button to add the apps to Homarr.
-They are then available in the app list and can be used as normally added apps.
-
-![Apps added from containers](img/add-to-homarr-apps.png)
-
-### Container labels
-
-`homarr.hide` excludes a container from the Docker Containers widget, tools page, and onboarding discovery whenever the
-label is present.
-
-During first-run onboarding, Homarr can also discover apps, integrations, groups, and compatible widgets from
-`homarr.*` labels, with Homepage labels as a fallback. See the complete [Docker label reference](/docs/integrations/docker-labels).
-
-### Security
-
-Mounting docker sockets can be risky, as they permit full control over your docker service.
-As an example, a thread actor could abuse Homarr use the socket to start, stop or delete containers on your system.
-
-Therefore we recommend the usage of a socket proxy, which can prohibit certain actions.
-A few examples include:
-
-- https://github.com/linuxserver/docker-socket-proxy
-- https://github.com/Tecnativa/docker-socket-proxy
-
-See documentation of the respective proxies on how to configure them.
-Homarr may behave in unexpected ways when you use proxies.
-
-#### Permissions
-
-Homarr needs the following permissions from the Docker API:
-
-- Containers/Start
-- Containers/Stop
-- Containers/Restart
-- Containers/Remove
-
-For socket proxies, you will need these permissions:
-
-- `CONTAINERS=1`
-- `POST=1`
-
-**Caution:** `POST` access is security critical as it provides extensive capabilities to modify your docker environment. Please leave it disabled if you're concerned about this.
-
-As a workaround, you can use [LSIO's socket proxy](https://github.com/linuxserver/docker-socket-proxy) and set the following:
-
-- ALLOW_START=1
-- ALLOW_STOP=1
-- ALLOW_RESTARTS=1
-
-These will work even with `POST=0`.
-
-You lose the ability to remove containers, but start, stop and restarts should work just fine.
-
-#### Connecting to Docker via Socket Proxies
-
-To connect to Docker via a socket proxy, you'll need to add these two environment variables in the compose file:
-
-- `DOCKER_HOSTNAMES=<name of the socket proxy container>`
-- `DOCKER_PORTS=<socket proxy port, usually 2375>`
-
-Refer: https://homarr.dev/docs/advanced/environment-variables/
-
-You will also need to add Homarr to the network of your socket proxy. You can do it like this:
-
-1. Add the network to your compose file (with appropriate changes):
-
-```yaml
-networks:
-  socket-proxy:
-    name: socket-proxy # <--- change this to the name of the network as set up by the socket proxy
-    external: true
-```
-
-2. Add the network to the homarr service in the compose file:
-
-```yaml
-networks:
-  - socket-proxy
-```
-
-3. Finally, if it is present, remove the default docker socket connection under `volumes` in the homarr service.
+Add Homarr to the proxy's Docker network and configure its service name and port with `DOCKER_HOSTNAMES` and
+`DOCKER_PORTS`.

apps/docs/docs/integrations/ical/index.mdx

@@ -8,7 +8,6 @@ import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IconZoomQuestion, IconChartBar, IconSearch } from "@tabler/icons-react";
 import { icalIntegration } from ".";
 import { calendarWidget } from "@site/docs/widgets/calendar";
 
@@ -39,6 +38,5 @@ import { calendarWidget } from "@site/docs/widgets/calendar";
   ]}
 />
 
-## Using the iCal integration
-
-The iCal integration allows you to add external calendars to Homarr. Any calendar that provides a public iCal URL can be integrated, such as Google Calendar, Apple Calendar, or Outlook.
+The integration accepts any public iCal URL, including calendars published by Google Calendar, Apple Calendar, and
+Outlook.

apps/docs/docs/integrations/immich/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Immich"
-description: "Self-hosted photo and video management solution"
+description: "Self-hosted photo and video management."
 hide_title: true
 ---
 
@@ -14,7 +14,7 @@ import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
 
 <IntegrationHeader integration={immichIntegration} categories={["Photo server"]} />
 
-### Widgets & Capabilities
+### Widgets and capabilities
 
 <IntegrationCapabilites items={[{ widget: immichAlbumCarouselWidget }, { widget: immichServerStatsWidget }]} />
 
@@ -24,34 +24,16 @@ import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
 
 ### Secrets
 
-<IntegrationSecrets secrets={[{
-  credentials: ['apiKey'],
-  steps: [
-    'Navigate to your Immich instance', 
-    'Open your account settings or navigate to https://YOUR_IMMICH/user-settings', 
-    'Scroll down to "API Keys"', 
-    'Click "New API Key"', 
-    'Enter a name, e.g. "Homarr"', 
-(
+Create an API key under **Immich user settings → API Keys** with these permissions:
 
-  <span>
+`album.statistics`, `album.read`, `album.create`, `user.read`, `user.update`, `asset.read`, `asset.view`,
+`asset.download`, `asset.statistics`, `server.statistics`, and `server.about`.
 
-    Select the following permissions:{" "}
-    <code>album.statistics</code>,{" "}
-    <code>album.read</code>,{" "}
-    <code>album.create</code>,{" "}
-    <code>user.read</code>,{" "}
-    <code>user.update</code>,{" "}
-    <code>asset.read</code>,{" "}
-    <code>asset.view</code>,{" "}
-    <code>asset.download</code>,{" "}
-    <code>asset.statistics</code>,{" "}
-    <code>server.statistics</code>,{" "}
-    <code>server.about</code>.
-
-  </span>
-
-),
-'Create the integration in Homarr and copy the API key to there'
-]
-}]} />
+<IntegrationSecrets
+  secrets={[
+    {
+      credentials: ["apiKey"],
+      steps: ["Create the API key in Immich and copy its value into the Homarr integration."],
+    },
+  ]}
+/>

apps/docs/docs/integrations/kubernetes/index.mdx

@@ -1,55 +1,33 @@
 ---
 title: "Kubernetes"
-description: "Kubernetes is a powerful container orchestration platform that automates the deployment, scaling, and management of containerized applications."
+description: "Read Kubernetes resources and cluster metrics in Homarr."
 hide_title: true
 ---
 
 import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IconBrandDocker, IconTool } from "@tabler/icons-react";
 import { kubernetesIntegration } from ".";
 
 <IntegrationHeader integration={kubernetesIntegration} categories={["Containers"]} />
 
-Homarr provides a user-friendly Kubernetes dashboard that offers an overview of your cluster’s resources in a clear and structured interface. It allows users to view key Kubernetes objects, including `Pods`, `Services`, `Ingresses`, `Nodes`, `ConfigMaps`, `Secrets`, `Namespaces`, and `Volumes`, as well as basic metrics when the Kubernetes Metrics Server is enabled.
+Homarr provides a read-only view of pods, services, ingresses, nodes, ConfigMaps, Secrets, namespaces, and volumes.
+Metrics Server is optional; without it, inventory and reserved capacity remain available but live CPU and memory do not.
 
-Docker service discovery does not convert Kubernetes resources into Homarr apps or integrations. Kubernetes remains a separate, read-only operational view, so a cluster resource is never changed or linked automatically.
+## In-cluster access
 
-:::warning[Read only]
-This integration is read-only, meaning Homarr does not modify or manage cluster resources but serves as an informational tool to enhance visibility into your Kubernetes environment.
-:::
-
-![Dashboard](img/dashboard.jpeg)
-
-### Prerequisites
-
-Before deploying Homarr in Kubernetes, ensure the following prerequisites are met:
-
-- Kubernetes (Version >= 1.24.0)
-- Metrics Server ([install from here](https://github.com/kubernetes-sigs/metrics-server)) is optional. Without it, Homarr still shows cluster inventory, node status, and reserved capacity, and identifies live CPU and memory usage as unavailable.
-- RBAC Enabled (Required for Homarr Helm chart)
-
-### Configuring RBAC in Helm Chart
-
-To enable RBAC for Homarr, configure the Helm chart values file as follows:
+Enable RBAC in the Homarr Helm values:
 
 ```yaml
 rbac:
   enabled: true
 ```
 
-:::tip[What Does rbac.enabled Do?]
-Enabling RBAC in the Helm chart creates the necessary Kubernetes Role-Based Access Control (RBAC) resources to allow Homarr to view various Kubernetes objects. These include:
+The chart creates the service account and read-only Role/ClusterRole bindings used by Homarr. Kubernetes 1.24 or newer is
+required.
 
-- Service Account: A dedicated service account for Homarr.
-- Role & RoleBinding: Grants permissions within a specific namespace to list, watch, and get pods, services, secrets, configmaps, and more.
-- ClusterRole & ClusterRoleBinding: Extends the same permissions cluster-wide for additional flexibility.
-  :::
+## Kubeconfig contexts
 
-### Multiple Kubernetes contexts
-
-When Homarr runs outside a cluster, set `KUBECONFIG` explicitly so Homarr loads the contexts from the referenced kubeconfig file or files. Mount the kubeconfig read-only and set the standard `KUBECONFIG` environment variable to its path inside the Homarr container:
+When Homarr runs outside the cluster, mount a kubeconfig read-only and set `KUBECONFIG` to its in-container path:
 
 ```yaml
 services:
@@ -60,20 +38,7 @@ services:
       KUBECONFIG: /app/config/kubeconfig
 ```
 
-The Kubernetes management pages include a context selector. The selected context is stored in the page URL, so each React Query cache entry and every API request remains context-specific. Resources with the same namespace and name in two contexts therefore remain separate.
+The management page exposes every configured context. An unavailable context does not hide healthy contexts; a context
+without Metrics Server is marked **Metrics unavailable**.
 
-Context status is checked independently. If one context is unavailable, the selector still lists healthy contexts. A context is shown as **Metrics unavailable** when its Kubernetes API is reachable but Metrics Server is not; inventory remains available without live CPU and memory usage.
-
-When Homarr runs inside Kubernetes without `KUBECONFIG`, it keeps using the in-cluster service account as the single default context.
-
-### Homarr Dashboard Overview
-
-Once deployed, Homarr provides a dashboard displaying Kubernetes metrics and resource information. The main page includes:
-
-- Pods: Lists running and pending pods.
-- Services: Shows available services and their configurations.
-- Ingresses: Displays ingress rules and associated routes.
-- Nodes: Provides an overview of cluster nodes and their status.
-- ConfigMaps & Secrets: Lists configuration data and secrets used within the cluster.
-- Namespaces: Displays all available namespaces in the cluster.
-- Volumes: Shows persistent and ephemeral storage resources.
+Kubernetes resources are not converted into Homarr apps or integrations during Docker discovery.

apps/docs/docs/integrations/opnsense/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: "OPNsense"
-description: "OPNsense is an open-source, easy-to-use, and easy-to-build firewall and routing platform."
+description: "Open-source firewall and routing platform."
 hide_title: true
 ---
 
@@ -8,22 +8,14 @@ import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IconHeartRateMonitor } from "@tabler/icons-react";
 import { opnsenseIntegration } from ".";
-import Alert from "@theme/Admonition";
 import { firewallWidget } from "../../widgets/firewall";
 
 <IntegrationHeader integration={opnsenseIntegration} categories={["Firewall"]} />
 
-### Widgets & Capabilities
+### Widgets and capabilities
 
-<IntegrationCapabilites
-  items={[
-    {
-      widget: firewallWidget,
-    },
-  ]}
-/>
+<IntegrationCapabilites items={[{ widget: firewallWidget }]} />
 
 ### Adding the integration
 
@@ -31,44 +23,18 @@ import { firewallWidget } from "../../widgets/firewall";
 
 ### Secrets
 
+Use a dedicated API-only user with **Lobby: Dashboard** and **Reporting: Traffic** privileges.
+
 <IntegrationSecrets
   secrets={[
     {
-      tabLabel: "ApiKey (Key & Secret)",
+      tabLabel: "API key and secret",
       credentials: ["opnsenseApiKey", "opnsenseApiSecret"],
-      header: (
-        <Alert type="info">
-          This integration does not require full API access to the firewall. The following guide outlines the process
-          for creating a restricted OPNsense user with a scrambled password, designed exclusively for API access. This
-          ensures minimal permissions and prevents local login capability.
-        </Alert>
-      ),
       steps: [
-        "Log in to the OPNsense web interface as an administrator",
-        "Navigate to System → Access → Users",
-        "Click the + (Add) button to create a new user",
-        <>
-          Fill in the user details:
-          <ul>
-            <li>Username: Enter a unique name</li>
-            <li>Password: Leave empty</li>
-            <li>Scrambled Password: Enable this option</li>
-            <li>Full name: (Optional) Add a descriptive name</li>
-          </ul>
-        </>,
-        <>
-          In Privileges section → Select the option below:
-          <ul>
-            <li>Lobby: Dashboard</li>
-            <li>Reporting: Traffic</li>
-          </ul>
-        </>,
-        "Click Save",
-        "Return to the Users list",
-        "Find the user and click the ticket icon in the Commands column",
-        "Click Yes in the popup to confirm",
-        "A txt file will download automatically, containing: Key and Secret",
-        "Save this file securely—this information will only be shown once",
+        "Under System → Access → Users, create a user with Scrambled Password enabled.",
+        "Grant Lobby: Dashboard and Reporting: Traffic privileges, then save the user.",
+        "Use the ticket action for that user and confirm the API key download.",
+        "Copy the downloaded key and secret into Homarr.",
       ],
     },
   ]}

apps/docs/docs/integrations/pi-hole/index.mdx

@@ -8,7 +8,6 @@ import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IconAd, IconDeviceGamepad } from "@tabler/icons-react";
 import Alert from "@theme/Admonition";
 import { dnsHoleSummaryWidget } from "@site/docs/widgets/dns-hole-summary";
 import { dnsHoleControlsWidget } from "@site/docs/widgets/dns-hole-controls";
@@ -44,7 +43,7 @@ import { piHoleIntegration } from ".";
     {
       credentials: ["apiKey"],
       steps: [],
-      body: "Please note, that in v6 of Pi-hole you no longer specify an API key, but instead either a password or application password. We suggest to use the application password when possible.",
+      body: "Pi-hole v6 uses a password or application password instead of an API key. Prefer an application password.",
     },
     {
       credentials: [],

apps/docs/docs/integrations/proxmox/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Proxmox"
-description: "Proxmox is a powerful open-source virtualization platform that allows you to run virtual machines and containers."
+description: "Virtual machines and containers managed by Proxmox VE."
 hide_title: true
 ---
 
@@ -8,15 +8,12 @@ import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IconHeartRateMonitor } from "@tabler/icons-react";
 import { proxmoxIntegration } from ".";
-import Alert from "@theme/Admonition";
 import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
-import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
 
 <IntegrationHeader integration={proxmoxIntegration} categories={["System monitoring"]} />
 
-### Widgets & Capabilities
+### Widgets and capabilities
 
 <IntegrationCapabilites items={[{ widget: healthMonitoringWidget }]} />
 
@@ -26,81 +23,23 @@ import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
 
 ### Secrets
 
+Use a Proxmox VE (`pve`) user and API token with the `PVEAuditor` role at `/` and **Propagate** enabled. PAM
+authentication may not work with the API.
+
 <IntegrationSecrets
   secrets={[
     {
-      header: (
-        <Alert type="caution">
-          The Proxmox API may not work with Linux PAM standard authentication. It is strongly recommended to use the
-          Proxmox VE authentication server realm when creating your API user.
-        </Alert>
-      ),
       credentials: ["username", "tokenId", "realm", "apiKey"],
       steps: [
-        "Navigate to the Proxmox portal, click on Datacenter",
-        "Expand Permissions, click on Groups",
-        "Click the Create button",
-        "Name the group something informative, like api-users",
-        "Click on the Permissions 'folder'",
-        <>
-          Click Add {"->"} Group Permission
-          <ul>
-            <li>Path: /</li>
-            <li>Group: group from Step 4 above</li>
-            <li>Role: PVEAuditor</li>
-            <li>Propagate: Checked</li>
-          </ul>
-        </>,
-        "Expand Permissions, click on Users",
-        <>
-          Click the Add button
-          <ul>
-            <li>User name: something informative like api</li>
-            <li>Realm: Proxmox VE authentication server</li>
-            <li>Password: create a secure password for the user</li>
-            <li>Confirm Password: re-enter the password</li>
-            <li>Group: group from Step 4 above</li>
-          </ul>
-        </>,
-        "Expand Permissions, click on API Tokens",
-        <>
-          Click the Add button
-          <ul>
-            <li>User: user from Step 8 above</li>
-            <li>Token ID: something informative like the application or purpose like homarr</li>
-            <li>Privilege Separation: unchecked</li>
-          </ul>
-        </>,
-        "Copy the Secret that is shown in Step 10 because it is only shown once",
-        "Go back to the 'Permissions' menu",
-        <>
-          Click Add {"->"} API Token Permission
-          <ul>
-            <li>Path: /</li>
-            <li>API Token: select the API token created in Step 10</li>
-            <li>Role: PVE Auditor</li>
-            <li>Propagate: Checked</li>
-          </ul>
-        </>,
+        "Create a Proxmox VE user or group and grant PVEAuditor at / with Propagate enabled.",
+        "Create an API token for that user. Disable privilege separation to inherit the user permission, or grant the token the same PVEAuditor permission.",
+        "Copy the token secret when Proxmox displays it and enter the user, realm, token ID, and secret in Homarr.",
       ],
       body: (
-        <>
-          <span>
-            Sometimes you'll also find the <code>api@pve!homarr</code> format, within Homarr you'll have to split it up
-            into:
-          </span>
-          <ul>
-            <li>
-              <b>Username:</b> api
-            </li>
-            <li>
-              <b>Realm:</b> pve
-            </li>
-            <li>
-              <b>Token ID:</b> homarr
-            </li>
-          </ul>
-        </>
+        <p>
+          For <code>api@pve!homarr</code>, use username <code>api</code>, realm <code>pve</code>, and token ID{" "}
+          <code>homarr</code>.
+        </p>
       ),
     },
   ]}

apps/docs/docs/management/api/index.mdx

@@ -6,98 +6,52 @@ tags:
   - Interface
 ---
 
-Using the Homarr API, you can interface with the application with your own code and business logic.
-It enables you to trigger almost all actions that you can perform from the Homarr UI.
-With the API, you can build resilient systems that automatically update Homarr with data - for example syncing it with
-your deployments in a cluster or dynamically adding integrations depending on how many replicas you run.
+Homarr exposes OpenAPI and tRPC endpoints for automation. Open the generated specification under
+**Management → Tools → API** or use the [interactive API reference](/api-reference).
 
-This page is language-neutral, and you must implement the API on your own in your desired language.
-It requires you to know your programming language well and have a basic understanding of HTTP, JSON and networking.
-You can test out API endpoints using any OpenAPI client - for example [Yaak](https://yaak.app/).
-
-## Opening the API specification
-
-The specification is implemented according to the OpenAPI standard.
-To access the documentation, you'll need to spin up an instance of Homarr.
-Navigate to `Management` > `Tools` > `API`.
-You can copy the JSON url into your OpenAPI client or try out the endpoints directly from your browser.
-
-Alternatively, you can [open the full interactive API reference](/api-reference) directly in your browser.
+![Homarr's API documentation page](../img/api.png)
 
 ## Authentication
 
-Many endpoints will require you to authenticate. At the top of the API reference, you'll find a button to authenticate yourself with an API key.
-You can obtain API keys from the "Authentication" tab at the top of the page.
-API keys will not expire and can be used indefinitely.
+Create an API key from the **Authentication** tab. Its value has the form `<id>.<token>` and is shown once.
 
-### API Key Format
+Send it in the `ApiKey` header:
 
-API keys are provided in the format `<id>.<token>`. When making requests, include the key in the `ApiKey` header:
-
-```
-ApiKey: abc123def456.xyz789tokenvalue...
+```sh
+curl -H 'ApiKey: <id>.<token>' https://homarr.example.com/api/health/live
 ```
 
-### Supported Endpoints
+The same header authenticates tRPC requests under `/api/trpc`. Without a key, browser requests can use the Homarr
+session cookie.
 
-API key authentication works with both endpoint types:
+API keys do not expire automatically and act as the user that created them. Every request uses that user's group and
+resource permissions.
 
-| Endpoint Type | Path Pattern    | API Key Support |
-| ------------- | --------------- | --------------- |
-| OpenAPI       | `/api/...`      | ✅ Supported    |
-| tRPC          | `/api/trpc/...` | ✅ Supported    |
+## Permission behavior
 
-If no API key is provided, Homarr falls back to session cookie authentication (for browser-based access).
+Unauthorized operations return `FORBIDDEN`. List endpoints filter records on the server when resource-specific access
+applies.
 
-### Usage Examples
+App catalog endpoints such as `app.all`, `app.getPaginated`, and `app.search` require **Modify all apps** because they
+include internal URLs. Use `app.selectable` for the reduced board-picker fields.
 
-**OpenAPI endpoint:**
+Integration list and search endpoints return only integrations the key owner can access. Check each integration's
+`hasUseAccess` and `hasInteractAccess` fields before reading data or invoking actions.
 
-```bash
-curl -H 'ApiKey: <id>.<token>' http://localhost:7575/api/health/live
-```
+## Board automation
 
-**tRPC endpoint:**
+The API can create, duplicate, rename, delete, and configure boards; manage board content; and set desktop or mobile home
+boards.
 
-```bash
-curl -H 'ApiKey: <id>.<token>' http://localhost:7575/api/trpc/app.all
-```
+Each board has exactly one Mobile and one Base layout. Mobile uses breakpoint `0`; all breakpoints are unique. Custom
+layouts can use any other breakpoint, and Homarr selects the highest breakpoint that fits the viewport. Preserve layout
+roles and use the canonical layouts returned by save operations, including generated IDs.
 
-### Use Cases
+Creating or changing an integration-backed widget requires use access to each newly selected integration.
 
-API key authentication enables programmatic access for:
+## Docker targets
 
-- Automation scripts and CI/CD pipelines
-- Third-party integrations
-- Custom dashboards and monitoring tools
-- Container orchestration systems that need to sync app definitions
-
-## Board Automation
-
-The OpenAPI and MCP APIs include board management endpoints for common automation workflows:
-
-- Create, duplicate, rename and delete boards
-- Change board visibility
-- Update board visual and behavior settings
-- Set desktop and mobile home boards for the current user
-- Configure global board defaults such as public home boards and status behavior
-
-Board layout responses identify each layout with a `mobile`, `base`, or `custom` role. Mobile and Base are protected. Layout-saving clients must preserve existing roles, keep Mobile at breakpoint `0`, keep Base as the highest breakpoint, and use unique custom breakpoints between them. The layout save operation returns the canonical saved layouts, including server-generated IDs for new custom layouts. A non-Base layout can be regenerated from Base with the protected reset operation.
-
-Use the interactive API reference to inspect the exact request body for each endpoint under the `boards` and `settings` tags.
-
-## Docker action payload migration
-
-Docker lifecycle and removal actions now identify each container with both its Docker endpoint and container ID. This is a
-breaking change for tRPC and MCP clients that previously sent an `ids` array to the start, stop, restart, or remove action.
-
-Replace the old payload:
-
-```json
-{ "ids": ["container-id"] }
-```
-
-with endpoint-qualified targets:
+Docker actions identify both the configured endpoint and the container:
 
 ```json
 {
@@ -105,38 +59,21 @@ with endpoint-qualified targets:
 }
 ```
 
-Read `endpointId` and `id` from `docker.getContainers` (MCP tool `docker_getContainers`) immediately before the action.
-Pass those pairs unchanged to `docker.startAll`, `docker.stopAll`, `docker.restartAll`, or `docker.removeAll`; their MCP tool
-names use underscores, such as `docker_restartAll`. Endpoint qualification prevents identical container IDs on different
-Docker or Podman endpoints from targeting the wrong service.
+Read both values from `docker.getContainers` immediately before calling `docker.startAll`, `stopAll`, `restartAll`, or
+`removeAll`. The endpoint ID prevents collisions between Docker or Podman hosts.
 
-## Partial integration failures
+`docker.getContainers` accepts optional `endpointIds`. Omit it or pass an empty array for every configured endpoint.
 
-Multi-integration widget queries keep data from integrations that remain available. Calendar and media-server results include
-an optional `error` on a failed integration; media-request responses expose a `failedIntegrations` array, and the latest
-requests endpoint returns its items in `requests`. When every selected integration fails, the query returns an error instead
-of a partial response.
+## Partial upstream failures
 
-Other widgets use the same settlement pattern with endpoint-specific shapes: a failed integration may appear as a named
-fallback row, in a failure array, or be omitted while healthy results remain. Widget pages should identify the shape they
-render rather than assuming every query exposes an `error` field.
+Queries that combine several integrations can return healthy data alongside failure metadata. The exact response shape
+depends on the endpoint; inspect the generated schema instead of assuming a common `error` field. When every selected
+integration fails, the query returns an error.
 
-### Saving dashboard layouts
+## Custom Widget resources
 
-The dashboard editor saves item positions and sections as one board update.
-Canvas height follows its content automatically and does not require a separate API setting.
-Responsive layouts store optional left and right gutter widths from zero to three columns.
-Gutter columns are reserved from the layout's total column count, and changing them reflows affected items.
+Authenticated administrators can retrieve the current Custom Widget authoring prompt, schema, component catalog, skill,
+and focused references under `/api/custom-widgets/`.
 
-## Get Custom Widget authoring resources
-
-Custom JSX v2 provides four HTTP discovery endpoints:
-
-- `GET /api/custom-widgets/authoring-prompt` returns the current prompt plus MCP and HTTP resource identifiers.
-- `GET /api/custom-widgets/schema` returns the canonical widget JSON Schema.
-- `GET /api/custom-widgets/components` returns the release-matched static component catalog.
-- `GET /api/custom-widgets/skill` returns the concise live `SKILL.md` plus skills.sh, source, and install metadata. Retrieve the schema, component catalog, and examples through their dedicated resources only when needed.
-
-Call `customWidget_configurationRequestUser` to create a temporary API source setup URL where the user can confirm their server URL and enter credentials. Do not construct or save this URL.
-
-Authenticated tRPC and MCP procedures support definition management, validation, previews, template patches, and credential writes. An exported definition does not contain credentials.
+Use [Custom Widget agent authoring](../custom-widgets/agent-authoring) for the lifecycle and
+[MCP](../mcp) when the client supports Model Context Protocol.

apps/docs/docs/management/apps/index.mdx

@@ -7,50 +7,39 @@ tags:
   - Ping
 ---
 
-Apps are the building blocks of your Homarr board.
-Most of the time they are a simple link to a website, but used on your board they also support a simple ping to check if your service is up.
-Apps are used in the bookmark and app widget.
+import { AppFlowDiagram } from "@site/src/components/pages/core-concepts/technical-diagrams";
 
-## Create an app
+An **app** is a saved shortcut used by the App and Bookmarks widgets. It contains a name, destination, icon, and
+optional status-check address.
 
-To create an app you can click on the button on the top right of the apps management page:
+![The Apps management page](../img/apps.png)
 
-![New app button](./img/new-app-button.png)
+## How an app is used
 
-Next, you'll need to fill out the required fields to configure the app:
+<AppFlowDiagram />
 
-![New app form](./img/new-app-form.png)
+## Configuration
 
-### Name
+Create and manage apps under **Management → Apps**.
 
-The name must be at least one character long and can be chosen freely.
+| Field       | Purpose                                                                                  |
+| ----------- | ---------------------------------------------------------------------------------------- |
+| Name        | Label shown on the board                                                                 |
+| Icon URL    | Direct image URL, icon-library result, or uploaded image                                 |
+| Description | Optional tooltip                                                                         |
+| URL         | Destination opened from the board; custom URI schemes are supported except `javascript:` |
+| Ping URL    | Optional HTTP(S) address used for status checks when it differs from the destination     |
 
-### Icon URL
+An app can be linked to an [integration](../integrations). Integration widgets then use the app as their destination
+when they provide a link to the service.
 
-This is the URL to the icon that will be displayed on the app widget.
-You can paste a direct HTTP(S) URL to an image, search the included icon repositories by name, or upload a local file through the upload button. The app name is pre-filled as the initial library search when no image is selected. Local images appear first, followed by SVG icons and other formats. Direct image URLs are previewed, used as entered, and are not searched in the icon repositories.
+See [Icons](/docs/advanced/icons) for icon sources and uploads.
 
-![Icon URL](./img/app-icon-url.png)
+## Permissions
 
-### Description
+- `app-create` creates apps.
+- `app-modify-all` lists and edits every app.
+- `app-full-all` also deletes and uses every app.
+- `app-use-all` allows using every app on boards without granting management access.
 
-An optional description that can be shown as tooltip on the app widget.
-
-### URL
-
-The URL to the website you want to link to. Clicking on the app widget or bookmark will open this URL.
-
-You can also use custom URI schemes such as `vscode://file/path`, `microsoft-edge:https://example.com`, or `myapp://open` to link to local applications or third-party programs. We trust that you know what you are doing — only `javascript:` URIs are blocked for security reasons.
-
-### Ping URL
-
-When you want to use another url for the simple status check you can set it here.
-This will allow you to set a different URL for the ping than the URL that is opened when clicking on the app widget.
-It's useful when you want to ping the service internally for example with a custom ip but open the website externally.
-Note that the ping URL only accepts `http://` and `https://` URLs — custom URI schemes are not supported for pings.
-
-## List of apps
-
-On the apps management page you find all apps that exist in your Homarr instance. Search by name or URL, open an app directly, or use its row actions to edit and delete it. A filtered search can be cleared without leaving the page.
-
-Any signed-in user can view this list. Creating, editing, and deleting apps requires the corresponding app permission; board permissions are not required.
+Users with only `app-create` can open the page and create an app, but do not receive the existing app list.

apps/docs/docs/management/assistant.mdx

@@ -1,68 +1,58 @@
 ---
-description: Configure and use Homarr Assistant.
+description: Configure and use Assistant.
 tags:
   - Assistant
   - AI
   - Administration
 ---
 
+import { AssistantFlowDiagram } from "@site/src/components/pages/core-concepts/technical-diagrams";
+
 # Assistant
 
-Homarr Assistant can answer questions and manage Homarr for you. It uses the signed-in user's permissions and asks for
-approval before making changes.
+Assistant answers questions and operates Homarr through the signed-in user's permissions. Read-only tools can run
+automatically; changes require approval by default.
 
-![Homarr Assistant conversation with suggested prompts](/img/assistant/conversation.png)
+![The Assistant management page](./img/assistant.png)
 
-## Set it up
+## Request flow
 
-Open **Management → Assistant**.
+<AssistantFlowDiagram />
 
-![Assistant provider, credentials, and model configuration](/img/assistant/configuration.png)
+## Configuration
 
-1. Select a provider and check its API URL.
-2. Enter an API key when required, then save the connection.
-3. Refresh the model list and select a model.
-4. Enable the assistant and save.
+Under **Management → Assistant**, select a provider, configure its API URL and key when required, select the default
+model, and enable Assistant. Users can choose another available model for a conversation.
 
-Choose a provider preset or use **Custom endpoint** with an OpenAI-compatible Chat Completions API. The
-[Homarr provider](../workshop/homarr-provider) is the default and needs no administrator API key. The Homarr team pays
-for a limited number of Assistant uses for each user every day; users sign in to the Community Workshop to use them.
+Provider presets cover common APIs. **Custom endpoint** accepts an OpenAI-compatible Chat Completions API. For a model
+server outside the Homarr container, use a hostname that the container can resolve instead of `localhost`.
 
-:::info Local model servers
+The [Homarr provider](../workshop/homarr-provider) is available through the Community Workshop without an administrator
+API key and has a daily request allowance.
 
-Inside a container, `localhost` means the Homarr container. Use the model server's container name, local DNS name, or
-host gateway address.
+## Access
 
-:::
+Open Assistant from the user menu, with `Shift+A`, from search with `Cmd/Ctrl+/`, or through the
+[Assistant widget](../widgets/assistant).
 
-## Use it
+Assistant can work with boards, apps, integrations, widgets, Custom Widgets, and supported connected services. Mention
+Homarr resources with `@`; the model loads additional live context only when needed.
 
-- Select **Assistant** in the user menu or press `Shift + A`.
-- Ask from `Cmd/Ctrl + K`.
-- Add the [Assistant widget](../widgets/assistant) to a board.
+Conversations are stored per user and can be searched, renamed, exported, or deleted.
 
-The assistant can work with boards, apps, integrations, widgets, Custom Widgets, and connected services. Use `@` to
-add Homarr items as context, `/` for shortcuts, and the paperclip for supported files.
+## Permissions and data
 
-Each request includes the user's name, current page and board, home board, server time, browser time zone, and a small
-summary of accessible Homarr resources. Live status is fetched only when needed.
+- Every tool call uses the current user's Homarr permissions.
+- Automatic approvals apply only to the current conversation and reset when switching conversations.
+- Provider keys and custom headers are encrypted and are not returned to the browser.
+- Prompts, attachments, tool definitions, and tool results are sent to the selected model provider.
 
-## Permissions and privacy
-
-- Read-only actions can run automatically. Changes require approval.
-- Homarr permissions apply to every tool call and mentioned item.
-- API keys and custom headers are encrypted and never returned to the browser.
-- Conversations are stored per user and can be exported or deleted.
-
-Prompts, attachments, tool definitions, and tool results are sent to the selected model provider. Review that
-provider's privacy policy before enabling the assistant.
+See [MCP](./mcp) to connect an external AI client and
+[Custom Widget agent authoring](./custom-widgets/agent-authoring) for widget generation.
 
 ## Troubleshooting
 
-- **No models found:** check the base URL, model discovery path, and API key. You can enter a model ID manually.
+- **No models found:** check the API URL, discovery path, and API key, or enter a model ID manually.
 - **Assistant is unavailable:** enable it and save the configuration.
-- **Tool calls stop:** select a model that supports streaming and tool calls.
-- **Local endpoint is unreachable:** check container networking and the server's listen address.
-
-See [MCP](./mcp) for external AI clients and [Custom Widget agent authoring](./custom-widgets/agent-authoring) for the
-widget authoring workflow.
+- **Tool calls stop:** use a model that supports streaming and tool calls.
+- **Local endpoint is unreachable:** check container DNS, routing, and the model server's listen address.

apps/docs/docs/management/backup.mdx

@@ -6,78 +6,34 @@ tags:
   - Data
 ---
 
-# Backup & Restore
+# Backup and restore
 
-Homarr provides a built-in backup and restore system for **SQLite** instances. You can export your entire database - including apps, integrations, boards, users, and encryption keys - as a ZIP archive, and restore it on the same or a different Homarr instance.
+Administrators using SQLite can export and restore the complete Homarr database under
+**Management → Tools → Backup**. MySQL and PostgreSQL installations must use their database-native backup tools.
 
-:::warning
+![The Backup and restore management page](./img/backup.png)
 
-Backup and restore is only available when using the **SQLite** database driver. MySQL and PostgreSQL instances do not show this page.
+## Export
 
-:::
+The ZIP contains:
 
-## Accessing the Backup Page
+| File            | Contents                                                    |
+| --------------- | ----------------------------------------------------------- |
+| `db.sqlite`     | Apps, integrations, boards, users, settings, and other data |
+| `metadata.json` | Homarr version, backup timestamp, and encryption metadata   |
 
-Navigate to `Management` → `Tools` → `Backup`. You must have **admin** permissions to access this page.
+Export requires typing `I understand`. Store the ZIP as sensitive data: it contains the database and the material
+needed to restore encrypted integration credentials.
 
-## Exporting a Backup
+## Restore
 
-![Export database card with the Download Backup action](/img/backup/export-database.png)
+Select a Homarr backup ZIP. The browser previews entity counts, board names, and required database migrations before
+the archive is uploaded.
 
-Click the **Export** button in the export card. You'll be prompted to type `I understand` to confirm. Once confirmed, a ZIP file downloads containing:
+Restoring replaces the current SQLite database and cannot be undone. After a successful restore, the Next.js process
+restarts and the page reloads when Homarr is ready.
 
-| File            | Description                                                         |
-| --------------- | ------------------------------------------------------------------- |
-| `db.sqlite`     | Full SQLite database with all entities                              |
-| `metadata.json` | Backup metadata: Homarr version, creation timestamp, encryption key |
+A backup can be restored on another Homarr instance. When its `SECRET_ENCRYPTION_KEY` differs, Homarr re-encrypts stored
+integration secrets for the target instance. Version metadata is used to apply compatible migrations.
 
-The backup contains the complete database. It includes Custom Widgets and all other Homarr configuration.
-
-## Restoring a Backup
-
-![Restore database card with the backup ZIP drop zone](/img/backup/restore-database.png)
-
-### 1. Upload
-
-Drag and drop or select a `.zip` backup file. The import card validates that the file contains a valid `db.sqlite` and metadata.
-
-### 2. Preview
-
-Before restoring, Homarr uses **sql.js WASM** to analyze the backup directly in your browser. You'll see:
-
-- **Entity counts** - how many apps, integrations, boards, users, etc. are in the backup
-- **Board names** - which boards will be restored
-- **Migration status** - Drizzle migrations are applied in-browser with a visual timeline showing each migration step
-
-### 3. Confirm
-
-Type `I understand` to acknowledge that restoring will replace your current database. This cannot be undone.
-
-During first-run onboarding, the database is still empty, so the restore preview goes directly to **Restore Database**
-without the extra typed confirmation. After Homarr restarts, onboarding opens the restored default home board.
-
-### 4. Restore
-
-The backup ZIP is sent to the server, validated, and applied. After a successful restore:
-
-- **The Next.js server restarts automatically** to reload the new database state
-- Nginx and Redis (if running in Docker) stay up - only the Next.js process restarts
-- The page reloads once the server is ready
-
-## Cross-Instance Restore
-
-You can restore a backup from one Homarr instance onto another. Homarr handles:
-
-- **Encryption key re-encryption** - If the target instance has a different `SECRET_ENCRYPTION_KEY`, integration secrets are decrypted with the old key and re-encrypted with the new one during import
-- **Version compatibility** - Backups include the Homarr version they were created with. Backward compatibility is maintained for older backup formats
-
-## Backup During Onboarding
-
-When setting up a new SQLite Homarr instance, the onboarding flow includes a **Restore from SQLite backup** step. You can upload a backup ZIP directly during onboarding to skip manual setup.
-
-## Security
-
-- Export requires admin permissions
-- The `I understand` confirmation dialog prevents accidental exports and overwrites
-- Backups contain encrypted integration secrets - they cannot be read without the `SECRET_ENCRYPTION_KEY`
-- Import only works on SQLite instances - the API routes refuse requests from MySQL/PostgreSQL instances
+The same restore flow is available during first-run onboarding, before the target database contains user data.

apps/docs/docs/management/boards/index.mdx

@@ -9,459 +9,86 @@ tags:
   - Layout
 ---
 
-import iconColorImage from "./img/icon-color.png";
-import itemRadiusImage from "./img/item-radius.png";
-import layoutSettingsImage from "./img/layout-settings.png";
-import layoutSettingsCustomRailsImage from "./img/layout-settings-custom-rails.png";
-import boardViewModeImage from "./img/board-view-mode.png";
-import boardEditModeImage from "./img/board-edit-mode.png";
-import keyboardTileEditingImage from "./img/keyboard-tile-editing.png";
+import { BoardLayoutsDiagram } from "@site/src/components/pages/core-concepts/technical-diagrams";
 
-Each dashboard is called a "board".
-You can create as many boards as you want.
-Boards can be restricted to user groups.
-A user may also have a "home board" which they will see at the root path (e.g. my-homarr.com or my-homarr.com/boards).
-Other boards can be viewed by direct links (e.g. my-homarr.com/boards/smart-home) or via the management pages.
-The management page includes a compact structural preview of each board's Base layout so you can recognize it before
-opening it. Containers include their visible widgets and app icons instead of appearing empty.
+A **board** is a dashboard page containing apps, widgets, and Containers. Its name is unique and forms the board URL.
+Boards can be public or restricted to users and groups.
 
-Names of boards must be unique because this will be used in the URL to load the desired board.
+![The Boards management page](../img/boards.png)
 
-## Create a new board
+Create, duplicate, open, and delete boards under **Management → Boards**. Press `Shift+C` from a board to open the
+board switcher.
 
-When creating a board, the availability of the board name will be checked for you.
+## Responsive layouts
 
-![](./img/create-board-modal.png)
+<BoardLayoutsDiagram />
 
-### Name
+Mobile and Base are protected layouts. New boards use three Mobile columns; Base uses the column count selected at
+creation. Additional layouts use unique breakpoints. Homarr selects the layout with the highest breakpoint that fits
+the current viewport.
 
-The name must not include any special characters and must be at least one character long.
-Underscores and hyphen-minus are allowed.
-
-### Column count
-
-The column count defines how many fixed-width cells are available in each row.
-One cell contains a `200 × 200` logical-pixel tile.
-Homarr scales the whole board uniformly instead of changing widget proportions, and always fits it to the available width without horizontal scrolling.
-The main canvas and enabled rails stay at least one viewport tall, and the canvas grows automatically while you drag or resize items near its lower edge.
-
-### Public
-
-This will enable public access for everyone - regardless of whether they are logged in or not.
-This can be really useful if you want to have public boards in your company or for family and friends.
-Modifications for public boards must be allowed explicitly using user groups and their permissions.
-
-## Board settings
-
-You navigate to the board settings by clicking on these three dots:
-
-![](./img/navigate-to-settings.png)
-
-Alternatively, you can also navigate from the board page itself using the cog icon at the top right:
-
-![](./img/navigate-to-settings-2.png)
-
-All board settings are edited on a single page. Click the **Save changes** button in the save bar at the bottom to apply them, or **Discard** to restore the last saved values. The save bar only appears when you have unsaved changes. Access control and the Danger zone are independent sections and are applied immediately.
-
-### General
-
-#### Page title
-
-This is the title that will be visible at the top left in the navigation bar:
-
-![](./img/page-title.png)
-
-This field is optional and Homarr will fall back to "Homarr" if nothing is set.
-
-#### Meta title
-
-This is the secondary title of the page that is not directly visible in the page itself.
-Browser will use it to set the title of tabs:
-
-![](./img/meta-title.png)
-
-Homarr will fall back to the board name and a suffix if nothing is set.
-
-#### Logo image URL
-
-This is the URL that is used for the image at the top left.
-Homarr will fall back to the Homarr logo if nothing is set.
-
-#### Favicon image URL
-
-This is the URL that is used for the favicon in the tab title.
-Homarr will fall back to the Homarr logo if nothing is set.
-
-### Layout
-
-In this section you can configure the different responsive layouts. Homarr selects the layout with the highest breakpoint that is not wider than the current screen, then scales its complete fixed-size canvas uniformly.
-
-<img
-  src={layoutSettingsImage}
-  alt="Board settings showing protected Mobile and Base responsive layouts with rail controls"
-  style={{ maxWidth: "100%" }}
-/>
-
-The layout cards show the representative geometry used for planning. This current example also shows a custom layout
-with both fixed rails enabled; the rails reserve columns and the remaining canvas reflows automatically.
-
-<img
-  src={layoutSettingsCustomRailsImage}
-  alt="Board layout settings with a custom layout and both fixed rails enabled"
-  style={{ maxWidth: "100%" }}
-/>
-
-Every board has two protected layouts. Creating a board adds **Mobile** at `0px` with three columns and **Base** at
-`768px` with the column count you choose. Both layouts can be edited, but neither can be removed.
-
-Every `1 × 1` tile has a `200 × 200` logical-pixel content area.
-The `24` logical-pixel gap between tiles is separate from that size.
-A `2 × 1` tile therefore contains two fixed cell widths plus the gap between them.
-Widgets see their logical size, while the board's visual scale makes the complete layout larger or smaller.
-When fitting below 100%, Homarr keeps widget typography and control density at their normal readable size.
-On larger canvases, the complete board grows together like browser zoom.
-The complete canvas always fits the available width and never adds horizontal board scrolling.
-
-- **Mobile** starts at `0px` and uses three columns on new boards.
-- **Base** is the widest layout and starts at `768px` on new boards.
-
-Mobile and Base can be renamed and their column counts can be changed, but they cannot be removed. Mobile has no fixed
-rails; rail configuration is available only on Base and custom layouts. You can add removable custom layouts between
-their breakpoints.
-
-Each layout stores independent positions and sizes. Moving or resizing a widget while editing Mobile does not move it in
-Base or any custom layout. New custom layouts start from Base's current column count and rail widths; Homarr chooses a
-free breakpoint between Mobile and Base, and you can then change the breakpoint, columns, and rails.
-
-Older or incomplete boards are repaired automatically. A board with no layouts receives Mobile at `0px` with three
-columns and Base at `768px` with ten columns. A board with one layout keeps it as Base and receives a generated Mobile
-layout. With multiple layouts, the narrowest becomes Mobile, the widest becomes Base, and intermediate layouts remain
-custom. Duplicate or out-of-order breakpoints are normalized without discarding saved positions.
-
-Use **Reset from Base** on Mobile or a custom layout to replace all of its positions and sizes with a newly generated version of Base. The layout's name, breakpoint, and column count are kept.
-
-The canvas is at least one window tall, even when it is empty.
-Its left and right edges are hard drag boundaries, while its bottom edge extends automatically as a tile is dragged or resized downward.
-Nested Containers keep their own resizable bounds.
-New items use their widget's default size and new Containers use a useful `4 × 3` size when space allows.
-
-#### Name
-
-The name of the layout can be chosen freely. It is only used for management and is not displayed on the board.
-
-#### Column count
-
-The total number of columns in the layout. Changing it projects the saved positions and sizes into the new grid width without overlap.
-
-#### Fixed rails
-
-Each responsive layout can enable a fixed left rail, a fixed right rail, or both.
-Set a rail width to zero to disable it for that layout.
-Choose a width from one to three columns with the three-step slider.
-The preview shows how much space remains for the main canvas.
-
-Rail columns are reserved from the layout's total column count.
-For example, a 12-column layout with a two-column left rail leaves ten columns for the canvas.
-The combined rail widths cannot consume the final main-canvas column.
-Enabling or widening a rail reflows canvas items into the remaining columns.
-Disabling a rail moves its contents back into the next available canvas positions.
-
-Rails fill the available window height and remain fixed while the page scrolls. They do not grow or scroll independently.
-Apps, widgets, and Containers inside them still use the same fixed `200 × 200` cells and can be rearranged in edit mode, where each rail shows its name and boundary.
-
-#### Breakpoint
-
-The minimum screen width where the layout is used; a layout is eligible at its breakpoint and above. Mobile is fixed at
-`0px`. Custom breakpoints must be unique and sit between Mobile and Base. Base must remain the highest breakpoint.
-When the initial viewport is not available, Homarr uses its remembered viewport information, client hints, or User-Agent
-fallback to select a layout.
-
-#### View and edit modes
-
-View mode renders a static board without executing the drag-and-drop editor.
-After the board is interactive, Homarr prepares the editor in the background for users who can modify it.
-Entering edit mode keeps the static board visible until that preparation finishes, then enables collision-aware movement and resizing.
-Collapsed Containers are expanded while editing so their contents and controls are reachable.
-
-<img
-  src={boardViewModeImage}
-  alt="A Homarr board in view mode with the dashboard canvas and static widgets visible"
-  style={{ maxWidth: "100%" }}
-/>
-
-Widget content is inert in edit mode, so dragging from the inert widget area moves the tile instead of activating the widget;
-settings and other controls remain usable in the compact header above the tile.
-A single compatible collision can swap two items when both resulting placements fit, including different-sized or lateral moves.
-For other collisions, or when a tile grows into occupied space, nearby tiles are compacted out of the way and collision chains reflow.
-The visible corner controls provide a 44-pixel resize target, and edge controls appear on hover for horizontal or vertical resizing.
-Resize handles stop at the tile's minimum allowed size while the pointer is still moving.
-Use the pencil button in the board header to enter edit mode; click it again to save. If you leave the page with unsaved
-changes, Homarr asks whether to discard them. If the editor cannot load, the board remains in view mode.
-
-<img
-  src={boardEditModeImage}
-  alt="Board in edit mode with the board header controls and editable dashboard tiles visible"
-  style={{ maxWidth: "100%" }}
-/>
-
-While edit mode is active, **Add board content** opens the same Universal Create surface as the global header action and
-Spotlight. It can add a widget, app, integration, Container, board, Workshop item, or Custom Widget when the
-current user and context allow it. Widget setup offers the main canvas, enabled rails, and existing Containers as
-destinations before the widget is created, so the common flow does not require a second move step.
-
-The widget editor also lists its selected integrations. Users with full access can choose **Edit connection** to test,
-diagnose, and repair an integration without leaving the board. A successful repair refreshes the affected widget; the
-saved integration changes apply everywhere that connection is used.
-
-Pointer users can drag from the inert widget area; interactive controls are excluded. Containers use the grab button at their top-left corner.
-Widgets can be resized from any edge or corner handle. Activate a Container's chrome with its top-left grip before using
-its resize handles.
-On a touch screen, press and hold a tile for about `200 ms` before moving it; a quick tap does not start a drag. Resize
-handles support direct touch input.
-Keyboard users can focus a tile, press Enter or Space to start editing, use the arrow keys to move it, and use Shift plus the arrow keys to resize it.
-Press Enter, Space, or Escape to stop keyboard editing.
-Keyboard moves and resizes apply immediately within the current canvas, rail, or Container; they cannot move an item
-between grids. Use pointer drag or **Move / resize item** for that.
-Escape stops keyboard editing without undoing those changes.
-During a pointer or touch interaction, Escape cancels the move or resize and restores the layout from before that interaction.
-Invalid, outside, or otherwise forbidden drops are cancelled in the same way.
-The **Move / resize item** action in the edit menu remains available for precise numeric input.
-
-<img
-  src={keyboardTileEditingImage}
-  alt="A focused board tile in keyboard editing mode"
-  style={{ maxWidth: "100%" }}
-/>
-
-#### Preview
-
-Layout Settings shows a lightweight structural preview for every layout, including saved spans, Containers, widget labels, and app icons.
-It uses a representative viewport width to project the saved geometry; it does not execute widget queries or represent every
-pixel of the screen range where the layout is active.
-
-Choose **Edit layout** to open the real board editor at that representative width on desktop. Save returns to Layout Settings. Cancel discards the local changes. On phones and tablets, the normal board editor continues to use the layout selected by the device width.
+Tiles use fixed `200 × 200` logical-pixel cells with a `24px` gap. Homarr scales the complete layout to the available
+width instead of changing each widget's proportions. **Reset from Base** regenerates a Mobile or custom layout from the
+current Base layout.
 
 ### Containers and rails
 
-Containers can hold apps, widgets, and nested Containers.
-The same Container model works on the main canvas, inside a fixed rail, or inside another Container.
-Move and resize Containers directly in edit mode; nested content stays within the Container's local bounds.
-Resize outlines follow the pointer continuously while a dashed preview marks the grid size that will be applied on release.
-Each responsive layout stores its own Container position and size.
+A **Container** groups apps, widgets, and nested Containers. It can have a label, collapse control, app-opening action,
+border color, and CSS classes.
 
-Each Container can configure:
+A **rail** reserves one to three columns at the left or right of a non-Mobile layout. Rails stay fixed while the page
+scrolls and store their contents separately for each layout.
 
-- Its label and whether that label is visible.
-- Whether users can collapse and expand it like an accordion.
-- Whether its menu shows **Open all in new tabs** for the app links it contains.
-- Its border color and custom CSS classes.
+## Edit a board
 
-Collapsing a Container reduces its full-width header to a half-row expansion bar and compacts the surrounding layout without losing its expanded size.
-Expanding it smoothly restores those bounds and moves following items out of the way without reloading the widgets inside it.
+Enter edit mode from the board header to add, move, resize, configure, or remove content. Save the board to persist the
+layout.
 
-### Background
+- Drag from an item's inactive content area; Containers use their grip.
+- Hold `Ctrl` on Windows/Linux or `Cmd` on macOS to select several items.
+- Use **Move / resize item** for another canvas, rail, Container, or exact coordinates.
+- Keyboard users can focus a tile, press Enter or Space, then move with arrow keys or resize with Shift + arrow keys.
+- Press Escape during a pointer or touch interaction to restore the item to its previous position.
 
-#### Background image URL
+The add-content menu can create an app, integration, widget, or Container without leaving the board.
 
-Homarr can display a background image behind apps and widgets.
-This URL can be used to define what image should be shown.
+## Board settings
 
-#### Background image attachment
+Board settings cover:
 
-This defines whether the background should move when the user scrolls.
+- **General:** page title, browser title, logo, and favicon.
+- **Layout:** responsive layouts, breakpoints, columns, and rails.
+- **Background:** image, attachment, size, and repeat behavior.
+- **Appearance:** colors, opacity, icon color, and item radius.
+- **Custom CSS:** styles applied only to the current board.
+- **Behaviour:** app status and widget context-menu behavior.
 
-#### Background image size
+See [Styling](/docs/advanced/styling) for board and global CSS.
 
-This defines whether the background should cover the entire page (and possibly be cropped) or never be cropped but may not cover the entire page.
+Outside edit mode, widgets may expose an advanced view and a context menu for status, refresh, quick options, settings,
+and actions. Available controls depend on the widget and the user's board and integration permissions.
 
-#### Background image repeat
+## Access control
 
-This defines whether the background should be repeated if it cannot cover the entire page.
-This option can be useful if you have patterns that can be repeated easily (e.g. patterns):
+Public boards are readable without signing in. Private boards require user, group, or global access.
 
-![](./img/background-repeat.png)
+| Board access | View | Edit content and settings | Access control, rename, delete |
+| ------------ | ---- | ------------------------- | ------------------------------ |
+| View         | Yes  | No                        | No                             |
+| Modify       | Yes  | Yes                       | No                             |
+| Full         | Yes  | Yes                       | Yes                            |
 
-### Appearance
+Inherited access comes from group permissions. Resource-specific access can be granted from the board's access-control
+section.
 
-#### Primary color
+Renaming a board changes its URL without a redirect. Deleting a board is permanent.
 
-Color that can be chosen freely to give accents to active elements.
+## Home boards
 
-#### Secondary color
+A **home board** opens at `/` and `/boards`. Desktop and mobile home boards are separate from the responsive layouts
+inside a board.
 
-Color that can be chosen freely to give accents.
+Defaults can be set for a user, group, or the whole server. User settings take priority, followed by matching groups,
+the `Everyone` group, and server defaults. Server-wide fallback boards must be public.
 
-#### Opacity
-
-Opacity of the colors.
-
-#### Icon color
-
-Change the color of your bookmark / app icons.
-
-<img src={iconColorImage} height={100} />
-
-#### Item radius
-
-Change the radius of your items and Containers.
-
-<img src={itemRadiusImage} height={100} />
-
-### Custom CSS
-
-This is the field where you can enter custom CSS.
-The styling will only be applied on the respective board page.
-
-When Homarr Assistant is enabled, users with modify permission can also ask it to edit the board's General, Background,
-Appearance, Custom CSS, and app-status settings. The assistant reads the current stylesheet first and presents an
-editable review form before requesting approval to save the change. It does not edit responsive layouts, access control,
-or Danger zone actions.
-
-[See this guide on how to work with custom CSS](/docs/advanced/styling/).
-
-### Behaviour
-
-#### Disable app status
-
-This will disable the status check for apps.
-
-#### Work directly from the board
-
-Widgets expose their routine controls without requiring edit mode:
-
-- Hold `Shift` while hovering a widget that supports advanced view to expand it in place while the other widgets
-  remain visible but dimmed. Release `Shift` to close it. Focus that widget and press `Shift` + `Enter` to keep the view
-  open until you close it. On touch devices, open it from the widget menu. Other widgets adapt in place instead.
-- When signed in, outside edit mode, and with **Enable right click on widgets** enabled, right-click a widget to inspect
-  its live query status, refresh its data, change quick options, open settings, or run supported actions. App tiles do
-  not use this widget menu, and available controls follow your board and integration permissions.
-
-The widget context menu follows the **Enable right click on widgets** preference in your user settings. On touch devices,
-use the widget menu where your browser exposes it.
-
-### Access control
-
-With the access control, you can permit a single user or a group to your board.
-The users and groups can have one of these three levels of access:
-
-| **Permission Level** | View board | Edit mode | Settings | Danger zone (eg. delete) |
-| -------------------- | ---------- | --------- | -------- | ------------------------ |
-| View board           | X          |           |          |                          |
-| Modify board         | X          | X         | X        |                          |
-| Full access          | X          | X         | X        | X                        |
-
-The permission level can only be changed after adding the user / group:
-
-![](./img/change-user-permission-level.png)
-
-If the board is private and the user is not added in any of the three tabs, they cannot access the board.
-They also do not see the board on the start page nor do they have access to any links for the board.
-
-Groups that have high permissions (e.g. administrator or all board permissions) will be shown as "inherited".
-They are permitted implicitly due to their permissions.
-
-After editing permissions, the save button below the table must be pressed.
-Otherwise, all changes will be discarded.
-
-### Danger zone
-
-#### Rename
-
-Renaming a board will break all existing links to it permanently with no redirect.
-
-#### Board visibility
-
-By default, boards will be private. This means only authenticated users that are authorized have access.
-Making a board public will expose it to everyone - including unauthenticated users.
-
-#### Delete
-
-This will permanently delete the board.
-This action is irreversible and cannot be undone.
-
-## Delete boards
-
-The deletion of boards is permanent and cannot be undone.
-There are two ways to delete a board:
-
-- Navigate to the settings of your board, open the "Danger zone" section and click on the "delete this board" button.
-- Navigate to the list of boards in the management pages, click the three dots and click on "delete permanently".
-
-Both actions will execute the same deletion process.
-
-## Duplicate boards
-
-:::note
-Duplicating a board will not copy the users and groups that have access to the board
-nor the integrations the user does not have access to.
-:::
-
-Duplicating a board will create a new board with the same settings, all responsive layouts, and independent positions as the original board.
-Duplicating a board that contains Custom Widgets also requires an administrator.
-You can duplicate a board by clicking on the three dots in the list of boards and selecting "Duplicate board".
-
-![](./img/duplicate-board-modal.png)
-
-## Setting boards as your home board
-
-The home board is the dashboard, that will be shown at the root path of Homarr or if no board name was passed in the URL.
-All the following paths will lead to the home board:
-
-- `my-homarr.com`
-- `my-homarr.com/boards`
-
-Your home board will have a special small badge at the top right in the list of boards:
-
-![](./img/home-board-flag.png)
-
-### For yourself
-
-To set the home board yourself, the easiest option is to set it directly in the list of boards:
-
-![](./img/set-as-home-board-menu.png)
-
-Alternatively, you can also define it via your user profile:
-
-1. Click on your user profile at the top right
-2. Click on `Your preferences`
-3. Change the home board in the `home board` dropdown and click on `Save`.
-
-### For other users
-
-1. Navigate to the users: `Management` > `Users` > `Manage`
-2. Click on the username of the user that you want to adjust
-3. Select the desired home board via the dropdown and click on `Save` \
-   ![](./img/set-home-board-other-user.png)
-
-### For user groups
-
-1. Navigate to the user groups: `Management` > `Users` > `Groups` > `Manage`
-2. Go to tab `Settings`
-3. Select the desired home board via the dropdown and click on `Save` \
-   ![](./img/set-home-board-user-group.png)
-
-### For whole server
-
-You can also set a global home board that will be used for all users that have not set a home board themselves.
-It will also be used for anonymous users.
-
-1. Navigate to the settings: `Management` > `Settings` > `Boards`
-2. Select the desired home board via the dropdown and click on `Save` \
-   ![](./img/set-home-board-global.png)
-
-:::note
-For the global home board you can only select boards that are public.
-:::
-
-### Mobile home board
-
-The mobile home board controls which board opens for devices that Homarr detects as mobile from the User-Agent header.
-This is separate from a board's **Mobile layout**, which controls the layout selected inside that board.
-You can set a mobile home board for yourself in your user preferences, for a user or group through management, or for the
-whole server with **Global mobile board** under `Management` > `Settings` > `Boards`.
-
-For signed-in users, Homarr checks the user's mobile home board, then the user's desktop home board, then the mobile and
-desktop defaults for the lowest-position matching group, followed by the mobile and desktop defaults for the `Everyone`
-group, and finally the server-wide mobile and desktop defaults. Anonymous visitors use the server-wide mobile default and
-then the server-wide desktop default. Server-wide fallback boards must be public. See the
-[global board defaults](/docs/management/settings#boards) for the complete precedence and the required public-board rule.
+See [Users and groups](../users) and [Server settings](../settings#boards).

apps/docs/docs/management/certificates/index.mdx

@@ -15,6 +15,8 @@ Below you can see a screenshot of the certificates page.
 The items show the subject, filename and when it expires.
 The color of the icon indicates how long it is valid.
 
+![The Trusted certificates management page](../img/certificates.png)
+
 ![](./img/screenshot.png)
 
 | Color     | Meaning                     |
@@ -30,15 +32,12 @@ Navigate to `Management` > `Tools` > `Certificates`.
 
 ## Add a certificate
 
-To add a certificate click on the "Add certificate" button.
+To add a certificate click on the "Add certificate" button. The upload form expands directly on the certificates page.
 
 ![](./img/add-button.png)
 
-Then select the certificate file you want to add.
-
-![](./img/add-modal.png)
-
-And click the "Add" button.
+Then select the certificate file you want to add and click the "Add" button. You can cancel to collapse the form without
+leaving the page.
 
 ## Delete a certificate
 
@@ -46,7 +45,7 @@ To delete a certificate you can click on the trash icon in the certificate card.
 
 ![](./img/card.png)
 
-Then confirm the deletion.
+The first click arms the action and the second click confirms the deletion in place; no confirmation dialog is opened.
 
 ## Managing it through file system
 

apps/docs/docs/management/custom-widgets/agent-authoring.mdx

@@ -1,169 +1,45 @@
-# Use agents and skills.sh
+# Connect an agent
 
-An external agent creates one widget at a time with the Homarr MCP server. The agent harness manages the list for multiple widgets.
+An MCP-connected agent can validate, preview, test, and save Custom Widgets. The API key owner must be a Homarr
+administrator.
 
-Homarr does not create widget packs or drafts for multiple widgets.
-
-The MCP API key must belong to a Homarr administrator. Non-administrator keys do not list Custom Widget tools, prompts,
-or resources. The same administrator requirement applies to the matching HTTP authoring endpoints.
-
-<a className="button button--primary" href="https://www.skills.sh/homarr-labs/homarr/homarr-custom-widget">
-  View the Custom Widget Skill on skills.sh
-</a>
-
-Install the Agent Skill from the verified Homarr repository:
+Install the official skill:
 
 ```sh
 npx skills add https://github.com/homarr-labs/homarr --skill homarr-custom-widget
 ```
 
-The portable skill gives concise authoring guidance. For connected agents, Homarr returns the complete `SKILL.md` and
-all bundled skill references once in one lazy tool response. The Homarr MCP prompt then gives the agent a
-retrieval workflow: read the live schema and fetch only the component documentation needed for the widget.
+The skill routes the agent to the release-matched schema, runtime, security, examples, and component metadata. It keeps
+those references separate so the agent loads only what the current widget needs.
 
-The workbench's **Copy AI prompt** action is separate. It creates a self-contained prompt below 12,000 characters for an ordinary ChatGPT or Claude conversation. It includes the lean contract, bindings, recommended components, and two polished examples. It never tells an offline model to call MCP tools.
-
-The source is in [`.agents/skills/homarr-custom-widget`](https://github.com/homarr-labs/homarr/tree/HEAD/.agents/skills/homarr-custom-widget). `HEAD` follows the repository default branch, so the link is not tied to an unreleased feature branch. Homarr does not provide a ZIP archive.
-
-After publication, run the installation command once. This action registers installation activity.
-
-Then, verify the skills.sh page. Request official maker attribution for `homarr-labs` from skills.sh.
-
-Repository code cannot give this attribution.
-
-## Get MCP resources
+## MCP resources
 
 - Prompt: `homarr-custom-widget-author`
-- Resources: `homarr://custom-widgets/schema`, `components`, `components/{name}`, `examples/{name}`, and `skill`
-- HTTP: `GET /api/custom-widgets/authoring-prompt`, `schema`, `components`, and `skill`
+- Skill: `homarr://custom-widgets/skill`
+- References: `homarr://custom-widgets/references/{schema|runtime|security}`
+- Schema: `homarr://custom-widgets/schema`
+- Components: `homarr://custom-widgets/components` and `components/{name}`
+- Examples: `homarr://custom-widgets/examples/{name}`
 
-The authoring-prompt tool description contains one sentence. The prompt contains the workflow instructions and resource links.
+Equivalent HTTP resources are available under `/api/custom-widgets/` for authenticated administrators.
 
-`GET /api/custom-widgets/skill` and `customWidget_getSkill` return a self-contained structured skill payload:
+## Authoring lifecycle
 
-```ts
-{
-  name: "homarr-custom-widget";
-  version: string;
-  skillMd: string; // Complete SKILL.md
-  references: Record<string, string>;
-  skillsShUrl: string;
-  sourceUrl: string;
-  installCommand: string;
-}
-```
+1. Load the skill and only the references needed for the design.
+2. Read the external API documentation and build the definition.
+3. Validate the JSX, then create a preview from the complete definition.
+4. Run every returned query and simulate every relevant action against the current preview revision.
+5. Inspect the preview and redacted journal. Revise the existing preview for JSX-only changes.
+6. Save from the final tested preview.
+7. Configure deployment-specific source URLs and credentials, then preview the saved definition again.
 
-The `homarr://custom-widgets/skill` MCP resource returns the same `SKILL.md` and references once as bundled Markdown.
+Use `templateLines` for multiline JSX tool input. A preview must have current evidence for every query and action before
+it can be saved. Simulation counts as action evidence without performing the mutation.
 
-The component catalog is a compact index of names, categories, safety levels, shared prop names, policies, and example
-IDs. Per-component results contain only component-specific props and a reference to shared prop documentation. Use
-`customWidget_getSharedProps` once with only the shared prop names needed across the selected components. This avoids
-repeating hundreds of global props in every tool result. The catalog is deliberately not embedded in the skill or
-clipboard prompt; the skill response still contains the complete authoring, schema, runtime, and security references.
+If the agent does not have a source URL or credential, it can request a short-lived Homarr configuration URL. An
+authenticated administrator completes it in Homarr; the agent receives the status, never the plaintext credential.
 
-These interfaces do not return an archive URL or archive hash.
+Agents can also search, inspect, install, and configure existing Workshop widgets instead of regenerating them.
 
-## Create a Custom Widget with MCP
-
-1. Load `customWidget_getSkill`, then get the prompt and live schema.
-2. Call `customWidget_getComponentCatalog`, followed by `customWidget_getComponent` for only the relevant installed
-   components and `customWidget_getExample` when one catalog example matches the interaction pattern. Fetch at most
-   eight component documents before the first validation (or four after a complete example already matches). If shared
-   props are needed, collect their catalog names and call `customWidget_getSharedProps` once for that set.
-3. Read the external API documentation.
-4. Build one definition, using `templateLines` for multiline JSX tool input.
-5. Validate the definition without saving it and repair every reported issue.
-6. Create a preview session.
-7. Run `customWidget_previewQuery` for every query returned by the preview and inspect its actual status and data shape. Assistant conversations retain a bounded response preview so large APIs cannot exhaust the model context. Use
-   `{}` for load queries; manual queries require exactly the returned primitive `parameterNames`.
-8. Test relevant actions in simulation mode.
-9. Open the returned preview path with browser tools.
-10. Inspect the redacted journal and revise the local candidate until validation, data, and rendering all work. Keep the
-    exact tested preview candidate locally. Any definition, template, or source change requires a new validation and preview;
-    earlier query evidence belongs to the previous preview revision.
-11. Create the widget from that final tested preview with `customWidget_createFromPreview`. The preview session already carries
-    the source URLs and encrypted credentials supplied during preview; the create call accepts only its session ID plus an
-    optional target board and persists that tested preview.
-12. Open its returned management path, and use a structured question when the user must choose whether to place it on a board.
-13. Otherwise, ask the user to configure the saved definition with the ten-minute Homarr source-setup URL.
-14. Create a final preview with the saved definition ID so Homarr loads its stored credentials, then test it again.
-15. Update the saved definition if the final verification finds a problem. `customWidget_update` also accepts
-    `templateLines` for multiline JSX without resetting omitted options.
-16. Repeat the procedure for the next widget.
-
-Successful validation returns a compact summary instead of echoing the full widget and template. Preview creation
-returns its session, links, and query checklist without repeating the submitted definition. Keep the candidate locally
-and reuse it for the next lifecycle step.
-
-Each source-configuration URL applies to one definition or preview and one source. It is short-lived, single-use, and
-can only be opened and completed by an authenticated Homarr administrator. The administrator confirms the server URL,
-network scope, and required credential fields directly in Homarr. The agent receives only request status and never
-receives plaintext credentials. Preview-scoped values expire with that preview; definition-scoped values persist.
-
-Agents can install existing widgets without regenerating them:
-
-1. Search with `customWidget_workshopSearch`.
-2. Inspect and validate a result with `customWidget_workshopGet`.
-3. Install it with `customWidget_workshopInstall`.
-4. Configure deployment-specific URLs and supplied credentials with `customWidget_sourceConfigure`.
-5. If the agent does not have those values, call `customWidget_configurationRequestUser` and wait for completion.
-6. Test the installed definition, then use `board_addItem` with kind `customApi` and the returned definition ID.
-
-Homarr encrypts the plaintext immediately. Homarr does not return the plaintext.
-
-## Evaluate the copied prompt
-
-Homarr maintainers can run the same self-contained prompt that the workbench copies through the live generation-quality suite:
-
-```sh
-OPENROUTER_API_KEY=... pnpm --filter @homarr/custom-widgets test:ai
-```
-
-The manifest suite covers nine complex and public-API prompts. Its deterministic fixture-backed cases include a fake
-homelab health API, CoinMarketCap's keyless public API, Bored, Agify, and a multi-request Pokédex. Before the configured
-model judges a result, the candidate must pass Homarr's real clipboard parser, canonical schema, and deterministic
-checks for documented endpoints, authentication, request triggers, query bindings, response fields, and essential
-runtime components.
-
-To exercise the real Homarr Assistant lifecycle instead of accepting a returned JSON block, run:
-
-```sh
-OPENROUTER_API_KEY=... pnpm --filter @homarr/custom-widgets test:assistant-ai
-```
-
-The same suites can target the Homarr provider with a Workshop PocketBase token instead of an OpenRouter key:
-
-```sh
-AI_PROVIDER_BASE_URL=https://homarr.dev/api/ai/v1 \
-AI_PROVIDER_API_KEY=<workshop-token> \
-AI_PROVIDER_MODEL=homarr/model \
-pnpm --filter @homarr/custom-widgets test:assistant-ai
-```
-
-`AI_PROVIDER_JUDGE_MODEL` can select a separate judge when the configured endpoint offers one. The Homarr provider
-offers exactly one model, so generation and review both use `homarr/model`.
-
-The assistant test exposes the same lazy skill, live schema, component catalog, targeted component references,
-validation, preview-query, and create-from-preview tools as the product. It refuses to save a definition that was not
-validated exactly or whose preview queries were not all tested. Multi-request fixtures return a different payload for
-each documented path and require manual-query parameters. Use `--case=pokedex`, `--case=coinmarketcap-keyless`,
-`--case=bored-activity`, or `--case=agify-name` for a focused run.
-
-Both suites use the configured provider models for generation and harsh review. They save tool traces, validated
-manifests, raw reviews, and detailed category scores under
-`packages/custom-widgets/.ai-evaluations/`. These live tests are maintainer-invoked rather than CI-required because
-they consume a configured provider account and exercise a nondeterministic model. The repository's ordinary tests
-cover the lifecycle enforcement, fixture routing, score calculation, and failure behavior without network access.
-
-Each scenario stops as soon as it passes and has a hard limit of ten generation attempts. Override the endpoint,
-models, or per-scenario limit with `AI_PROVIDER_BASE_URL`, `AI_PROVIDER_API_KEY`, `AI_PROVIDER_MODEL`,
-`AI_PROVIDER_JUDGE_MODEL`, and
-`CUSTOM_WIDGET_AI_MAX_LOOPS`. Generated artifacts are local and ignored by Git; promote a reviewed, validated result
-into the bundled-widget source deliberately.
-
-The reference API check uses a real PokeAPI list/detail request and a read-only Portainer container query when `PORTAINER_BASE_URL` and `PORTAINER_API_KEY` are set. Use `pnpm --filter @homarr/custom-widgets test:reference-apis -- --pokeapi-only` for the public PokeAPI check alone. To exercise start, restart, and stop against a disposable container, also set `PORTAINER_TEST_CONTAINER_ID` and the explicit safeguard `PORTAINER_ALLOW_MUTATIONS=1`; the script restores the container's original running state.
-
-Use `pnpm --filter @homarr/custom-widgets test:reference-apis -- --public-ai-apis-only` to verify the live Bored and
-CoinMarketCap response shapes used by the assistant fixtures. The same command also verifies Agify when
-`AGIFY_API_KEY` is configured; otherwise it reports the authenticated check as skipped without weakening the
-deterministic Agify fixture tests.
+See [MCP](/docs/management/mcp) for client configuration and [requests and security](./requests-and-security) for the
+runtime limits.

apps/docs/docs/management/custom-widgets/authoring.mdx

@@ -1,70 +1,29 @@
 # Create a Custom Widget
 
-import { CanonicalCustomWidgetExample } from "@site/src/components/custom-widget-code";
-import workbenchImage from "./img/workbench.png";
-import workbenchMobileImage from "./img/workbench-mobile.png";
-import workbenchValidationImage from "./img/workbench-validation.png";
+The workbench provides editors for general metadata, API sources, requests, widget options, JSX, and preview data. Raw
+JSON is available when direct editing is faster.
 
-The workbench exposes **General**, **API sources**, **Requests**, **Options**, **JSX**, and **Preview** sections. Advanced JSON is
-available in the manifest and request/option editors. Code and preview sit side by side on desktop; on smaller screens the
-**Configure**/**Preview** switch shows one pane at a time and the section navigation scrolls horizontally. Preview sizes display
-as **S/M/L** (Compact/Standard/Wide), and fixtures are **Live**, **Loading**, **Empty**, or **Error**.
-For multiline JSX, prefer `templateLines` in agent or MCP input and keep the final tested preview as the source of truth before saving.
+## Workflow
 
-<img
-  src={workbenchImage}
-  alt="Custom Widget workbench with configuration sections and a live preview"
-  style={{ maxWidth: "100%" }}
-/>
+1. Configure each API source, network scope, authentication method, and credential.
+2. Add named queries and actions. Values can reference widget options or invocation parameters.
+3. Define widget options and their defaults.
+4. Write JSX using `data`, `status`, `options`, and temporary `inputs`.
+5. Run **Test and preview**, inspect the response data and redacted request journal, then save.
 
-<img
-  src={workbenchMobileImage}
-  alt="Mobile Custom Widget workbench with Configure and Preview switch and horizontally scrollable section navigation"
-  style={{ maxWidth: "100%" }}
-/>
+Changing the definition, options, or credentials invalidates the previous preview. Preview actions are simulated unless
+**Run actions against the configured API** is enabled for that preview session.
 
-The workbench keeps the configuration and preview together so you can inspect validation diagnostics, the redacted request
-journal, fixture data, and preview size before saving. Invalid fields stay marked in the form while the preview explains why it
-needs attention.
+Widget options support text, textarea, number, switch, select, multi-select, slider, date, time, color, icon, URL,
+duration, time zone, and JSON controls. Dynamic choices can come from a load query.
 
-<img
-  src={workbenchValidationImage}
-  alt="Custom Widget workbench showing a Base URL validation error with Test, preview, and Create actions disabled"
-  style={{ maxWidth: "100%" }}
-/>
+See the [safe JSX runtime](./custom-jsx), [component reference](./component-reference), and
+[request reference](./requests-and-security) for the authoring contract.
 
-## Manual workflow
+## Create with another AI service
 
-1. Configure the default API source, network scope, authentication, and credential.
-2. Add query/action cards. Values can be literals, widget options, or invocation parameters.
-3. Add widget options with their control and default value.
-4. Write responsive JSX using `data`, `status`, `options`, and temporary `inputs`.
-5. Test and preview, inspect Data and the redacted request journal, then save.
+**Create or fix with any AI** copies a self-contained prompt for an ordinary ChatGPT or Claude conversation. The model
+must return one fenced `json` block containing the complete definition. Paste that block into the workbench, add
+credentials separately, and validate it against a real preview.
 
-<CanonicalCustomWidgetExample
-  id="named-widget-requests"
-  label="Named queries and actions"
-  example="requests"
-  height="420px"
-/>
-
-<CanonicalCustomWidgetExample id="widget-options" label="Widget options" example="options" height="360px" />
-
-Every option has a default. Supported controls include text, textarea, number, switch, select, multi-select, slider, date, time, color, icon, URL, duration, time zone, and JSON. Dynamic choices use `choicesFrom: { request, itemsPath?, valuePath, labelPath }`; the request must be a load query without invocation parameters, and you cannot provide both static `choices` and `choicesFrom`.
-
-Preview actions are simulated by default and recorded in the journal without contacting the service. Enable **Run actions against the configured API** only when you intend a real mutation; live actions still require configured confirmation.
-
-## ChatGPT or Claude
-
-Open **Create or fix with any AI**, enter the desired widget and optional API documentation URL, then select the copy action beside the accordion title. The single self-contained prompt is below 12,000 characters, starts with your request, includes the lean contract and two polished examples, and never claims that an offline chat has MCP tools.
-
-The model must return one fenced `json` block containing the complete widget, including the JSX in its `template`
-field. Copy that single block and select **Paste**. Homarr fills the visual builders and the JSX editor
-without any placeholder replacement or second paste.
-
-Homarr shows all actionable schema or JSX errors inline. Enter credentials separately. The copied prompt does not include the
-latest preview response; use **Preview** > **Data** to inspect it and mention important response fields in your request. The prompt deliberately
-recommends a focused Mantine component set, visual hierarchy, responsive layout, theme compatibility, and loading,
-empty, failure, and success states.
-
-Connected agents should use the skills.sh skill and retrieve the live schema and individual component metadata only as needed.
+For an MCP-connected agent, use the [Homarr Custom Widget skill](./agent-authoring) instead.