fix(docker): normalize container CPU usage

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

@@ -0,0 +1,43 @@
+---
+name: homarr-custom-widget
+description: Author, validate, preview, test, install, or configure API-backed Homarr Custom JSX v2 widgets.
+---
+
+# Homarr Custom Widget
+
+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.
+
+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.
+
+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.
+
+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`.
+
+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)`; 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.
+
+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.
+
+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.
+
+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.
+
+For a community widget, use `customWidget_workshopSearch`, `customWidget_workshopGet`, then `customWidget_workshopInstall`; configure its source securely. Preview configuration expires, so create before persisting configuration.
+
+Reference routing:
+
+- 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

@@ -0,0 +1,37 @@
+# Runtime
+
+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" />
+<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>
+```
+
+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.
+
+`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

@@ -0,0 +1,49 @@
+# Schema
+
+```ts
+interface HomarrCustomWidgetV2 {
+  $schema: "homarr-custom-widget-v2";
+  name: string;
+  description?: string;
+  iconUrl?: string;
+  sources: Record<string, CustomWidgetSource>;
+  requests: Record<string, CustomWidgetRequest>;
+  options?: Record<string, CustomWidgetOption>;
+  template: string;
+}
+```
+
+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 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/homarr-custom-widget/references/security.md

@@ -0,0 +1,7 @@
+# Security
+
+All requests use Homarr's protected server executor. Source origin, network scope, DNS, redirects, SSRF, rate limits, permissions, size limits, timeouts, and encrypted credential injection remain enforced.
+
+The JSX interpreter blocks imports, hooks, refs, raw event callbacks, browser requests, eval, arbitrary functions, prototype access, unsafe URLs, global CSS escape, arbitrary portals, bigint, statement blocks, IIFEs, and recursion. Regex literals must be bounded and reject backreferences, lookbehind, nested quantifiers, excessive length, and unsupported flags.
+
+Credentials are stored separately and never exported or returned to an agent. A published self-hosted source URL is only a suggestion: installers must confirm or replace private and loopback URLs for their own Homarr deployment. Source origins cannot be controlled through widget options.

.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,206 +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
-│   ├── old-import/      # Legacy Homarr import
-│   ├── old-schema/      # Legacy Homarr zod schemas
-│   └── 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/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`

.deepsource.toml

@@ -1,8 +0,0 @@
-version = 1
-
-[[analyzers]]
-name = "javascript"
-
-[analyzers.meta]
-plugins = ["react"]
-environment = ["nodejs"]

.dockerignore

@@ -17,7 +17,8 @@ coverage
 dev
 .build
 e2e
-apps/docs
+apps/docs/*
+!apps/docs/package.json
 apps/nextjs/.next
 .env
 .env.*

.env.example

@@ -61,9 +61,31 @@ TURBO_TELEMETRY_DISABLED=1
 # Enable mock integration
 UNSAFE_ENABLE_MOCK_INTEGRATION=true
 
+# Public URL contract. Values must be absolute HTTP(S) URLs without credentials,
+# query strings, or fragments. Trailing slashes are normalized at startup.
+HOMARR_WEBSITE_URL=https://homarr.dev
+# PocketBase API used by Homarr and by the standalone documentation site.
+# Defaults to HOMARR_WEBSITE_URL.
+# WORKSHOP_API_URL=https://homarr.dev
+# Public Workshop website used by links in Homarr, Custom Widgets, onboarding,
+# and assistant context. Defaults to HOMARR_WEBSITE_URL/workshop.
+# WORKSHOP_WEB_URL=https://homarr.dev/workshop
+
+# Documentation and PocketBase deployment settings.
+# WORKSHOP_PUBLIC_ORIGIN=https://homarr.dev
+# PB_ALLOWED_ORIGINS=*
+
+# Local Workshop stack:
+# 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
+# WORKSHOP_PUBLIC_ORIGIN=http://127.0.0.1:3003
+# Optional: GITHUB_CLIENT_ID=
+# Optional: GITHUB_CLIENT_SECRET=
+
 # Enable demo mode (seeds a demo user "demo"/"demo", a sample board and a mock integration)
 # DEMO_MODE=true
 
 # Whether demo mode is read-only. Defaults to true (the public demo blocks all mutations).
 # Set to false for writable preview deployments so the demo user can modify the dashboard.
-# DEMO_READ_ONLY=false
+# DEMO_READ_ONLY=false

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -33,6 +33,14 @@ 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
+        - 1.71.0
         - 1.70.0
         - 1.69.2
         - 1.69.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/pull_request_template.md

@@ -16,6 +16,6 @@
 **When contributing a new integration or widget:**
 
 - [ ] I confirmed manually that the integration or widget is working with a real system and performed basic smoke
-  tests (e.g. what happens if it is offline)
+      tests (e.g. what happens if it is offline)
 - [ ] Optional but recommended: I confirm that I am willing to be added to the `CODEOWNERS` of this feature and will
-  provide support and maintain the integration (e.g. in case of breaking or failure)
+      provide support and maintain the integration (e.g. in case of breaking or failure)

.github/renovate.json5

@@ -1,6 +1,6 @@
 {
   $schema: "https://docs.renovatebot.com/renovate-schema.json",
-  extends: ["config:recommended"],
+  extends: ["config:recommended", ":dependencyDashboardApproval"],
   packageRules: [
     {
       matchPackageNames: ["^@homarr/"],
@@ -47,7 +47,7 @@
   rangeStrategy: "bump",
   automerge: false,
   baseBranchPatterns: ["dev"],
-  dependencyDashboard: false,
+  dependencyDashboard: true,
   // prevent special characters in branch names (otherwise git errors occur on windows)
   branchNameStrict: true,
 }

.github/workflows/autofix.yml

@@ -3,7 +3,7 @@ name: Formatting
 on:
   pull_request:
     types: [opened, synchronize, reopened]
-    branches: ["*"]
+    branches: ["**"]
 
 permissions:
   contents: read
@@ -32,4 +32,4 @@ jobs:
         run: |
           git diff --name-only --diff-filter=ACMR -z "origin/${BASE_REF}...HEAD" -- \
             '*.css' '*.js' '*.json' '*.jsonc' '*.jsx' '*.md' '*.mdx' '*.scss' '*.ts' '*.tsx' '*.yaml' '*.yml' \
-            | xargs -0 -r pnpm exec oxfmt --check
+            | xargs -0 -r pnpm exec oxfmt --check --

.github/workflows/automatic-approval.yml

@@ -1,35 +0,0 @@
-name: "[Dependency Updates] Auto Approve"
-on:
-  pull_request:
-    types: [opened, synchronize]
-
-permissions: {}
-
-jobs:
-  approve-automatic-prs:
-    runs-on: ubuntu-latest
-    timeout-minutes: 2
-    # 158783068: homarr-renovate[bot]
-    # 190541745: homarr-crowdin[bot]
-    # 210161987: homarr-update-contributors[bot]
-    # 175486441: homarr-releases[bot]
-    # Extracted from https://api.github.com/users/<username>
-    if: github.actor_id == 158783068 || github.actor_id == 190541745 || github.actor_id == 210161987 || github.actor_id == 175486441
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v7
-      - name: Obtain token
-        id: obtainToken
-        uses: actions/create-github-app-token@v3
-        with:
-          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
-          permission-pull-requests: write # required to approve pull request
-
-      - name: Install GitHub CLI
-        run: sudo apt-get install -y gh
-      - name: Approve automatic PRs
-        env:
-          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
-        run: |
-          gh pr review ${{github.event.pull_request.number}} --approve --body "Automatically approved by GitHub Action"

.github/workflows/bot-auto-merge-reconcile.yml

@@ -0,0 +1,43 @@
+name: "[Bots] Reconcile Auto-merge"
+
+on:
+  schedule:
+    - cron: "*/30 * * * *"
+  workflow_dispatch:
+
+permissions: {}
+
+jobs:
+  reconcile:
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v7
+
+      - name: Obtain token
+        id: obtainToken
+        uses: actions/create-github-app-token@v3
+        with:
+          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
+          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
+          permission-pull-requests: write # required to enable auto-merge
+
+      - name: Install GitHub CLI
+        run: sudo apt-get install -y gh
+
+      - name: Re-enable auto-merge for prepared bot PRs
+        env:
+          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
+        run: |
+          # 158783068: homarr-renovate[bot]
+          # 190541745: homarr-crowdin[bot]
+          # 210161987: homarr-update-contributors[bot]
+          # 175441: homarr-releases[bot]
+          gh pr list --repo "${{ github.repository }}" --base dev --state open --limit 100 \
+            --json number,author,reviewDecision,mergeStateStatus,autoMergeRequest \
+            --jq '.[] | select(.author.login as $login | ["app/homarr-renovate", "app/homarr-crowdin", "app/homarr-update-contributors", "app/homarr-releases"] | index($login)) | select(.reviewDecision == "APPROVED") | select(.mergeStateStatus == "CLEAN") | select(.autoMergeRequest == null) | .number' \
+          | while read -r pr; do
+              echo "Re-enabling auto-merge on PR #$pr"
+              gh pr merge "$pr" --auto --squash
+            done

.github/workflows/bot-pr-automerge.yml

@@ -0,0 +1,47 @@
+name: "[Bots] Approve and Auto-merge"
+
+on:
+  pull_request:
+    types: [opened, synchronize, reopened, ready_for_review]
+
+permissions: {}
+
+jobs:
+  approve-and-automerge:
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    # 158783068: homarr-renovate[bot]
+    # 190541745: homarr-crowdin[bot]
+    # 210161987: homarr-update-contributors[bot]
+    # 175441: homarr-releases[bot]
+    # Extracted from https://api.github.com/users/<username>
+    if: |
+      (github.actor_id == 158783068 || github.actor_id == 190541745 || github.actor_id == 210161987 || github.actor_id == 175441) &&
+      github.event.pull_request.head.repo.full_name == github.repository &&
+      github.event.pull_request.base.ref == 'dev'
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v7
+
+      - name: Obtain token
+        id: obtainToken
+        uses: actions/create-github-app-token@v3
+        with:
+          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
+          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
+          permission-pull-requests: write # required to approve a pull request and enable auto-merge
+
+      - name: Install GitHub CLI
+        run: sudo apt-get install -y gh
+
+      - name: Approve and enable auto-merge
+        env:
+          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
+        run: |
+          PR_NUMBER="${{ github.event.pull_request.number }}"
+          if [ "$(gh pr view "$PR_NUMBER" --json reviewDecision --jq .reviewDecision)" != "APPROVED" ]; then
+            gh pr review "$PR_NUMBER" --approve --body "Automatically approved by Homarr bot policy"
+          fi
+          if [ "$(gh pr view "$PR_NUMBER" --json autoMergeRequest --jq '.autoMergeRequest != null')" != "true" ]; then
+            gh pr merge "$PR_NUMBER" --auto --squash
+          fi

.github/workflows/ci.yml

@@ -3,12 +3,12 @@ name: CI
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]
-    branches: ["*"]
+    branches: ["**"]
   pull_request_target:
     types: [closed]
-    branches: ["*"]
+    branches: ["**"]
   push:
-    branches: [main, dev, beta, next]
+    branches: [main, dev, beta, next, v2, release/v2]
   merge_group:
   workflow_dispatch:
     inputs:
@@ -34,8 +34,10 @@ permissions:
   contents: read
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.event.pull_request.number || inputs.pr_number || github.ref }}
-  cancel-in-progress: false
+  # Every event for a PR shares one group so a close event cancels stale image
+  # publication and a newer synchronize run cannot be overwritten by an older run.
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || inputs.pr_number || github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' || github.event_name == 'pull_request_target' || github.event_name == 'workflow_dispatch' || github.ref != 'refs/heads/main' }}
 
 env:
   FORCE_COLOR: 3
@@ -49,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 }}
@@ -82,28 +84,41 @@ jobs:
         run: cp .env.example .env
 
       - name: Lint, typecheck, and build affected workspaces
-        run: pnpm turbo run lint typecheck build --affected --continue=dependencies-successful --concurrency=4 --log-order=stream
+        run: pnpm turbo run lint typecheck build --affected --continue=dependencies-successful --concurrency=2
 
       - name: Validate workspace configuration
         run: pnpm lint:ws
 
+      - name: Validate Custom Widget architecture
+        run: pnpm check:custom-widgets
+
+      - name: Validate checked-in OpenAPI schema
+        run: pnpm check:openapi
+
+      - name: Validate Custom Widget bundle budget
+        run: |
+          pnpm --filter nextjs build
+          pnpm check:custom-widget-bundle
+
       - name: Run unit tests
         run: pnpm test
 
   container:
     name: Container and E2E
-    needs: fast-gate
+    needs: [fast-gate, preview-amd64]
     if: |
-      github.event_name == 'merge_group' ||
-      (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
-      (github.event_name == 'workflow_dispatch' && (inputs.operation == 'validate' || inputs.operation == 'publish'))
+      !cancelled() && needs.fast-gate.result == 'success' &&
+      (
+        github.event_name == 'merge_group' ||
+        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
+        (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
+        (github.event_name == 'workflow_dispatch' && (inputs.operation == 'validate' || inputs.operation == 'publish'))
+      )
     runs-on: ubuntu-latest
     timeout-minutes: 30
     permissions:
       contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.preview-build.outputs.digest }}
+      packages: read
     steps:
       - uses: actions/checkout@v7
         if: "!env.ACT"
@@ -118,8 +133,18 @@ jobs:
         if: "!env.ACT"
         uses: docker/setup-buildx-action@v4
 
+      - name: Reuse amd64 preview image
+        if: needs.preview-amd64.outputs.digest != '' && !env.ACT
+        env:
+          DIGEST: ${{ needs.preview-amd64.outputs.digest }}
+        run: |
+          echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u "${{ github.actor }}" --password-stdin
+          docker pull "${PREVIEW_IMAGE}@${DIGEST}"
+          docker tag "${PREVIEW_IMAGE}@${DIGEST}" homarr-ci
+          docker tag "${PREVIEW_IMAGE}@${DIGEST}" homarr-e2e
+
       - name: Build container once
-        if: "!env.ACT"
+        if: needs.preview-amd64.outputs.digest == '' && !env.ACT
         uses: docker/build-push-action@v7
         with:
           context: .
@@ -134,8 +159,8 @@ jobs:
             org.opencontainers.image.source=${{ github.server_url }}/${{ github.repository }}
             org.opencontainers.image.revision=${{ github.sha }}
             org.opencontainers.image.ref.name=pr-${{ github.event.pull_request.number || inputs.pr_number || 'none' }}
-          cache-from: type=gha,scope=homarr-linux-amd64
-          cache-to: type=gha,scope=homarr-linux-amd64,mode=max
+          cache-from: type=gha,scope=homarr-e2e
+          cache-to: type=gha,scope=homarr-e2e,mode=max
           secrets: |
             TURBO_API=${{ secrets.TURBO_API }}
             TURBO_TEAM=${{ secrets.TURBO_TEAM }}
@@ -176,7 +201,10 @@ jobs:
         run: pnpm exec playwright install-deps chromium
 
       - name: Run E2E tests
-        run: pnpm test:e2e
+        env:
+          NODE_ENV: development
+          CI: "true"
+        run: pnpm exec vitest e2e --retry 1 --maxWorkers 4
 
       - name: Upload E2E artifacts
         if: failure() && !env.ACT
@@ -186,27 +214,44 @@ jobs:
           path: e2e/test-results/
           retention-days: 7
 
-      - name: Log in to GHCR for preview publication
-        if: |
-          !env.ACT &&
-          (
-            (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
-            (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-          )
+  preview-amd64:
+    name: Build amd64 preview image
+    needs: fast-gate
+    if: |
+      (
+        (github.event_name == 'pull_request' && github.event.pull_request.draft == false && github.event.pull_request.head.repo.full_name == github.repository) ||
+        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
+        (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
+      )
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    permissions:
+      contents: read
+      packages: write
+    outputs:
+      digest: ${{ steps.preview-build.outputs.digest }}
+    steps:
+      - uses: actions/checkout@v7
+        if: "!env.ACT"
+        with:
+          persist-credentials: false
+          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
+
+      - name: Log in to GHCR
+        if: "!env.ACT"
         uses: docker/login-action@v4
         with:
           registry: ${{ env.REGISTRY }}
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Push amd64 preview image by digest
+      - name: Set up Docker Buildx
+        if: "!env.ACT"
+        uses: docker/setup-buildx-action@v4
+
+      - name: Build and push amd64 preview image by digest
         id: preview-build
-        if: |
-          !env.ACT &&
-          (
-            (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
-            (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-          )
+        if: "!env.ACT"
         uses: docker/build-push-action@v7
         with:
           context: .
@@ -214,22 +259,20 @@ jobs:
           platforms: linux/amd64
           outputs: type=image,"name=${{ env.PREVIEW_IMAGE }}",push-by-digest=true,name-canonical=true,push=true
           cache-from: type=gha,scope=homarr-linux-amd64
+          cache-to: type=gha,scope=homarr-linux-amd64,mode=max
           secrets: |
             TURBO_API=${{ secrets.TURBO_API }}
             TURBO_TEAM=${{ secrets.TURBO_TEAM }}
             TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
             TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
 
-      - name: Show Act publication result
-        if: env.ACT
-        run: echo "Act validated the publication path; external GHCR writes are disabled locally."
-
   preview-arm64:
     name: Build arm64 preview image
     needs: fast-gate
     if: |
       (
-        (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
+        (github.event_name == 'pull_request' && github.event.pull_request.draft == false && github.event.pull_request.head.repo.full_name == github.repository) ||
+        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
         (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
       )
     runs-on: ubuntu-24.04-arm
@@ -277,18 +320,25 @@ jobs:
 
   publish-preview:
     name: Publish multi-platform preview image
-    needs: [container, 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') ||
         (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
       )
     runs-on: ubuntu-latest
     timeout-minutes: 5
     permissions:
+      contents: read
       packages: write
+      pull-requests: read
     env:
-      PREVIEW_TAG: pr-${{ github.event.pull_request.number || inputs.pr_number }}
+      PREVIEW_TAG: ${{ github.event_name == 'push' && 'v2' || format('pr-{0}', github.event.pull_request.number || inputs.pr_number) }}
     steps:
       - name: Log in to GHCR
         if: "!env.ACT"
@@ -302,16 +352,52 @@ jobs:
         if: "!env.ACT"
         uses: docker/setup-buildx-action@v4
 
+      - name: Verify PR head before publication
+        if: github.event_name == 'pull_request'
+        uses: actions/github-script@v8
+        env:
+          EXPECTED_HEAD_SHA: ${{ github.event.pull_request.head.sha }}
+        with:
+          script: |
+            const { data: pull } = await github.rest.pulls.get({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              pull_number: context.payload.pull_request.number,
+            });
+            if (pull.state !== "open") {
+              core.setFailed(`PR #${pull.number} is ${pull.state}; refusing to publish its preview.`);
+              return;
+            }
+            if (pull.head.sha !== process.env.EXPECTED_HEAD_SHA) {
+              core.setFailed(`PR #${pull.number} moved from ${process.env.EXPECTED_HEAD_SHA} to ${pull.head.sha}.`);
+            }
+
       - name: Publish preview manifest
         if: "!env.ACT"
         env:
-          AMD64_DIGEST: ${{ needs.container.outputs.digest }}
+          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: |
+          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
+
   cleanup:
     name: Clean up preview image
     if: github.event_name == 'pull_request_target' || (github.event_name == 'workflow_dispatch' && inputs.operation == 'cleanup')
@@ -347,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/skip-renovate-stability-days.yml

@@ -1,5 +1,6 @@
 permissions:
   statuses: write
+  contents: read
 
 on:
   pull_request:
@@ -16,12 +17,20 @@ jobs:
         env:
           GH_TOKEN: ${{secrets.GITHUB_TOKEN}}
         run: |
-          gh api \
-          --method POST \
-          -H "Accept: application/vnd.github+json" \
-          -H "X-GitHub-Api-Version: 2022-11-28" \
-          /repos/${{github.repository}}/statuses/${{github.event.pull_request.head.sha}} \
-          -f 'state=success' \
-          -f 'target_url=https://docs.renovatebot.com/configuration-options#minimumreleaseage' \
-          -f 'description=Skipped for non renovate branches' \
-          -f 'context=renovate/stability-days'
+          for attempt in 1 2 3 4 5; do
+            if gh api \
+              --method POST \
+              -H "Accept: application/vnd.github+json" \
+              -H "X-GitHub-Api-Version: 2022-11-28" \
+              /repos/${{github.repository}}/statuses/${{github.event.pull_request.head.sha}} \
+              -f 'state=success' \
+              -f 'target_url=https://docs.renovatebot.com/configuration-options#minimumreleaseage' \
+              -f 'description=Skipped for non renovate branches' \
+              -f 'context=renovate/stability-days' \
+              --silent; then
+              exit 0
+            fi
+            echo "status POST failed (attempt $attempt/5), retrying in 5s"
+            sleep 5
+          done
+          exit 1

.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

@@ -0,0 +1,146 @@
+name: Workshop
+
+on:
+  pull_request:
+  push:
+    branches: [dev, v2, release/v2, main]
+
+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
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-node@v6
+        with:
+          node-version: 24.18.0
+      - uses: pnpm/action-setup@v6
+        with:
+          run_install: false
+      - run: pnpm install --frozen-lockfile
+      - run: pnpm --filter @homarr/workshop typecheck
+      - run: pnpm --filter @homarr/docs typecheck
+      - run: docker compose --env-file apps/workshop/.env.staging.example -f apps/workshop/docker-compose.staging.yml config --quiet
+      - run: pnpm test:workshop
+      - run: pnpm test:workshop-image
+
+  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: 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/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

@@ -16,6 +16,7 @@ out/
 next-env.d.ts
 
 # artifacts
+.ai-evaluations/
 packages/db/migrations/*/migrate.cjs
 
 # nitro
@@ -24,6 +25,8 @@ packages/db/migrations/*/migrate.cjs
 
 # production
 build
+tools/homarr-dev/homarr
+tools/homarr-dev/homarr-dev
 
 # misc
 .DS_Store
@@ -71,10 +74,23 @@ apps/nextjs/public/images/background.png
 
 # personal agent config
 .opencode
-.agents/
+.agents/*
+!.agents/skills/
 skills-lock.json
 
 # docusaurus
 apps/docs/.docusaurus
 apps/docs/build
 .pnpm-store
+benchmark-results
+
+# local performance investigation (never ship benchmark data or restored backups)
+.widget-performance/
+.bench/
+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"]
+    }
+  }
+}

.oxfmtrc.json

@@ -3,5 +3,15 @@
   "printWidth": 120,
   "endOfLine": "lf",
   "sortPackageJson": true,
-  "ignorePatterns": ["**/*.cjs", "**/lang/**", "static-data/**", "CHANGELOG.md", "apps/docs/.docusaurus/**", "apps/docs/build/**", "apps/docs/blog/**"]
+  "ignorePatterns": [
+    "**/*.cjs",
+    "**/lang/**",
+    "static-data/**",
+    "CHANGELOG.md",
+    "apps/docs/.docusaurus/**",
+    "apps/docs/build/**",
+    "apps/docs/blog/**",
+    "packages/custom-widgets/src/core/component-catalog.generated.json",
+    "apps/docs/static/custom-widgets/component-catalog-v1.json"
+  ]
 }

.oxlintrc.json

@@ -30,7 +30,35 @@
   "options": {
     "reportUnusedDisableDirectives": "off"
   },
-  "ignorePatterns": ["**/*.config.js", "**/*.config.mjs", "**/*.cjs", "**/lang/*.d.json.ts", ".next/**", "apps/docs/.docusaurus/**", "apps/docs/build/**"],
+  "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",
+    "**/*.cjs",
+    "**/lang/*.d.json.ts",
+    ".next/**",
+    "apps/docs/.docusaurus/**",
+    "apps/docs/build/**"
+  ],
   "settings": {
     "react": { "version": "19" }
   }

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,12 +41,15 @@ homarr/
 │   ├── analytics/       # Server-side analytics (Umami)
 │   ├── server-settings/ # Server setting keys/types
 │   ├── settings/        # User-facing settings UI context
-│   ├── old-import/      # Legacy Homarr import
-│   ├── old-schema/      # Legacy Homarr zod schemas
+│   ├── 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
 │   └── github/          # CI setup action
+├── tools/
+│   └── homarr-dev/      # Go CLI for local and PR Docker images
 ├── development/         # Dev docker-compose (Redis, MySQL, PostgreSQL)
 ├── e2e/                 # E2E test specs
 └── Dockerfile           # Multi-stage production build
@@ -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
@@ -68,6 +72,9 @@ When modifying user-facing code, you MUST also update the corresponding document
 ## Monorepo Commands
 
 - `pnpm dev` — Next.js app only
+- `pnpm dev:cli -- dev` — run the developer CLI without installing a global binary
+- `pnpm db:seed` — seed default database data explicitly
+- `pnpm docker:dev:up` — start the Redis development service in the background
 - `pnpm dev:docs` — Docusaurus docs site only
 - `pnpm turbo build` — build all packages
 - `pnpm turbo build --filter=@homarr/docs` — build docs only
@@ -79,5 +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

AUDIT.md

@@ -1,535 +0,0 @@
-# Custom Widgets Architecture Audit and North Star
-
-> Status: implemented in the current working tree; baseline retained below for traceability
-> Evidence snapshot: `c5703e7e5` on PR #6304
-> Scope: built-in custom-widget displays, Custom JSX, network execution, authoring, preview, import/export, AI prompts, and MCP tools
-
-## Implementation outcome
-
-The migration described by this audit is implemented. `@homarr/custom-widgets` now owns the domain through explicit `core`, `jsx`, `runtime`, `server`, and `workbench` exports. API, Widgets, and Next.js retain only authorization, persistence, transport, board registration, navigation, and localized adapter concerns.
-
-Key outcomes:
-
-- One typed configuration and display-descriptor model drives schemas, defaults, form hydration, serialization, import/export, preview, examples, diagnostics, generated references, and AI prompts.
-- Display-data extraction moved out of API and Widgets into the domain package; the former API-to-Widgets re-export chain no longer exists.
-- The interpreter, shared security policy, registry, wrappers, named-request runtime, hardened executor, preview sessions, rate limits, and workbench UI have focused package-owned modules and tests.
-- Runtime and workbench network behavior is injected through typed ports. The domain package has no dependency on API, Widgets, Next.js routes, notification infrastructure, or modal infrastructure.
-- Public tRPC and MCP procedures are characterized, v2 and v3 import envelopes remain accepted, display-only v1 remains covered, and MCP offers iterative schema, validation, template read/write/patch, create/import/update, preview query, simulation, and journal tools.
-- The AI prompt uses a multiline two-block authoring bundle, documents the `SubFetch` render-child contract, and is generated from the canonical registry and tested examples.
-- Architecture enforcement currently scans 110 production modules for dependency direction, cycles, file budgets, dynamic loading, and untranslated JSX literals. Generated-reference drift and every Mantine export classification are test-enforced.
-- The latest production build measured the largest Custom JSX route payload at 99,852 gzip bytes across two chunks, below the 768 KiB budget.
-
-Focused verification is green: 278 package tests, 35 API/MCP tests, 52 Widgets renderer tests, 7 E2E tests, affected typecheck, affected lint, docs build, production Next.js build, architecture checks, generated drift, and the bundle budget. The root `pnpm test` command is presently blocked on this workstation by unrelated Docker-backed integration suites timing out while the shared Docker daemon is under external load; no Custom Widget test failed in those runs.
-
-## Executive summary
-
-The feature has a strong security direction and a capable authoring experience, but its implementation has outgrown its current ownership model. PR #6304 changes 56 files with 13,206 additions. The primary feature directories contain 10,437 lines, spread across `@homarr/widgets`, `@homarr/api`, `@homarr/definitions`, `@homarr/validation`, and the Next.js management route.
-
-The main problem is not the absolute line count. It is that domain policy, transport, persistence, rendering, form state, compatibility, and documentation generation are interleaved across package boundaries. A change to one display type can require synchronized edits in schemas, form defaults, import conversion, preview extraction, runtime rendering, documentation, and AI instructions. Several of those paths use untyped records, duplicated conversion logic, or direct API dependencies.
-
-The north star is a single `@homarr/custom-widgets` domain package with explicit `core`, `jsx`, `runtime`, `server`, and `workbench` entry points. Existing applications and packages become thin adapters. The extraction must preserve public APIs, import formats, permission behavior, and the current UI while improving internal cohesion.
-
-This audit does not authorize a big-bang rewrite. The migration should be a sequence of behavior-preserving PRs, beginning with characterization tests and ending with enforced dependency and complexity budgets.
-
-## Measured baseline
-
-### Change footprint
-
-| Measure                         | Current value |
-| ------------------------------- | ------------: |
-| PR files changed                |            56 |
-| PR additions                    |        13,206 |
-| PR deletions                    |         1,385 |
-| Primary feature-directory lines |        10,437 |
-
-Generated component-reference JSON accounts for 2,491 added lines and is not treated as source complexity.
-
-### Largest production files
-
-| File                                                                            | Lines | Responsibilities currently combined                                                                                                                                                   |
-| ------------------------------------------------------------------------------- | ----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `apps/nextjs/src/app/[locale]/manage/custom-widgets/_custom-widget-form.tsx`    | 1,911 | Schema refinement, defaults, server-error mapping, form conversion, submission, preview state, focus management, display picker, connection fields, and every display-specific editor |
-| `packages/api/src/router/custom-widget/custom-widget-router.ts`                 |   978 | CRUD, import/export, template patching, MCP descriptions, preview sessions, preview execution, journals, and action simulation/execution                                              |
-| `packages/widgets/src/custom-api/safe-jsx-interpreter.tsx`                      |   944 | AST model, parsing, environments, budgets, sanitization, expression evaluation, safe methods, callbacks, and React rendering                                                          |
-| `apps/nextjs/src/app/[locale]/manage/custom-widgets/_custom-widget-preview.tsx` |   834 | Preview orchestration, error boundary, tabs, response tree, diagnostics, request journal, sample data, and renderer selection                                                         |
-| `packages/widgets/src/custom-api/jsx-whitelist.ts`                              |   775 | Mantine imports, wrappers, icon mapping, runtime component map, registry filtering, data sanitization, and safe bindings                                                              |
-| `packages/widgets/src/custom-api/jsx-sub-fetch.tsx`                             |   599 | Query rendering, render props, path display, action execution, buttons, toggles, refresh, notifications, and confirmations                                                            |
-
-These files exceed the proposed 300-line production-module target. The interpreter is a reasonable candidate for a documented 400-line exception after its independent policies, evaluators, and renderer are extracted.
-
-### Current ownership
-
-```mermaid
-flowchart LR
-  D["@homarr/definitions<br/>registry and examples"]
-  V["@homarr/validation<br/>schemas and AST diagnostics"]
-  W["@homarr/widgets<br/>renderers and interpreter"]
-  A["@homarr/api<br/>CRUD, permissions, execution and MCP"]
-  N["Next.js route<br/>workbench, preview and prompt"]
-  X["Docs<br/>generated reference and guides"]
-
-  N --> A
-  N --> V
-  N --> D
-  N --> W
-  W --> A
-  W --> D
-  A --> V
-  X --> D
-```
-
-The `@homarr/widgets → @homarr/api` edge is particularly costly. Runtime request components call the generated tRPC client directly, so moving the domain into a package that is also consumed by the API would create a dependency cycle unless request execution is inverted behind a typed port.
-
-## What is working well
-
-- Custom JSX v2 replaces raw runtime URLs and methods with named, typed requests.
-- Board permissions, network scope, DNS validation, redirect policy, response limits, caching, concurrency, and action rules are server-enforced.
-- The safe interpreter no longer treats an upstream JSX parser as a sandbox.
-- Component metadata drives runtime classification, editor completion, docs generation, and part of the AI prompt.
-- The workbench supports multiline JSX, diagnostics, real preview sizes, response inspection, request journals, import review, undo/redo, and paste-to-import.
-- MCP exposes schema, validation, preview, journal, template read/write/patch, import, and update workflows without exposing stored secrets.
-- Shared examples cover simple metrics, nested queries, charts, actions, and richer interactive layouts.
-
-The migration must preserve these capabilities. Package extraction is not a reason to weaken the security boundary or remove authoring features.
-
-## Findings
-
-### P1 — Domain ownership is fragmented
-
-Custom-widget behavior is implemented in five packages/applications. None of them is the clear source of truth for the complete lifecycle. `@homarr/definitions` owns component metadata and examples, `@homarr/validation` owns schemas and template diagnostics, `@homarr/widgets` owns runtime evaluation, `@homarr/api` owns network and persistence flows, and Next.js owns authoring transformations.
-
-Impact:
-
-- Maintainers must search unrelated packages to understand one behavior.
-- Changes have a large synchronization surface and can drift silently.
-- The domain cannot be tested or reused as a coherent unit.
-- Package names describe infrastructure location rather than feature ownership.
-
-### P1 — Giant modules mix unrelated reasons to change
-
-The largest files are not merely long; they combine policy, orchestration, state, and presentation. The form contains all display editors. The router contains every management and preview procedure. The interpreter contains parsing through React emission. The request component file contains both query and mutation interaction models.
-
-Impact:
-
-- Reviews are broad and regression-prone.
-- Unit-test seams are difficult to identify.
-- Merge conflicts concentrate in a small number of files.
-- Small feature changes require understanding thousands of lines of adjacent behavior.
-
-### P1 — Runtime code depends directly on the API client
-
-`packages/widgets/src/custom-api/component.tsx` and `jsx-sub-fetch.tsx` import `@homarr/api/client`. They also directly invoke notifications and confirmation modals.
-
-Impact:
-
-- The renderer cannot be used or tested without application infrastructure.
-- A future `@homarr/custom-widgets` package would cycle with `@homarr/api` if both retained these imports.
-- Preview and board runtime cannot share the same renderer through different request implementations without branching inside the components.
-
-Required direction: a runtime provider must receive typed query, action, confirmation, notification, and invalidation ports. The board and preview layers supply adapters.
-
-### P1 — Configuration transformations are duplicated
-
-Create defaults and builders live in the form, edit hydration lives in the edit page, and import hydration lives in `_custom-widget-import-utils.ts`. These paths independently translate between stored display configs and form values. They rely on display-type switches, record casts, and JSON text fields such as the request manifest.
-
-Impact:
-
-- Create, edit, paste replacement, import, export, and MCP can disagree.
-- Adding a field requires updating multiple transforms.
-- Round trips are difficult to prove lossless.
-
-Required direction: each display type supplies one typed descriptor containing schema, defaults, `toForm`, `fromForm`, preview projection, and migration behavior.
-
-### P1 — Type safety degrades at domain boundaries
-
-`Record<string, unknown>`, `as never`, and `as unknown as` are frequent in form conversion, display extraction, preview state, imports, registry wrappers, and API parsing. Some casts are necessary at the interpreter/React boundary, but most domain-level casts indicate missing discriminated unions or validated adapters.
-
-Impact:
-
-- Invalid combinations survive until runtime.
-- Refactors do not receive complete compiler guidance.
-- Server and client transformations can diverge while continuing to compile.
-
-Required direction: parse unknown values once at ingress and use typed domain objects afterward. Unsafe casts must be isolated to named boundary modules and justified by tests.
-
-### P1 — Security policy is represented more than once
-
-The template validator and interpreter both parse JSX and maintain concepts such as blocked properties, blocked props, AST depth, and operation limits. Runtime component filtering adds another policy layer.
-
-The analyzer and interpreter have different jobs, so they should not be collapsed into one evaluator. They must, however, consume one immutable policy definition and shared AST normalization utilities.
-
-Impact:
-
-- A property can be rejected by one layer and missed by another.
-- Security changes require parallel edits and duplicate tests.
-- Diagnostics can describe behavior that differs from runtime enforcement.
-
-### P1 — The API router combines transport and application behavior
-
-The router owns tRPC metadata, Zod inputs, database writes, encryption, import/export, template revisions, preview execution, rate-limit acquisition, journal recording, and MCP documentation.
-
-Impact:
-
-- Domain logic is only testable through tRPC context setup.
-- MCP and browser endpoints can accidentally implement different workflows.
-- Framework-specific `TRPCError` values leak into lower-level executor and manifest code.
-
-Required direction: tRPC procedures authorize, load persistence models, call a domain service, and map domain errors. They do not implement request rendering, template patching, preview execution, or import conversion inline.
-
-### P2 — Metadata generation is only partially centralized
-
-The component registry and examples are shared, but runtime maps, wrappers, safe bindings, display-type metadata, AI prompt prose, form choices, and some docs remain separately assembled. The AI prompt is built inside a client button component.
-
-Impact:
-
-- Agent instructions can drift from validation and runtime behavior.
-- Prompt generation requires UI and network context.
-- Display types lack the same single-registry guarantee as JSX components.
-
-Required direction: prompt generation is a pure function in `core`, using the schema, display descriptors, component registry, and tested fixtures. The UI only fetches context and copies the result.
-
-### P2 — Compatibility behavior is mixed into primary flows
-
-V1 detection, migration warnings, legacy network diagnostics, v2 imports, v3 exports, and fallback display parsing are embedded beside current authoring/runtime logic.
-
-Impact:
-
-- Happy paths are harder to read.
-- Legacy behavior can accidentally influence v2 code.
-- Compatibility retirement has no obvious deletion boundary.
-
-Required direction: version detection and migrations live under `core/migrations`. Runtime and workbench receive a normalized current model plus explicit review state.
-
-### P2 — Test topology does not mirror the architecture
-
-Interpreter coverage is substantial, and request-executor/router tests exist, but tests are colocated under their current infrastructure owners instead of a feature package. A focused renderer run passed 52 tests during review, while the selected API suites failed before collecting tests because the root Vitest client environment rejected server-only environment access.
-
-Impact:
-
-- The complete feature cannot be verified with one package command.
-- Server test failures can be configuration failures rather than behavioral failures.
-- Form conversion and workbench orchestration have limited direct characterization coverage relative to their size.
-
-Required direction: the package owns focused test projects or environment-specific configs for core, DOM runtime/workbench, and Node server tests. API adapter tests remain in `@homarr/api`.
-
-### P2 — A small amount of user-facing copy bypasses translation
-
-Examples found during the snapshot include the raw-response tooltip and a default empty template message. Dynamic translation keys also require repeated `as never` casts, reducing translation-key safety.
-
-Impact:
-
-- Locale completeness gates are unreliable.
-- Refactoring copy is harder than changing typed translation keys.
-
-Required direction: all package UI receives a typed message catalog or uses typed scoped translations. No visible fallback literals are allowed in production components.
-
-## North-star package
-
-```text
-packages/custom-widgets/
-├── src/core/
-│   ├── config/          # discriminated display configurations and form models
-│   ├── displays/        # typed display descriptors and built-in display metadata
-│   ├── import/          # v2/v3 parsing, export, review, and authoring bundles
-│   ├── migrations/      # v1 detection, normalization, and review requirements
-│   ├── prompts/         # pure AI prompt generation
-│   └── examples/        # typed fixtures shared by tests, docs, editor, and prompts
-├── src/jsx/
-│   ├── ast/             # parser adapter, AST types, traversal, and normalization
-│   ├── policy/          # blocked properties, props, URLs, and budgets
-│   ├── analyzer/        # authoring diagnostics
-│   ├── interpreter/     # expression and collection evaluation
-│   ├── registry/        # component descriptors, wrappers, and export classification
-│   └── bindings/        # branded safe helpers and sanitized data
-├── src/runtime/
-│   ├── displays/        # built-in renderers
-│   ├── jsx/             # Custom JSX renderer and error containment
-│   ├── requests/        # SubFetch, actions, toggles, refresh, and state handling
-│   └── provider/        # injected runtime capabilities
-├── src/server/
-│   ├── network/         # hardened executor and destination policy
-│   ├── requests/        # manifest resolution and parameter substitution
-│   ├── limits/          # rate and concurrency limits
-│   └── preview/         # sessions, simulation, and journals
-└── src/workbench/
-    ├── form/            # shared state and connection/display sections
-    ├── editor/          # CodeMirror and registry-driven diagnostics
-    ├── preview/         # widget, response, journal, and diagnostic views
-    └── import/          # clipboard parsing and review UI
-```
-
-Public exports are explicit:
-
-```json
-{
-  "exports": {
-    "./core": "./src/core/index.ts",
-    "./jsx": "./src/jsx/index.ts",
-    "./runtime": "./src/runtime/index.ts",
-    "./server": "./src/server/index.ts",
-    "./workbench": "./src/workbench/index.ts"
-  }
-}
-```
-
-There is no broad root barrel. Internal folders cannot be imported by consumers.
-
-### Dependency rules
-
-```mermaid
-flowchart LR
-  C["custom-widgets/core"]
-  J["custom-widgets/jsx"]
-  R["custom-widgets/runtime"]
-  S["custom-widgets/server"]
-  B["custom-widgets/workbench"]
-  API["@homarr/api adapter"]
-  W["@homarr/widgets adapter"]
-  N["Next.js route adapter"]
-  DOC["Docs generator"]
-
-  J --> C
-  R --> C
-  R --> J
-  S --> C
-  B --> C
-  B --> R
-  API --> C
-  API --> S
-  W --> C
-  W --> R
-  N --> C
-  N --> B
-  DOC --> C
-  DOC --> J
-```
-
-Hard rules:
-
-1. `@homarr/custom-widgets` never imports `@homarr/api`, `@homarr/widgets`, or Next.js route modules.
-2. `core` has no React, Mantine, tRPC, database, Redis, or browser dependency.
-3. `jsx` has no API, persistence, Redis, notification, or modal dependency.
-4. `runtime` performs no direct tRPC calls. It consumes `CustomWidgetRuntimePort`.
-5. `workbench` performs no direct tRPC calls. It consumes `CustomWidgetWorkbenchPort` callbacks.
-6. `server` has no tRPC or database-query dependency. API adapters load authorized records and map errors.
-7. Cross-entry imports follow the arrows above; reverse imports fail CI.
-
-### Runtime ports
-
-The exact transport remains owned by adapters. The domain contract should cover behavior rather than tRPC details:
-
-```ts
-interface CustomWidgetRuntimePort {
-  getData(input: { itemId: string; signal?: AbortSignal }): Promise<CustomWidgetRequestResult>;
-  query(input: NamedRequestInvocation & { signal?: AbortSignal }): Promise<CustomWidgetRequestResult>;
-  action(input: NamedRequestInvocation & { confirmed?: boolean }): Promise<CustomWidgetRequestResult>;
-  confirm(input: ActionConfirmation): Promise<boolean>;
-  notify(input: RuntimeNotification): void;
-  invalidate(input: RuntimeInvalidation): Promise<void>;
-}
-```
-
-Board runtime and preview runtime implement the same port. Preview simulation is an adapter capability, not a conditional tRPC import inside `ActionButton`.
-
-### Display descriptors
-
-Every display type is represented once:
-
-```ts
-interface CustomWidgetDisplayDescriptor<TConfig, TForm> {
-  type: CustomWidgetDisplayType;
-  configSchema: ZodType<TConfig>;
-  formSchema: ZodType<TForm>;
-  createDefault(): TConfig;
-  toForm(config: TConfig): TForm;
-  fromForm(form: TForm): TConfig;
-  migrate(input: unknown): DisplayMigrationResult<TConfig>;
-  extract(response: unknown, config: TConfig): DisplayModel;
-  capabilities(config: TConfig): CustomWidgetCapability[];
-}
-```
-
-UI fields and renderer components may be registered in runtime/workbench companion maps keyed by the same typed display identifier. Domain descriptors remain serializable and framework-independent.
-
-## Developer-experience north star
-
-### Maintainers
-
-- Start at `packages/custom-widgets` for every feature behavior.
-- Find one module per concept and one descriptor per display type.
-- Add a display type without editing central switches in multiple packages.
-- Run one package command for core, DOM, and server tests.
-- Receive compile-time failures when a configuration field is not handled by forms, preview, migration, or export.
-- Review PRs that move one domain boundary at a time.
-
-### Administrators and template authors
-
-- Preserve the current continuous form and live workbench.
-- Keep preview usable before a live response exists through schema-valid defaults and editable sample data.
-- Keep diagnostics actionable, localized, clickable, and consistent with runtime policy.
-- Keep imports reviewable and secrets excluded.
-- Keep query and action capabilities visible without noisy permanent warnings.
-
-### AI agents
-
-- Obtain schema, registry, limits, examples, and prompt rules from the same typed sources.
-- Use readable multiline templates through authoring bundles and line-based template tools.
-- Validate, preview, inspect journals, patch, and revalidate without rewriting unrelated configuration.
-- Receive stable machine-actionable issue codes in addition to localized or human-readable messages.
-- Never need to infer runtime behavior from UI-only prompt strings.
-
-## Fragmentation rules
-
-- Production modules target at most 300 lines, excluding generated files, fixtures, and type-only declarations.
-- Algorithmic modules can reach 400 lines only with a file-level rationale and focused tests.
-- A module has one primary reason to change; moving lines without separating policy from orchestration does not satisfy the target.
-- React components do not contain schema definitions or persistence transforms.
-- Routers do not contain reusable domain algorithms.
-- Domain functions do not throw framework-specific errors.
-- Unknown input is validated once. Parsed values are not carried as `Record<string, unknown>` through internal layers.
-- Compatibility code lives in versioned migration modules and has explicit removal criteria.
-- Generated artifacts are reproducible and checked for drift, but excluded from line budgets.
-
-## Migration roadmap
-
-### PR 1 — Characterize contracts
-
-- Add round-trip tests for every display descriptor: default → form → config, stored config → form → config, and import → export.
-- Add fixtures for v1 display-only, v1 network-review-required, v2 import, and v3 export.
-- Add prompt snapshots sourced from the component registry and examples.
-- Split Node and DOM Vitest projects so server suites collect and run reliably.
-- Record bundle and render baselines before moving modules.
-
-Gate: all existing behavior is represented by tests, with no production moves yet.
-
-### PR 2 — Establish `core`
-
-- Create `@homarr/custom-widgets` and explicit exports.
-- Move custom-widget schemas, typed configs, display descriptors, examples, import/export, migration, capability analysis, and prompt generation into `core`.
-- Replace form/edit/import conversion duplication with descriptor calls.
-- Temporarily re-export legacy imports from definitions and validation to keep consumers stable.
-
-Gate: create, edit, import, export, MCP validation, and AI prompt generation use the same domain contracts.
-
-### PR 3 — Extract JSX policy and interpreter
-
-- Move AST types, parser adapter, shared security policy, analyzer, evaluator, budgets, bindings, and registry into `jsx`.
-- Separate evaluator modules by expression family and React emission.
-- Generate diagnostics and runtime enforcement from the same policy constants.
-- Keep the Mantine export-classification CI check.
-
-Gate: the security suite passes unchanged, analyzer/runtime policy drift tests pass, and no consumer imports JSX internals.
-
-### PR 4 — Extract runtime
-
-- Move built-in renderers, Custom JSX display, SubFetch, actions, toggles, refresh, and error containment into `runtime`.
-- Introduce the runtime port and adapters for board and preview contexts.
-- Remove direct imports of the API client, modals, and notifications from domain components.
-- Split request components into query, action, toggle, refresh, feedback, and shared-state modules.
-
-Gate: board rendering and workbench preview use the same runtime components through different adapters; actions retain confirmation, rollback, invalidation, and permission behavior.
-
-### PR 5 — Extract server services
-
-- Move executor, manifests, network policy, limits, caching/single-flight, and preview-session logic into `server`.
-- Replace `TRPCError` below the adapter with typed domain errors.
-- Split API procedures into management, templates, preview, and runtime routers that delegate to package services.
-- Keep authorization, database lookup, encryption, and tRPC/MCP metadata in `@homarr/api`.
-
-Gate: browser and MCP flows call the same services; request security tests run as Node package tests; public procedure names and inputs remain compatible.
-
-### PR 6 — Extract and fragment workbench
-
-- Move reusable editor, preview, response tree, import review, connection section, display picker, and display-specific fields into `workbench`.
-- Introduce a workbench port for validate, preview, query, simulate action, journal, and save callbacks.
-- Keep Next.js pages responsible only for routing, loading initial data, and constructing adapters.
-- Replace the monolithic form with small sections and descriptor-driven display fields while preserving the continuous form, two-pane scrolling, autofocus, and mobile modes.
-
-Gate: no workbench source file exceeds the agreed budget, and create/edit/paste replacement share one state model.
-
-### PR 7 — Remove scaffolding and enforce boundaries
-
-- Remove compatibility re-exports and old implementations after all consumers move.
-- Add CI checks for forbidden imports, dependency cycles, source-size budgets, untranslated literals, generated-artifact drift, component classification, and custom-JSX chunk size.
-- Update contributor and architecture documentation with package entry points and extension recipes.
-
-Gate: old ownership paths contain only thin adapters or are deleted.
-
-## Verification strategy
-
-### Core
-
-- Every display descriptor accepts valid data and rejects mismatched configuration.
-- All create/edit/import/export transformations are lossless where expected.
-- V1/v2/v3 compatibility and review states are deterministic.
-- Prompt output, authoring bundles, fixtures, docs data, and completion data are generated from shared sources.
-
-### JSX
-
-- Computed and Unicode-obfuscated reflective access remains blocked.
-- Analyzer and interpreter share property, prop, URL, and budget policy.
-- Own-property resolution, branded calls, callback accounting, and node/operation limits remain enforced.
-- Every upstream Mantine export is classified and every enabled runtime component resolves.
-
-### Runtime and workbench
-
-- Query cancellation, stale results, retries, render children, action locks, DELETE confirmation, toggle rollback, and invalidation behave identically in preview and boards.
-- Error boundaries isolate template and display failures.
-- Empty, sample, stale, loading, failure, and success states are localized and accessible.
-- Keyboard, focus, responsive, reduced-motion, and narrow-widget behavior remain covered.
-
-### Server and adapters
-
-- Board IDOR, permission levels, anonymous actions, named-request kinds, substitutions, DNS classes, redirects, headers, response limits, caching, and rate limits remain covered.
-- Server tests run under an explicit Node environment rather than failing during client-environment initialization.
-- MCP schemas and descriptions remain discoverable, stable, and absent from unsafe runtime procedures.
-
-### Required commands
-
-At the end of the migration, the package and repository must pass:
-
-```sh
-pnpm --filter @homarr/custom-widgets test
-pnpm test
-pnpm test:e2e
-pnpm turbo typecheck --affected
-pnpm turbo lint --affected
-pnpm turbo build --filter=@homarr/docs
-pnpm check:custom-widget-bundle # after the Next.js production build
-```
-
-CI additionally checks dependency direction, cycles, file budgets, generated references, translations, and client bundle size.
-
-## Completion criteria
-
-- `@homarr/custom-widgets` owns every reusable custom-widget domain behavior.
-- No circular dependencies exist.
-- The package does not import `@homarr/api`, `@homarr/widgets`, or Next.js route modules.
-- Runtime and workbench networking uses injected typed ports.
-- One typed descriptor is the source of truth for each display type.
-- One shared JSX policy drives authoring diagnostics and runtime enforcement.
-- Create, edit, import, export, preview, MCP, and board runtime use the same typed transformations.
-- Public tRPC/MCP names, import formats, stored configuration, and permission behavior remain compatible.
-- V1 display-only migration and network-review states remain tested.
-- Production modules satisfy the 300/400-line budgets.
-- No untranslated user-facing strings remain.
-- Core, JSX, runtime, server, workbench, integration, E2E, accessibility, docs, and bundle checks pass.
-- A maintainer can locate a custom-widget behavior from the package structure without searching unrelated packages.
-
-## Explicit non-goals
-
-- Replacing Mantine or Homarr's visual language.
-- Allowing arbitrary cross-origin requests.
-- Replacing named requests with general JavaScript execution.
-- Changing stored secrets or exposing them through export or MCP.
-- Redesigning the current management UX during the package extraction.
-- Removing compatibility formats before migration and review flows are proven.
-
-## Decision record
-
-- The package owns all Custom Widget behavior, not only Custom JSX.
-- Security and correctness are hard constraints.
-- Maintainer simplicity is the primary tie-breaker after those constraints.
-- Current user and agent workflows are preserved during extraction.
-- Generated artifacts do not count toward source-size budgets.
-- Migration occurs through reviewable, behavior-preserving PRs rather than a single rewrite.

CHANGELOG.md

@@ -1,3 +1,19 @@
+## [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)
+
+## [1.72.0](https://github.com/homarr-labs/homarr/compare/v1.71.0...v1.72.0) (2026-07-24)
+
+## [1.71.0](https://github.com/homarr-labs/homarr/compare/v1.70.0...v1.71.0) (2026-07-17)
+
 ## [1.70.0](https://github.com/homarr-labs/homarr/compare/v1.69.2...v1.70.0) (2026-07-10)
 
 ## [1.69.2](https://github.com/homarr-labs/homarr/compare/v1.69.1...v1.69.2) (2026-07-06)

CHANGES.md

@@ -1,96 +0,0 @@
-# Changes
-
-## Goal
-
-Remove widget-only services from Homarr's global Integration system.
-
-The affected services are release providers and Search.ch. They are only used by specific widgets, so keeping them as global integrations added unnecessary setup, UI, database rows, docs pages, and integration package code.
-
-ArchiveTeam Warrior remains a proper integration but is no longer auto-seeded on first install.
-
-## Why
-
-These services do not need shared integration state.
-
-- Release providers are selected per Releases widget repository.
-- Search.ch is only used by the Timetable widget.
-
-Moving them into widget options makes configuration simpler and removes dead-weight integration code from `packages/integrations`.
-
-## What Changed
-
-### Release Providers
-
-- Added release provider definitions in `packages/definitions/src/release-provider.ts`.
-- Removed release providers from `IntegrationKind`.
-- Moved release-fetching code out of `packages/integrations` and into `packages/request-handler/src/release-providers.ts`.
-- Updated the Releases widget to store provider configuration directly in widget options:
-  - `provider`
-  - `identifier`
-  - `versionFilter`
-  - `providerUrl`
-- Updated the Releases widget editor to use a provider select instead of an integration select.
-- Updated Docker import mapping so `ghcr.io` maps to `gitHubContainerRegistry`.
-- GitHub Container Registry now uses the public OCI registry API and accepts full image references such as `ghcr.io/homarr-labs/homarr:latest`.
-
-### Timetable / Search.ch
-
-- Removed Search.ch as an integration.
-- Added a Timetable widget `baseUrl` option, defaulting to `https://search.ch`.
-- Moved Search.ch request/parsing logic into `packages/request-handler/src/timetable.ts`.
-- Updated the Timetable API to receive `baseUrl` directly from widget options.
-
-### ArchiveTeam Warrior
-
-- Kept as a proper integration (not removed).
-- Removed `defaultUrl` from the integration definition to prevent auto-seeding on first install.
-
-### Integration Cleanup
-
-- Removed creators, exports, docs references, and implementation files for the deleted integrations.
-- Removed unused dependencies from `packages/integrations/package.json`.
-
-### Database Migration
-
-- Added `packages/db/migrations/custom/0003_remove_widget_only_integrations.ts`.
-- The migration moves old integration-linked widget config into widget options, then deletes the old widget-only integration rows.
-- Updated the earlier release widget migration to use the new `provider` field instead of `providerIntegrationId`.
-
-### Docs
-
-- Updated Releases widget docs to describe providers instead of integrations.
-- Updated Timetable docs to remove Search.ch integration setup.
-- Removed obsolete integration docs pages for the deleted integration kinds.
-- Updated docs sitemap and integration docs mappings.
-
-### Translations
-
-- Added English labels for the new widget options:
-  - `widget.timetable.option.baseUrl.label`
-  - `widget.releases.option.repositories.providerUrl.label`
-
-## How It Works Now
-
-Release provider configuration lives on each Releases widget repository entry. The request handler resolves provider metadata and fetches releases directly from the provider-specific endpoint. GHCR uses anonymous OCI registry access for public packages.
-
-Timetable passes its widget URL option directly to its API router and request handler. No global integration lookup is needed.
-
-ArchiveTeam Warrior continues to use the standard integration system, but users must manually add the integration (it is not auto-created on install).
-
-## Deliberate Non-Goals
-
-- No provider secret/token support was added.
-- No new secret storage model was introduced.
-- No compatibility layer was kept in `packages/integrations`.
-
-Widget options are client-visible, so storing provider credentials there would be wrong. If authenticated provider requests are needed later, they need a separate secret-storage design.
-
-## Verification So Far
-
-- Focused typechecks passed for affected packages.
-- Full `pnpm turbo typecheck` passed.
-- Full `pnpm lint` passed with existing warnings.
-- Focused release provider normalization tests passed.
-- Widget translation test passed.
-- Live GHCR smoke checks passed for `ghcr.io/muchobien/pocketbase:latest` and `ghcr.io/homarr-labs/homarr:latest`.
-- `pnpm test packages/integrations/test/pi-hole.spec.ts` passed earlier, but failed on rebased reruns because Pi-hole reported `domainsBeingBlocked` as `-2`/`0` instead of `> 1`.

CODEOWNERS

@@ -206,6 +206,14 @@ packages/integrations/src/unraid @manuel-rw
 apps/docs/docs/integrations/uptime-kuma @ajnart
 packages/integrations/src/uptime-kuma @ajnart
 
+# What's Up Docker (WUD) - introduced in https://github.com/homarr-labs/homarr/pull/6523 by @tiimonn
+apps/docs/docs/integrations/whats-up-docker @tiimonn
+apps/docs/docs/widgets/whats-up-docker @tiimonn
+packages/api/src/router/widgets/wud.ts @tiimonn
+packages/integrations/src/wud @tiimonn
+packages/request-handler/src/wud.ts @tiimonn
+packages/widgets/src/wud @tiimonn
+
 # Traefik - by @Nerdy-Technician
 apps/docs/docs/integrations/traefik @Nerdy-Technician
 apps/docs/docs/widgets/traefik @Nerdy-Technician

Dockerfile

@@ -3,12 +3,18 @@
 FROM node:24.18.0-alpine AS base
 
 FROM base AS builder
+ARG TARGETPLATFORM
 WORKDIR /app
-RUN apk add --no-cache libc6-compat curl bash && apk update
+# Native dependencies normally use prebuilds, but the build must remain
+# reproducible when a prebuild download times out and compilation is required.
+RUN apk add --no-cache libc6-compat curl bash python3 make g++
 
 RUN corepack enable pnpm
-COPY pnpm-lock.yaml pnpm-workspace.yaml package.json ./
+COPY .npmrc pnpm-lock.yaml pnpm-workspace.yaml package.json ./
 COPY patches ./patches
+COPY --parents ./apps/*/package.json ./packages/*/package.json ./tooling/*/package.json ./
+# @homarr/definitions generates documentation types during install.
+COPY --parents ./packages/definitions/src ./
 # Workaround for pnpm/pnpm#5268: pnpm fetch crashes when patchedDependencies
 # are configured with nodeLinker: hoisted. The applyPatchToDir function tries
 # to chdir into node_modules/<pkg> which doesn't exist during fetch (only the
@@ -16,17 +22,19 @@ COPY patches ./patches
 # isolated linker, patches apply inside the virtual store (node_modules/.pnpm/...)
 # which IS created by pnpm fetch. The original hoisted linker is restored
 # before the install step so the final node_modules layout stays flat.
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
+RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
     pnpm config set store-dir /pnpm/store && \
     sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
-    pnpm fetch && \
+    pnpm fetch --ignore-scripts && \
     sed -i 's/nodeLinker: isolated/nodeLinker: hoisted/' pnpm-workspace.yaml
 
+# Install only from the fetched, committed lockfile so local and Docker builds
+# resolve the same dependency graph. Serial lifecycle builds avoid esbuild's
+# atomic binary replacement racing across the hoisted workspace (pnpm/pnpm#8200).
+RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
+    npm_config_nodedir=/usr/local pnpm install --recursive --offline --frozen-lockfile --child-concurrency=1
+
 COPY . .
-# Follow the pnpm fetch pattern from https://pnpm.io/cli/fetch
-# --frozen-lockfile is omitted as recommended by the pnpm fetch docs
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
-    pnpm install --recursive
 
 ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'
@@ -37,7 +45,9 @@ RUN --mount=type=secret,id=TURBO_API,env=TURBO_API \
     --mount=type=secret,id=TURBO_TEAM,env=TURBO_TEAM \
     --mount=type=secret,id=TURBO_TOKEN,env=TURBO_TOKEN \
     --mount=type=secret,id=TURBO_REMOTE_CACHE_SIGNATURE_KEY,env=TURBO_REMOTE_CACHE_SIGNATURE_KEY \
-    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}" pnpm build
+    --mount=type=cache,id=homarr-next-build-${TARGETPLATFORM},target=/app/apps/nextjs/.next/cache,sharing=locked \
+    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}" \
+    pnpm turbo build --filter=@homarr/nextjs... --filter=@homarr/cli
 
 FROM base AS runner
 WORKDIR /app
@@ -85,5 +95,6 @@ ENV AUTH_PROVIDERS='credentials'
 ENV REDIS_IS_EXTERNAL='false'
 ENV NODE_ENV='production'
 
+EXPOSE 7575
 ENTRYPOINT [ "/app/entrypoint.sh" ]
 CMD ["sh", "run.sh"]

apps/docs/README.md

@@ -21,8 +21,14 @@ pnpm dev:docs
 
 # Or from within this directory
 pnpm dev
+
+# Point the docs at a local PocketBase instance
+WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
 ```
 
+The standalone docs use `WORKSHOP_API_URL` for PocketBase and `HOMARR_WEBSITE_URL` for the public site origin. The old
+`WORKSHOP_URL` name is a deprecated one-release alias.
+
 ## Build
 
 ```bash
@@ -40,7 +46,7 @@ Uses oxlint and oxfmt (same as the rest of the monorepo):
 ```bash
 pnpm lint        # oxlint
 pnpm format      # oxfmt (check)
-pnpm format -- --write  # oxfmt (fix)
+pnpm format:fix    # oxfmt (fix)
 ```
 
 ## Typecheck
@@ -55,8 +61,8 @@ pnpm typecheck
 docs/
 ├── getting-started/    # Installation guides, glossary, prerequisites
 ├── management/         # Boards, apps, users, integrations, settings, tasks, API
-├── integrations/       # 55 integration guides (one folder each)
-├── widgets/            # 42 widget guides (one folder each)
+├── integrations/       # 56 integration guides (one folder each)
+├── widgets/            # 43 widget guides (one folder each)
 ├── advanced/           # SSO, env vars, proxy, styling, CLI, development
 └── community/          # FAQ, donate, license, translations, get-in-touch
 ```
@@ -93,7 +99,7 @@ pnpm verify:search
 | Layer          | Technology                                  |
 | -------------- | ------------------------------------------- |
 | Site generator | Docusaurus 3 (`@docusaurus/preset-classic`) |
-| Styling        | Tailwind CSS 3 + Docusaurus Infima          |
+| Styling        | Tailwind CSS 4 + Docusaurus Infima          |
 | Icons          | `@tabler/icons-react`                       |
 | Diagrams       | Mermaid (`@docusaurus/theme-mermaid`)       |
 | Search         | Algolia DocSearch                           |
@@ -102,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/blog/2024/09-23-version-1.0/index.mdx

@@ -13,8 +13,6 @@ This will be a one time occurrence and version > ``1.0`` will have less breaking
 This time more important than every; **read the breaking changes** list and **create a backup** before updating.
 Some third party installation methods may take multiple days or weeks to update to the new version.
 
-See [this guide on how to import your previous Homarr dashboard](/docs/getting-started/after-the-installation#importing-a-zip-from-version-before-100)
-
 ## Changes at a glance
 - **Asynchronous integrations system**: In versions prior to ``1.0``, we fetched data upon each request synchronously.
 This means that the user had to wait for the requests to finish so any data would appear.

apps/docs/blog/2025/01-19-migration-guide-1.0/index.mdx

@@ -10,12 +10,11 @@ If you are still on a version before 0.15.10, please update to 0.15.10 where we
 
 <!-- truncate -->
 
-## Export your data
+## Preserve your old installation
 
-As 1.0 is a complete rewrite of Homarr and therefor not compatible with the old docker mounts, we need to export your data first.
-For this you can navigate to the `Migrate to 1.0` page which you can find under `Management` > `Tools` > `Migrate to 1.0`.
-Here you can select which things you want to export and download the zip file.
-It will also show you a secret key which you will need to import the secret data like user password hashes, salts and integration secrets.
+Homarr 1.0 is a complete rewrite and cannot reuse the old Docker mounts. Keep the 0.15 installation and its data intact while you build the replacement. The historical `Management` > `Tools` > `Migrate to 1.0` export can still be kept as a record, but current Homarr releases cannot import that ZIP or its secret key.
+
+Plan to recreate your apps, integrations, and boards manually in the new installation. A SQLite database backup can be restored from the onboarding welcome screen only when it was created by a compatible current Homarr release; it is not a conversion path for a 0.15 database.
 
 ![Export page](./img/old-homarr-export-data.png)
 
@@ -28,28 +27,15 @@ Please note that if you are using docker you need to specify a diffrent external
 So in your compose file the ports would be `7576:7575` instead of `7575:7575`.
 
 ## Import your data
-Once the installation is completed you can access the new installation. During the onboarding you'll need to select `Import from Homarr before 1.0`.
 
-![Onboarding initial step](./img/onboarding-step-1.png)
+:::warning Legacy guide
 
-After that you can upload the zip file you downloaded in the first step.
+The pre-1.0 ZIP importer is no longer included in current Homarr releases. Keep the old installation available until you have manually verified the replacement. Compatible SQLite backups from current releases can still be restored from the onboarding welcome screen.
 
-![Onboarding import dropzone](./img/old-homarr-import-dropzone.png)
-
-After that you'll get a list with all your boards that can be imported. You can configure how it should be imported and can select which screensizes it should import.
-
-![Onboarding import list](./img/old-homarr-import-choose-imported-data.png)
-
-Once you have selected everything you can click on `Confirm import and continue` which will open the encryption key input dialog where you can input the secret key you got during the export.
-
-![Onboarding import key input](./img/old-homarr-import-decryption-token.png)
-
-After that you can continue the onboarding and you should see all your boards and data in the new installation.
-
-See [After the installation](https://homarr.dev/docs/getting-started/after-the-installation) for more information.
+:::
 
 ## Remove the old installation
 
 After you are happy with the new installation and everything is working as expected you can remove the old installation.
 Please make sure to backup the data before you remove the old installation.
-Also once the port 7575 is free again you can change the port mapping of the new installation to `7575:7575` if you want to.
+Also once the port 7575 is free again you can change the port mapping of the new installation to `7575:7575` if you want to.

apps/docs/components.json

@@ -0,0 +1,24 @@
+{
+  "$schema": "https://ui.shadcn.com/schema.json",
+  "style": "base-nova",
+  "rsc": false,
+  "tsx": true,
+  "tailwind": {
+    "config": "",
+    "css": "src/css/custom.css",
+    "baseColor": "mist",
+    "cssVariables": true,
+    "prefix": ""
+  },
+  "aliases": {
+    "components": "@/components",
+    "utils": "@/lib/utils",
+    "ui": "@/components/ui",
+    "lib": "@/lib",
+    "hooks": "@/hooks"
+  },
+  "iconLibrary": "tabler",
+  "rtl": false,
+  "menuColor": "default",
+  "menuAccent": "subtle"
+}

apps/docs/docs/advanced/_category_.json

@@ -1,7 +1,7 @@
 {
   "label": "Advanced",
   "collapsed": true,
-  "position": 4,
+  "position": 5,
   "link": {
     "type": "generated-index",
     "title": "Advanced Concepts or features"

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

@@ -0,0 +1,175 @@
+# Developer Docker CLI
+
+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 (`gh auth login`) is only needed for pull-request features.
+
+## 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 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 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.
+
+### 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
+homarr dash
+# or
+pnpm dev:cli -- dash
+```
+
+The instance dashboard displays all running and stopped Homarr containers, published ports, health states, and resource volumes.
+
+| 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
+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/
+```
+
+- `--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`).
+
+### Build & Rebuild
+
+```bash
+# 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
+```
+
+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

@@ -8,62 +8,77 @@ tags:
 sidebar_position: 1
 ---
 
-## Setting up your development environment
-
-This guide will help you set up your development environment to start contributing to homarr.
+## Set up your development environment
 
 ### Prerequisites
 
-- **Node.js (lts)**: You can download it from the [official website](https://nodejs.org/).
-- **pnpm (latest)**: You can install it by running `npm install -g pnpm`.
+- **Node.js 24.18 or newer**: You can download it from the [official website](https://nodejs.org/).
+- **Corepack**: Run `corepack enable` so the repository selects its pinned pnpm 11 version.
 - **Git**: You can download it from the [official website](https://git-scm.com/).
-- **Docker or Docker Desktop**: You can download it from the [official website](https://www.docker.com/).
-- **A GitHub account**: You can create one on the [official website](https://github.com/).
+- **Docker or Docker Desktop**: Required for the Redis service and the developer Docker CLI.
+- **Go 1.25+**: Required only for the developer Docker CLI. You can download it from the [official website](https://go.dev/).
+- **GitHub CLI**: Required only for pull-request image features. Install it from the [official website](https://cli.github.com/), then authenticate with `gh auth login`.
 
-### Setting up the project
+The versions in the root `package.json` are the supported baseline. Let Corepack select the repository version instead
+of installing an unrelated global pnpm:
 
-1. Fork the repository by clicking on the "Fork" button on the top right corner of the repository page.
+```sh
+corepack enable
+corepack install
+pnpm install --frozen-lockfile
+```
 
-![Fork button](./img/fork.png)
+### Run the Homarr application
 
-2. Clone the repository to your local machine with `git clone`. You can find the url to use by clicking on the "Code" button on the top right corner of your forks repository page.
+1. Copy `.env.example` to `.env`.
+2. Set `DB_URL` to an absolute writable SQLite file path.
+3. Keep Redis and the optional local databases running in one terminal.
+4. Apply migrations and start Next.js in another terminal.
 
-![Clone button](./img/clone.png)
+```sh
+cp .env.example .env
+```
 
-3. Change directory to the project folder with `cd homarr`.
+Terminal 1:
 
-4. Install the dependencies with `pnpm install`.
+```sh
+pnpm docker:dev
+```
 
-5. Start redis by running `pnpm run docker:dev`. This will run a docker-compose file with a redis service.
+Terminal 2:
 
-6. Copy the `.env.example` file to `.env` and replace `DB_URL` with the full path you want to use for the sqlite database file. For example `DB_URL='C:\\Dev\\homarr\\packages\\db\\db.sqlite'`
+```sh
+pnpm db:migration:sqlite:run
+pnpm dev
+```
 
-7. Run the migrations to create the sqlite db file with `pnpm run db:migration:sqlite:run`.
+The infrastructure command remains in the foreground. Open `http://127.0.0.1:3000`; the first user created through
+Homarr becomes the instance administrator.
+Use `pnpm docker:dev:up` instead when you only need Redis in the background. Running the migration also seeds the
+default data; use `pnpm db:seed` to seed it explicitly later.
 
-8. Start the development server with `pnpm dev` and wait for a message that says `✓ Ready in 10.7s`
+Workshop contributors can set up PocketBase and Docusaurus with the dedicated
+[Workshop development guide](./workshop).
 
-9. Open your browser and navigate to [http://localhost:3000](http://localhost:3000). (Loading the page might take up to 2 minutes the first time)
+### Useful commands
 
-### Useful npm scripts
-
-#### During development
-
-- `pnpm dev`: Start the development server.
-- `pnpm cli`: Run cli commands.
-- `pnpm db:migration:sqlite:run`: Run the migrations to create or update the sqlite db file.
-- `pnpm db:migration:sqlite:generate`: Generate a new migration file for the sqlite db. Also works with `mysql`.
-- `pnpm db:studio`: Open a visual studio for the database.
-- `pnpm package:new`: Create a new package in the monorepo.
-
-#### Checking code quality
-
-- `pnpm lint`: Run the linter to check for code quality issues.
-- `pnpm format:fix`: Run the formatter to fix code style issues.
-- `pnpm test`: Run the tests. You can also use `pnpm test:ui` to get a UI for the tests.
-- `pnpm typecheck`: Run the typescript type checker.
-
-#### Building the project
-
-- `pnpm build`: Build the project for production.
-- `docker build -t homarr .`: Build a docker image for the project.
-- `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:latest`: Run the created docker image.
+- `pnpm dev` — Next.js on port 3000.
+- `pnpm dev:benchmark` — authenticated-board benchmark; readiness-only `--smoke` runs are not performance claims.
+- `pnpm dev:cli -- dev` — browse and run local images and remote pull-request images.
+- `pnpm dev:cli -- build <name>` — build the current checkout as `homarr:<name>`.
+- `pnpm dev:cli -- build --pr <number>` — build a pull request from a temporary checkout.
+- `pnpm dev:cli -- rebuild <name>` — rebuild an image from its recorded checkout or pull request.
+- `pnpm dev:cli:install` — optionally install the developer CLI as a `homarr` binary.
+- `pnpm dev:docs` — Docusaurus only on port 3003.
+- `pnpm docker:dev:up` — Redis development service in the background.
+- `pnpm cli` — Homarr operations CLI.
+- `pnpm db:migration:sqlite:run` — create or update a SQLite database.
+- `pnpm db:seed` — seed the default database data explicitly.
+- `pnpm db:studio` — inspect the database.
+- `pnpm format` / `pnpm format:fix` — check or apply oxfmt.
+- `pnpm lint` / `pnpm lint:fix` — check or apply oxlint.
+- `pnpm typecheck` — typecheck all workspaces.
+- `pnpm test` — unit and contract suites.
+- `pnpm build` — production monorepo build.
+- `docker build -t homarr .` — build a production Docker image.
+- `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:<name>` — run it.

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

@@ -25,13 +25,40 @@ This is especially useful for [docker secrets](https://docs.docker.com/engine/sw
 Using the `PUID` and `PGID` will require you to set the correct permissions on the mounted volumes and if used the docker socket. See more in the [Running as a different user](/docs/advanced/running-as-different-user) documentation.
 :::
 
-| Environment Variable     | Description                                                                                                                                                                        | Possible values                     | Default |
-| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------- |
-| `PUID`                   | User ID to run the container as                                                                                                                                                    | Any valid user ID                   | `0`     |
-| `PGID`                   | Group ID to run the container as                                                                                                                                                   | Any valid group ID                  | `0`     |
-| `LOG_LEVEL`              | Log level to use                                                                                                                                                                   | `debug` / `info` / `warn` / `error` | `info`  |
-| `NO_EXTERNAL_CONNECTION` | Disables some requests that need internet connection                                                                                                                               | `true` or `false`                   | `false` |
-| `ENABLE_DNS_CACHING`     | Enables dns caching. Enabled by default, but if you experience issues with IPv6 or static IPs, see [#4006](https://github.com/homarr-labs/homarr/issues/4006) or disable this flag | `true` or `false`                   | `true`  |
+| Environment Variable     | Description                                                                                                                                                                                                                            | Possible values                     | Default                       |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ----------------------------- |
+| `PUID`                   | User ID to run the container as                                                                                                                                                                                                        | Any valid user ID                   | `0`                           |
+| `PGID`                   | Group ID to run the container as                                                                                                                                                                                                       | Any valid group ID                  | `0`                           |
+| `LOG_LEVEL`              | Log level to use                                                                                                                                                                                                                       | `debug` / `info` / `warn` / `error` | `info`                        |
+| `NO_EXTERNAL_CONNECTION` | Disables Homarr's internet-backed requests, including update checks, weather, and RSS feeds                                                                                                                                            | `true` or `false`                   | `false`                       |
+| `ENABLE_DNS_CACHING`     | Enables dns caching. Enabled by default, but if you experience issues with IPv6 or static IPs, see [#4006](https://github.com/homarr-labs/homarr/issues/4006) or disable this flag                                                     | `true` or `false`                   | `true`                        |
+| `HOMARR_DISABLE_IPV6`    | Disables the IPv6 listener of the internal nginx proxy, even when the host supports IPv6. IPv6 is normally disabled automatically when the host has no IPv6 configured. See [#4596](https://github.com/homarr-labs/homarr/issues/4596) | `true` or `false`                   | `false`                       |
+| `HOMARR_WEBSITE_URL`     | Main Homarr documentation/site base used by runtime links. Must be an absolute HTTP(S) URL.                                                                                                                                            | HTTP(S) URL                         | `https://homarr.dev`          |
+| `WORKSHOP_API_URL`       | PocketBase API used by Homarr and standalone documentation.                                                                                                                                                                            | HTTP(S) URL                         | `HOMARR_WEBSITE_URL`          |
+| `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](/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
 
@@ -51,11 +78,12 @@ A random secret can be generated by using the following command: `openssl rand -
 
 ## Docker
 
-| Environment Variable  | Description                                     | Possible values                                                      | Default |
-| --------------------- | ----------------------------------------------- | -------------------------------------------------------------------- | ------- |
-| `DOCKER_HOSTNAMES`    | Comma seperated list of hostnames to connect to | For example `localhost,docker.example.com`                           | -       |
-| `DOCKER_PORTS`        | Comma seperated list of ports to connect to     | For example `2375,2376`                                              | -       |
-| `DOCKER_SOCKET_PATHS` | Comma seperated list of paths to sockets        | For example `/var/run/docker.sock,/run/user/1000/podman/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
 
@@ -105,6 +133,9 @@ External redis is currently not supported with Proxmox Community Scripts
 The advanced deployments environment variables should only be used if you know what you are doing.
 :::
 
-| Environment Variable     | Description                                        |
-| ------------------------ | -------------------------------------------------- |
-| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts |
+| Environment Variable     | Description                                         |
+| ------------------------ | --------------------------------------------------- |
+| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts. |
+
+All public URL variables reject non-HTTP protocols, embedded credentials, query strings, and fragments, and normalize
+trailing slashes when Homarr or Docusaurus starts.

apps/docs/docs/advanced/icons/index.mdx

@@ -12,7 +12,7 @@ tags:
 
 Icons in Homarr are automatically requested from multiple sources:
 
-- [Dashboard Icons](https://dashboardicons.com/) - Our recommended source with over 1888+ curated, high-quality icons
+- [Dashboard Icons](https://dashboardicons.com/) - Our recommended source with more than 1,888 curated, high-quality icons
 - [selfh.st icons](https://github.com/selfhst/icons)
 - [Simple icons](https://github.com/simple-icons/simple-icons)
 - [Tabler icons](https://tabler-icons.io/)
@@ -21,7 +21,7 @@ Icons in Homarr are automatically requested from multiple sources:
 - **Local icons**: automatically fetched from the [medias feature](/docs/management/media/)
 
 Using these icon sources, Homarr provides a total collection of over 11,000 icons at your fingertips.
-The icon picker is a fast searcher that helps you to find your desired icon simply by entering a search term.
+The image picker searches this collection after a short typing delay. When a name is available, such as an app or search engine name, the picker uses it as the initial search. Results show your locally uploaded images first, followed by SVG icons and then other image formats.
 
 ### Finding Missing Icons
 
@@ -31,7 +31,13 @@ If you can't find the icon you're looking for in Homarr's built-in picker, we st
 
 Icons that are high quality and printable ([SVG](https://wikipedia.org/wiki/Scalable_Vector_Graphics)) are marked with a red badge "SVG" at the top right.
 
+You can clear the selected image with the clear button or the usual keyboard shortcut for deleting a line (Command+Backspace on macOS or Control+Backspace on other platforms). Clearing the field does not restore the previous image.
+
 ### Using external icons
 
 If you don't find the icon you're looking for on Dashboard Icons or wish to use a different source, you can simply enter a URL that points to an icon.
-It is important that the URL directly points to the file without any advertisements or elements around it.
+Direct HTTP(S) image URLs are used as entered instead of being searched in the built-in repositories. The picker previews the image and shows whether it loaded successfully. It is important that the URL directly points to the file without any advertisements or elements around it.
+
+### Uploading a local image
+
+Users with media upload permission can select **Upload image** next to the field. After the upload finishes, the new local image is selected immediately and is available at the top of future searches.

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

@@ -6,11 +6,66 @@ 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    |
+| 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. 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
+
+`MOD` + `E` enters edit mode. Homarr keeps the current board visible while the editor prepares; movement and resizing become available when it is ready.
+
+When a tile is focused in edit mode:
+
+| Shortcut             | Description                                                                 |
+| -------------------- | --------------------------------------------------------------------------- |
+| `Enter` or `Space`   | Starts or stops keyboard editing                                            |
+| Arrow keys           | Moves the focused tile within its current canvas, rail, or Container        |
+| `Shift` + Arrow keys | Resizes from the tile's lower-right corner: Left/Up shrink; Right/Down grow |
+| `Esc`                | Stops keyboard editing without undoing its changes                          |
+
+Keyboard moves and resizes apply immediately. To move an item between a canvas, rail, or Container, drag it there or use **Move / resize item** for precise numeric placement.
+Commands at a grid boundary or at the tile's minimum size are ignored and announced instead of moving or shrinking the tile.
+
+On touch screens, press and hold a tile before moving it; a quick tap does not start a drag. Resize handles accept direct touch input. During a pointer or touch move or resize, `Esc` cancels the interaction and restores the layout from before it started.
+
+## Board editing
+
+When a tile is focused in edit mode:
+
+| Shortcut             | Description                                                                 |
+| -------------------- | --------------------------------------------------------------------------- |
+| `Enter` or `Space`   | Starts or stops keyboard editing                                            |
+| Arrow keys           | Moves the focused tile within its current canvas, rail, or Container        |
+| `Shift` + Arrow keys | Resizes from the tile's lower-right corner: Left/Up shrink; Right/Down grow |
+| `Esc`                | Stops keyboard editing without undoing its changes                          |
+
+Keyboard moves and resizes apply immediately. To move an item between a canvas, rail, or Container, drag it there or use **Move / resize item** for precise numeric placement.
+Commands at a grid boundary or at the tile's minimum size are ignored and announced instead of moving or shrinking the tile.
 
 :::tip
 

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

@@ -49,7 +49,6 @@ services:
       traefik.http.routers.homarr.rule: Host(`your.internal.dns.address.here.com`)
       traefik.http.routers.homarr.entrypoints: websecure
       traefik.http.routers.homarr-secure.app: homarr
-      traefik.http.apps.homarr.loadbalancer.server.port: 7575
 
 networks:
   proxy:
@@ -144,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/single-sign-on/index.mdx

@@ -128,6 +128,8 @@ Homarr supports multiple authentication options, from internal userbase (credent
 
     If you'd rather manage group memberships for OIDC users locally (instead of via the IdP), set `AUTH_OIDC_GROUPS_LOCAL_MANAGEMENT=true`. While enabled, Homarr stops syncing OIDC users' group memberships from the groups claim, and admins can add/remove OIDC users on a group's members page. If you turn this back to `false`, the next login of each user resumes the regular sync and reconciles their groups with the IdP's claim again, which may remove memberships that were added manually while local management was enabled.
 
+    To let an existing credentials user also sign in with OIDC, set `AUTH_OIDC_ENABLE_DANGEROUS_CREDENTIALS_LINKING=true`. On the first OIDC sign-in, Homarr links a credentials user with the same email address instead of creating a second user. The user keeps their password login, local username and profile, groups, permissions, boards, settings, and API keys. OIDC profile and group claims do not overwrite the credentials-owned data. Homarr requires the OIDC profile to contain `email_verified: true` while this option is enabled. Only enable this when your OIDC provider verifies email addresses, because a matching email could otherwise be used to take over an existing account.
+
     <details>
       <summary>
         Example Setup
@@ -205,6 +207,7 @@ Homarr supports multiple authentication options, from internal userbase (credent
     | ``AUTH_OIDC_NAME_ATTRIBUTE_OVERWRITE`` | Overwrite name attribute. By default it will use preferred_username if it does not contain a `@` and otherwise name. | ---          |
     | ``AUTH_OIDC_FORCE_USERINFO`` | Force userinfo endpoint to be used for user information.    | false         |
     | ``AUTH_OIDC_ENABLE_DANGEROUS_ACCOUNT_LINKING`` | Enable account linking for OIDC provider. This will link the OIDC accounts by email. Be sure that you have verified emails to prevent stealing accounts. | false |
+    | ``AUTH_OIDC_ENABLE_DANGEROUS_CREDENTIALS_LINKING`` | Link an OIDC identity to an existing credentials user with the same email. The credentials login and existing user data are preserved. Requires the OIDC profile to contain `email_verified: true`. | false |
     | ``AUTH_OIDC_TOKEN_ENDPOINT_AUTH_METHOD`` | Override method for the token endpoint authentication. Supported values are `client_secret_basic`, `client_secret_post`, `client_secret_jwt` and `none`. | client_secret_basic |
 
     ### Permission System

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 down a bit and click on custom CSS.
-Here you can enter your CSS code, which will be applied on the respective board page.
-
-![](./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/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "Community",
-  "position": 5,
+  "position": 6,
   "collapsed": true,
   "link": {
     "type": "generated-index"

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,96 +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. Administrators can create [Custom Widgets](/docs/management/custom-widgets) that read an HTTP API and render the response with a built-in display type. These display types require no programming.
+Use the browser developer console only for client-side failures. Review logs before sharing them because URLs and other
+deployment details may be present.
 
-Custom JSX is available when you need a more specific layout or an interactive control. It uses a restricted declarative JSX interpreter with a classified Mantine component set. Network operations are declared as named, same-origin requests and are checked against board permissions on the server. It does not execute arbitrary JavaScript or expose browser `fetch`.
+### Why can Homarr not reach a service behind Gluetun?
 
-You should be comfortable reading JSON and JSX to author complex templates. The management workbench includes examples, diagnostics, a component reference, API response inspection, and a prompt you can copy into an AI assistant. Always review imported templates and request capabilities before saving them.
+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.
 
-### Is it secure to expose Homarr to the web?
+### Where do I report a bug or request a feature?
 
-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)
+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).
 
-### How do I open the console / log?
+### Can Homarr be used commercially?
 
-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,384 +6,76 @@ tags:
   - Configuration
 ---
 
-import imageStartFromScratchStepServerSettings from "./img/onboarding-from-scratch-step-server-settings.png";
-import imageStartFromScratchStepAdminUser from "./img/onboarding-from-scratch-step-admin-user.png";
-import imageStartFromScratchStepExternalAdminGroup from "./img/onboarding-from-scratch-step-external-admin-group.png";
-import imageStartFromScratchStepFinish from "./img/onboarding-from-scratch-step-finish.png";
-import manageBoardHeaderEditMode from "./img/manage-board-header-edit-mode.png";
-import manageBoardHeaderAddItem from "./img/manage-board-header-add-item-menu.png";
-import manageBoardHeaderChooseItem from "./img/manage-board-header-choose-item.png";
-import manageBoardNoApp from "./img/manage-board-no-app.png";
-import manageExportOldHomarr from "./img/old-homarr-export-data.png";
-import manageImportOldHomarrDropzone from "./img/old-homarr-import-dropzone.png";
-import manageImportOldHomarrChooseData from "./img/old-homarr-import-choose-imported-data.png";
-import manageImportDecryptionToken from "./img/old-homarr-import-decryption-token.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)
 
-The onboard will show the first time you start Homarr.
-This process will help you with your first steps and adding some initial data, such as the administrator account.
+See [Boards](/docs/management/boards) for responsive layouts, access control, appearance, and home-board settings.
 
-:::note
+### Apps
 
-If you see this screen repeatitly after you restarted 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)
 
-You can either import a previous dashboard using the ZIP archive or start from scratch:
+See [Apps](/docs/management/apps) or [Icons](/docs/advanced/icons).
 
-![Screenshot of Step 1 onboarding](./img/onboarding-step-1.png)
+### Integrations
 
-You may refresh anytime and continue from a different device - the onboarding is saved immediately on the server for your convenience.
+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.
 
-### Starting from scratch
+![Integration catalog with compatible widgets](./img/after-installation-integrations.png)
 
-Depending on your auth provider configuration you will either first see the admin user creation form or the external group creation form.
-If the credentials provider was selected, you'll be prompted to create an admin user for Homarr.
-This user cannot be deleted and has full control over Homarr and all of its boards.
-You must choose a username and password (both can later be changed).
-We enforce strict password requirements when you enter your password to protect your instance if you accidentally
-expose it to the internet.
+See [Managing integrations](/docs/management/integrations) and the
+[integration catalog](/docs/category/integrations).
 
-<img src={imageStartFromScratchStepAdminUser} alt={"Screenshot form to create admin user"} width={300} />
+### Widgets
 
-If you selected external providers (such as LDAP or OIDC), you'll be prompted to create an admin group.
-This group will be used to synchronize users from your provider to Homarr.
-When a user logs in through the provider, any of their groups that match groups in Homarr will be assigned to the user.
-The name of the group must match exactly the name of the group in the provider.
+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.
 
-<img
-  src={imageStartFromScratchStepExternalAdminGroup}
-  alt={"Screenshot form to create external admin group"}
-  width={300}
-/>
+![Board in edit mode with the add-content menu](./img/after-installation-widgets.png)
 
-Next, you can configure some basic settings for Homarr. We recommend to leave all settings at default for most users.
-Here you can also disable analytics. Please note that our analytics are completly anonymous and is fully compliant with GDPR and PECR.
+See the [widget catalog](/docs/category/widgets).
 
-<img
-  src={imageStartFromScratchStepServerSettings}
-  alt={"Screenshot of analytics and indexing settings in the onboarding"}
-  width={300}
-/>
+### Containers and rails
 
-### Setting up integrations
+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.
 
-After configuring server settings, the onboarding guides you through setting up your integrations.
+![Board layout settings with fixed sidebars](./img/after-installation-containers-rails.png)
 
-#### Docker service discovery
+See [Boards](/docs/management/boards#containers-and-rails).
 
-If Docker is available (socket mounted), Homarr automatically detects running containers and matches them to known integration types.
-Matching integrations are pre-selected in the integration list, saving you from manually picking each one.
+### Users, groups, and permissions
 
-#### URL templating
+Users inherit permissions and default boards from their groups. Resource-specific access can further restrict boards
+and integrations.
 
-You can define a base URL template to auto-fill integration URLs in bulk.
-Two modes are supported:
+![Group permission settings](./img/after-installation-users-permissions.png)
 
-- **Subdomain mode** - e.g. `{app}.example.com` where `{app}` is replaced with the integration name
-- **Port mode** - e.g. `192.168.1.1:{port}` where `{port}` is replaced with the integration's default port
+See [Users and groups](/docs/management/users) and [single sign-on](/docs/advanced/single-sign-on).
 
-#### API key helper links
+## Explore further
 
-For integrations that require API keys (such as Sonarr, Radarr, SABnzbd, or Seerr), a helper link opens the relevant settings page in the target application so you can quickly copy your key.
+- [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)
 
-#### Creating apps from Docker containers
-
-You can optionally auto-create bookmark apps for all discovered Docker containers, making them immediately available on your board.
-
-:::note
-
-Release providers and Search.ch are configured directly in their widgets instead of the integrations page.
-
-:::
-
-After this step, you finished the onboarding.
-The onboarding can no longer be started again.
-From here you can click on one of the provided links to continue your journey.
-We recommend you to continue with the section [creating your first board on this page](#creating-your-first-board).
-
-<img src={imageStartFromScratchStepFinish} alt={"Screenshot of the finish onboarding process with links"} width={300} />
-
-### Importing a ZIP from version before 1.0.0
-
-This is recommended when you used Homarr before and want to re-import your data.
-It is important that you first migrate correctly using [the list of breaking changes for 1.0](/blog/2024/09/23/version-1.0).
-
-<img src={manageExportOldHomarr} alt="Export from old Homarr" style={{ maxWidth: 500 }} />
-
-**How to export and import data**
-
-1. Navigate to your old Homarr, open your management pages, open the tools submenu and open `Migrate to 1.0`.
-2. Check the contents that you want to export. We recommend you to export all data.
-3. Click on the export data button
-4. Save the ZIP file, that is being downloaded, on your device. If you selected "integrations" or "users", you also get an encryption / decryption key.
-   Copy it and do not loose it!
-5. Go to your new >1.0.0 Homarr instance and start the onboarding. Choose `Import from Homarr before 1.0`
-6. Drag and drop your previously downloaded ZIP archive into the file upload: <br/><img src={manageImportOldHomarrDropzone} style={{ maxWidth: 500 }} />
-7. Next, choose the data that you want to import and how to import it. Since screen sizes were removed in 1.0, we create a new board for every screen size by default. We recommend you to only keep the best layout and adjust it later in 1.0.0 - but you can also import all of them and pick later.<br/><img src={manageImportOldHomarrChooseData} style={{ maxWidth: 500 }} />
-8. If you previously exported integrations or users, you will be asked to decrypt the data safely using your obtained encryption token. Paste into the modal and confirm your action.<br/><img src={manageImportDecryptionToken} style={{ maxWidth: 500 }} />
-9. Next, you can [follow the same setup as when starting from scratch](#starting-from-scratch). After you completed the onboarding, all of your data will be migrated and available.
-
-## Creating your first board
-
-In Homarr, you organize your apps and widgets on boards.
-Boards can be organized using the interactive drag and drop.
-Let's create your first board by navigating here: `Manage` > `Boards` > `New board`:
-![](./img/manage-create-board-button.png)
-
-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)).
-
-![](./img/manage-create-board-modal.png)
-
-Congratulations - you've just created your first board. You can see boards, that you have access to, on this page:
-
-![](./img/manage-view-board.png)
-
-## Add your first app to Homarr
-
-To add links to your dashboard, you must first add them as an "app".
-Navigate to this page to add an app:
-
-![](./img/manage-navigate-apps.png)
-
-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:
-
-![](./img/manage-view-board.png)
-
-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 mode**: Clicking this button will toggle the 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, ...).
-- **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:
-
-<img src={manageBoardHeaderEditMode} alt={"Screenshot of buttons in the edit mode"} width={200} />
-
-- **Add item**: Click this button to add new elements to your page.
-- **Exit edit mode**: Click this btuton to save your changes and exit edit mode.
-
-To continue, click the option "New Item":
-
-<img src={manageBoardHeaderAddItem} alt={"Screenshot of the add item menu"} width={200} />
-
-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.
-
-<img src={manageBoardHeaderChooseItem} alt={"Screenshot of choosing the app item in the modal"} width={300} />
-
-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.
-
-![](./img/manage-board-edit-app.gif)
-
-In the modal you can edit the app that you want to display:
-
-![](./img/manage-board-choose-app.png)
-
-As soon as you save your changes, the tile on the board will refresh and display your app.
-Using the small bidirectional arrow at the bottom right you can resize the element.
-Start pressing with your mouse button down, move your mouse to resize and release your finger as soon your you're happy with the size.
-
-![](./img/resize-item.gif)
-
-To move your item to a different position on the board, simply hold the mouse button anywhere on the item and move with the mouse to the desired position.
-As soon as you release your finger, the item will snap in place in the grid.
-
-![](./img/move-item.gif)
-
-:::note
-
-You cannot move items freely on the vertical axis.
-We always align all items to the top of the page to simply organization.
-To move items to the bottom, you must add more items or resize items.
-
-:::
-
-:::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.
-
-:::
-
-Users on touch or mobile devices may not be able to drag and drop or move items.
-They can use the "Move / resize item" option in the edit menu of items instead:
-
-![](./img/manage-board-move-resize-item-menu.png)
-
-Be sure to save your changes by exiting edit mode!
-
-![](./img/exit-edit-mode.png)
-
-## 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:
-
-![](./img/manage-board-header-add-item-menu.png)
-
-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, don't forget to save your changes using the exit edit mode button:
-
-![](./img/exit-edit-mode.png)
-
-## Grouping your items
-
-As the last step, let's organize your freshly created items using two different options.
-You can choose either or both of them on your boards.
-
-### Using dynamic sections
-
-Dynamic sections are a simple, resizable visual group to group items.
-
-![](./img/create-dynamic-section.png)
-
-After adding a dynamic section, you can simply drag and drop items into the section:
-
-![](./img/dynamic-section.gif)
-
-### Using categories
-
-Categories are more advanced and complicated than dynamic sections.
-To create a category, open the add item modal and choose "new category":
-
-![](./img/add-category.png)
-
-Every category must have a name. After you click "Add category", you will get a new item on your board:
-
-![](./img/category.gif)
-
-You can drag and drop items in to this category in the edit mode.
-Categories will have a big space before and after them in the edit mode to
-enable you to drag and drop items outside the category.
-You can also collapse or open categories in edit mode to facilitate your editing process.
-
-:::note
-
-A current limitation of categories is, that they will always have a width of 100%.
-You cannot reduce their horizontal width.
-
-:::
-
-## 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

@@ -1,13 +1,20 @@
 # Glossary
 
-In the glossary, you'll learn the different components and their names of Homarr.
+This glossary explains Homarr's main components and the terms used for them.
 
-| Term            | Definition                                                                                                     |
-| --------------- | -------------------------------------------------------------------------------------------------------------- |
-| Apps            | An piece of software that you or a third party hosts (eg. Google)                                              |
-| Integration     | A connection to a service outside of Homarr                                                                    |
-| Dynamic section | Resizeable area where items on your board can be placed and grouped                                            |
-| Widget          | A tile that uses your integrations to display data or enables you to interact with with them                   |
-| Edit mode       | Temporary state that you can enter where you can drag and drop, edit or customize your board                   |
-| Board           | Customizable page which can be edited using the edit mode. This is where apps, sections and widgets are placed |
-| Tasks           | Workloads that are performed in the background - even if there is no user 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.22.0](https://img.shields.io/badge/Version-8.22.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.70.0](https://img.shields.io/badge/AppVersion-v1.70.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
 
@@ -263,7 +263,7 @@ httproute:
             value: /
       backendRefs:
         - name: homarr
-          port: 8080
+          port: 7575
 ```
 
 </details>
@@ -427,17 +427,17 @@ All available values are listed on the [artifacthub](https://artifacthub.io/pack
 | envSecrets.dbEncryption.key                        | string | `"db-encryption-key"`                                                                                                                                                                                                                            | Secret key for SECRET_ENCRYPTION_KEY can be generated with `openssl rand -hex 32`                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 | fullnameOverride                                   | string | `""`                                                                                                                                                                                                                                             | Overrides chart's fullname                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
 | hostAliases                                        | list   | `[]`                                                                                                                                                                                                                                             | Add static entries to /etc/hosts in the Pod. This is useful in the following cases: - You are running in a dual-stack cluster (IPv4 + IPv6) and want to force usage of IPv4 for specific hostnames - Your application is having DNS resolution issues or IPv6 preference issues - You need to override or simulate DNS entries without changing global DNS - You are running in an air-gapped or isolated environment without external DNS Example: hostAliases: - ip: "192.168.1.10" hostnames: - "example.com" - "example.internal"                    |
-| httproute                                          | object | `{"enabled":false,"hostnames":["chart-example.local"],"parentRefs":[{"name":"my-gateway","namespace":"default"}],"rules":[{"backendRefs":[{"name":"homarr","port":8080}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]}` | Gateway API HTTPRoute configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| httproute                                          | object | `{"enabled":false,"hostnames":["chart-example.local"],"parentRefs":[{"name":"my-gateway","namespace":"default"}],"rules":[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]}` | Gateway API HTTPRoute configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | httproute.enabled                                  | bool   | `false`                                                                                                                                                                                                                                          | Enable HTTPRoute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | httproute.hostnames                                | list   | `["chart-example.local"]`                                                                                                                                                                                                                        | Hostnames this route matches (similar to ingress.hosts.host)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
 | httproute.parentRefs                               | list   | `[{"name":"my-gateway","namespace":"default"}]`                                                                                                                                                                                                  | References to the parent Gateway(s) this route attaches to. Each item must include at least a `name`, and optionally a `namespace`.                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| httproute.rules                                    | list   | `[{"backendRefs":[{"name":"homarr","port":8080}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]`                                                                                                                          | List of routing rules. Each rule can include: - matches: path/header/query matching - filters: optional transformations (redirects, header modifications, etc.) - backendRefs: one or more Kubernetes Services to forward traffic to                                                                                                                                                                                                                                                                                                                     |
+| httproute.rules                                    | list   | `[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]`                                                                                                                          | List of routing rules. Each rule can include: - matches: path/header/query matching - filters: optional transformations (redirects, header modifications, etc.) - backendRefs: one or more Kubernetes Services to forward traffic to                                                                                                                                                                                                                                                                                                                     |
 | httproute.rules[0].filters                         | list   | `[]`                                                                                                                                                                                                                                             | Optional filters for this rule (default: empty)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | httproute.rules[0].matches[0].path.type            | string | `"PathPrefix"`                                                                                                                                                                                                                                   | Path match type. One of: Exact, PathPrefix, RegularExpression                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | 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.70.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-labels/index.mdx

@@ -0,0 +1,95 @@
+---
+title: "Docker labels"
+description: "Discover apps, integrations, and widgets from container labels during Homarr onboarding."
+---
+
+# Docker label discovery
+
+During onboarding, Homarr scans running containers on every reachable
+[Docker-compatible host](/docs/integrations/docker). Labels let you provide exact app metadata instead of relying on
+image-name matching. You can review and deselect every result before Homarr creates anything.
+
+A container with valid Homarr labels takes priority over image-based discovery. Containers without valid labels can
+still be suggested from their image and published ports.
+
+## Homarr labels
+
+`homarr.name` and `homarr.href` are required for label discovery. All other labels are optional.
+
+| Label                | Purpose                                                                    |
+| -------------------- | -------------------------------------------------------------------------- |
+| `homarr.name`        | App or integration display name                                            |
+| `homarr.href`        | Address opened by the app and used as the suggested integration address    |
+| `homarr.group`       | Container section that receives the selected app and compatible widget     |
+| `homarr.icon`        | App icon URL                                                               |
+| `homarr.description` | App description                                                            |
+| `homarr.ping`        | Address used for app status checks                                         |
+| `homarr.id`          | Stable source identifier; defaults to the Docker container ID              |
+| `homarr.board`       | Intended board name; see [Board targeting](#board-targeting)               |
+| `homarr.integration` | Homarr integration kind, for example `sonarr`                              |
+| `homarr.widget`      | Homarr widget kind to add when it supports the selected integration        |
+| `homarr.hide`        | Excludes the container when this label is present, regardless of its value |
+
+Unknown integration and widget kinds are ignored. Do not put API keys, passwords, or other secrets in labels. Enter
+credentials in onboarding, where Homarr stores them using its normal encrypted integration-secret flow.
+
+## Compose example
+
+```yaml
+services:
+  sonarr:
+    image: lscr.io/linuxserver/sonarr:latest
+    labels:
+      homarr.name: "Sonarr"
+      homarr.href: "http://server.local:8989"
+      homarr.group: "Media"
+      homarr.icon: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/sonarr.svg"
+      homarr.description: "TV library"
+      homarr.ping: "http://server.local:8989"
+      homarr.integration: "sonarr"
+      homarr.widget: "calendar"
+```
+
+Use an address that is reachable where it is needed. A Docker service name can work for server-side integration
+requests, while an app link opened in a browser usually needs a LAN hostname, IP address, or reverse-proxy address.
+Onboarding accepts these self-hosted address formats directly and only requires the field to be non-empty.
+
+## Homepage label fallback
+
+When `homarr.name` is absent, onboarding also understands these Homepage labels:
+
+- `homepage.name`
+- `homepage.href`
+- `homepage.group`
+- `homepage.icon`
+- `homepage.description`
+
+`homepage.name` and `homepage.href` are required for the fallback. Homarr does not combine partial Homarr metadata with
+Homepage metadata: once `homarr.name` is present, use `homarr.*` labels for the remaining fields too.
+
+## What onboarding creates
+
+In **Connect**, label-discovered apps and integrations appear before image-based suggestions. You can import multiple
+services in one pass and edit every suggested address. For image-matched apps, Homarr uses the detected service type
+when building host, subdomain, or reverse-proxy path suggestions.
+
+When setup completes, Homarr rechecks the selected container sources and then:
+
+- creates an app with its name, address, icon, description, and ping address;
+- creates the requested integration and links its app after you provide required credentials;
+- places grouped apps in a board container named by `homarr.group`;
+- places ungrouped apps in the main board area;
+- adds `homarr.widget` only when the widget kind is valid and compatible with the selected integration;
+- keeps image-based discovery available for unlabeled containers.
+
+If a selected container disappears, targets another board, or requests an incompatible widget, setup finishes with a
+warning instead of creating an invalid board item.
+
+## Board targeting
+
+On a fresh installation with one seeded `dashboard` board, one unique selected `homarr.board` value can name that first
+board. Otherwise, the label must match the board selected in onboarding. Services labeled for another board are skipped
+and reported in the completion warning.
+
+Onboarding configures one board at a time. Run normal board management after setup if you want to distribute services
+across several boards.

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

@@ -1,168 +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`
-
-### Managing your Docker containers within Homarr
-
-Homarr allows you to interact with Docker containers running on your system.
-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)
-
-### Configuration
-
-Currently Homarr supports one label for configuration of the containers:
-
-- **homarr.hide:** If set to any value, the container will be hidden from the Docker Containers widget and tools page.
-
-### 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):
+`/var/run/docker.sock` is the default. For other in-container paths, set a comma-separated list:
 
 ```yaml
-networks:
-  socket-proxy:
-    name: socket-proxy # <--- change this to the name of the network as set up by the socket proxy
-    external: true
+environment:
+  DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
 ```
 
-2. Add the network to the homarr service in the compose file:
+## Podman
+
+Homarr uses Podman's Docker-compatible API. Start the Podman socket, mount it, and include its in-container path in
+`DOCKER_SOCKET_PATHS`.
+
+For rootless Podman:
+
+```sh
+systemctl --user enable --now podman.socket
+podman info --format '{{.Host.RemoteSocket.Path}}'
+```
+
+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
-networks:
-  - socket-proxy
+environment:
+  DOCKER_HOSTNAMES: docker-proxy-home,docker-proxy-lab
+  DOCKER_PORTS: 2375,2375
 ```
 
-3. Finally, if it is present, remove the default docker socket connection under `volumes` in the homarr service.
+:::warning Plaintext Docker API
+
+Unauthenticated Docker TCP provides control of the Docker host. Keep a socket proxy on a private network or use TLS.
+
+:::
+
+Use `DOCKER_ENDPOINTS` for named endpoints, TLS, or restricted capabilities:
+
+```yaml
+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"]
+      }
+    ]
+```
+
+Each endpoint requires a stable `id`, display `name`, `kind` (`docker` or `podman`), transport, and the `inventory`
+capability. Optional capabilities are `logs`, `lifecycle`, and `remove`.
+
+| 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`                                           |
+
+`DOCKER_ENDPOINTS` takes precedence over the socket, hostname, and port lists.
+
+## Use in Homarr
+
+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.
+
+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.
+
+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).
+
+## Security
+
+A Docker or Podman socket grants extensive host control. Prefer a least-privilege socket proxy when lifecycle access is
+not required.
+
+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.
+
+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,35 +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.download</code>,{" "}
-    <code>asset.statistics</code>,{" "}
-    <code>server.statistics</code>,{" "}
-    <code>server.about</code>.
-    <br />
-    Additional permissions may be required depending on your Immich version. If you encounter authorization errors, grant any missing permissions requested by the server.
-
-  </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."],
+    },
+  ]}
+/>