Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Point locked container updates at the host's command setup
rcourtman28217e083699
diff --git a/docs/DOCKER.md b/docs/DOCKER.mdindex bec0c2a873..ec85676a6f 100644--- a/docs/DOCKER.md+++ b/docs/DOCKER.md@@ -659,7 +659,7 @@ Pulse can start, stop, and restart Docker / Podman containers directly from the- **Command execution enabled** on the agent — it is disabled by default. Either:- start the agent with `--enable-commands` (or `PULSE_ENABLE_COMMANDS=true`), or- tick **Allow Pulse to run commands on this host** in the token step of **Settings → Infrastructure** before copying the install command, which adds the flag and grants the token the command execution permission. Pulse can then run commands as root on that host: this is the full-trust combined profile, not a least-privilege setting- - an agent installed without it cannot be switched on from Pulse; run the new install command on the host+ - an agent installed without it cannot be switched on from Pulse; run the new install command on the host. On the host's **Manage** dialog in **Settings → Infrastructure**, **Remote commands** opens the installer with this option already ticked- **Admin approval**: every lifecycle action requires confirmation by an admin in the UI before it runs. The agent then verifies the container's state before the change and confirms it actually reached the requested state afterwards.### Limitationsdiff --git a/docs/release-control/v6/internal/subsystems/agent-lifecycle.md b/docs/release-control/v6/internal/subsystems/agent-lifecycle.mdindex 1f19cde52f..8ba94cc6a9 100644--- a/docs/release-control/v6/internal/subsystems/agent-lifecycle.md+++ b/docs/release-control/v6/internal/subsystems/agent-lifecycle.md@@ -306,6 +306,22 @@ Enrollment, receipt freshness, removal, correlation and stored observations keeptheir existing semantics. The host disk recording and API presence regressionscover this distinction; they do not establish installed guest recovery.+### A host without command access hands over the host-side step (3 November 2026)++Settings → Infrastructure → Manage on an agent whose `commandsEnabled` is not+true shows a Remote commands section instead of a bare "Not enabled" card. It+says Pulse cannot apply container updates or other actions on that host, that+command access is granted on the host rather than from Pulse, and names the+installer option. Its button closes the dialog, sets the shared install state's+command-access choice through `setEnableCommands(true)` (the same atomic+token/flag path as the checkbox) and opens the agent installer, so the option+arrives ticked; it is disabled while a token is minting because that path+ignores a change mid-mint. Attached agents of a platform source show the same+section. Pulse still offers no in-app switch: a `monitoring-only` ceiling is+local by design, so a compromised Pulse cannot grant itself execution. The+locked Docker update pill points at this dialog. `InfrastructureWorkspace.test.tsx`+pins the section and the preset installer navigation.+### Command access is a named token-step choice, not a legacy option (21 October 2026)The installer's command-access checkbox reads **Allow Pulse to run commands on@@ -329,7 +345,7 @@ use the only working route: Docker updates dispatch through the agent commandsession, the separate action runner's container actions are unqualified, androotful Docker under the safe collector profile carries no update checks oractions. The label is owned by `getUnifiedAgentCommandAccessOptionLabel`, which-the locked Docker update pill and the Proxmox setup guide also read, so copy+a host's Remote commands section and the Proxmox setup guide also read, so copythat sends users to it cannot drift from the checkbox.`InfrastructureInstallerSection.test.tsx` pins the checkbox in the token stepwith its root-access and replacement descriptions.diff --git a/docs/release-control/v6/internal/subsystems/frontend-primitives.md b/docs/release-control/v6/internal/subsystems/frontend-primitives.mdindex 900ecee2e6..04ac9d6ced 100644--- a/docs/release-control/v6/internal/subsystems/frontend-primitives.md+++ b/docs/release-control/v6/internal/subsystems/frontend-primitives.md@@ -864,6 +864,14 @@ names the installer option through `getUnifiedAgentCommandAccessOptionLabel`install command on, instead of the retired "legacy combined command profile"wording and its advanced-options path.+Superseded 3 November 2026: the pill now says the host's agent "does not+accept commands from Pulse" (an absent `commandsEnabled` reads as false, so it+no longer claims how the agent was installed) and sends users to Settings →+Infrastructure → Manage on that host → Remote commands, which names the option+and opens the installer with it ticked. The pill no longer reads the shared+label itself. `containerUpdateBadgeModel.unavailable.test.ts` and+`ContainerUpdateBadge.test.tsx` pin the wording.+### Container update control offers only what the server advertises (21 October 2026)`UpdateButton` is live only when the server advertises the `update` capabilitydiff --git a/frontend-modern/browser-verification/2f61f3d99fca98f6.json b/frontend-modern/browser-verification/2f61f3d99fca98f6.jsonnew file mode 100644index 0000000000..da71dac79b--- /dev/null+++ b/frontend-modern/browser-verification/2f61f3d99fca98f6.json@@ -0,0 +1,40 @@+{+ "version": 1,+ "base_sha": "94a368de87f1454a50ad598a2ba4a18e25fc4456",+ "verified_at": "2026-11-03T14:10:00Z",+ "result": "passed",+ "changed_paths": [+ "frontend-modern/src/components/Settings/InfrastructureWorkspace.tsx",+ "frontend-modern/src/components/shared/containerUpdateBadgeModel.ts"+ ],+ "content_sha256": {+ "frontend-modern/src/components/Settings/InfrastructureWorkspace.tsx": "ebaa5b5812e21e19ff7791945a71933fd17119c6967f9f49e99e682c99b643b1",+ "frontend-modern/src/components/shared/containerUpdateBadgeModel.ts": "a6a9e59af671c4a232962e1740be9323e1f6c3cc9a1c135fc22023309909395b"+ },+ "routes": [+ "/settings/infrastructure",+ "/settings/infrastructure?add=agent",+ "/docker"+ ],+ "viewports": [+ {+ "width": 1440,+ "height": 1000+ },+ {+ "width": 375,+ "height": 812+ }+ ],+ "states": [+ "Manage dialog for a mock agent host without command access shows the Remote commands are off section and no Not enabled info card",+ "Phone width: section and full-width 44px Get install command button fit with no horizontal page scroll",+ "Add Pulse Agent installer opened from the section shows Allow Pulse to run commands on this host already ticked",+ "Docker page locked update pills (11 containers) carry the new does not accept commands from Pulse explanation naming Manage on the host"+ ],+ "interactions": [+ "Opened Manage on agent:host-linux-1 from the infrastructure ledger",+ "Clicked Get install command and confirmed the route and checkbox state",+ "Read the locked update pill explanations on the Docker page"+ ]+}diff --git a/frontend-modern/public/docs/DOCKER.md b/frontend-modern/public/docs/DOCKER.mdindex bec0c2a873..ec85676a6f 100644--- a/frontend-modern/public/docs/DOCKER.md+++ b/frontend-modern/public/docs/DOCKER.md@@ -659,7 +659,7 @@ Pulse can start, stop, and restart Docker / Podman containers directly from the- **Command execution enabled** on the agent — it is disabled by default. Either:- start the agent with `--enable-commands` (or `PULSE_ENABLE_COMMANDS=true`), or- tick **Allow Pulse to run commands on this host** in the token step of **Settings → Infrastructure** before copying the install command, which adds the flag and grants the token the command execution permission. Pulse can then run commands as root on that host: this is the full-trust combined profile, not a least-privilege setting- - an agent installed without it cannot be switched on from Pulse; run the new install command on the host+ - an agent installed without it cannot be switched on from Pulse; run the new install command on the host. On the host's **Manage** dialog in **Settings → Infrastructure**, **Remote commands** opens the installer with this option already ticked- **Admin approval**: every lifecycle action requires confirmation by an admin in the UI before it runs. The agent then verifies the container's state before the change and confirms it actually reached the requested state afterwards.### Limitationsdiff --git a/frontend-modern/src/components/Settings/InfrastructureWorkspace.tsx b/frontend-modern/src/components/Settings/InfrastructureWorkspace.tsxindex f437fc089a..d4aee6ad3b 100644--- a/frontend-modern/src/components/Settings/InfrastructureWorkspace.tsx+++ b/frontend-modern/src/components/Settings/InfrastructureWorkspace.tsx@@ -14,6 +14,7 @@ import X from 'lucide-solid/icons/x';import { presentationPolicyIsReadOnly } from '@/stores/sessionPresentationPolicy';import { hasFeature, runtimeCapabilitiesLoaded } from '@/stores/license';import { copyToClipboard } from '@/utils/clipboard';+import { getUnifiedAgentCommandAccessOptionLabel } from '@/utils/unifiedAgentInventoryPresentation';import { notificationStore } from '@/stores/notifications';import { updateStore } from '@/stores/updates';import { eventBus } from '@/stores/events';@@ -488,6 +489,48 @@ const InfrastructureWorkspaceContent: Component<InfrastructureWorkspaceProps> =</div>);+ // A monitoring-only agent sets its command ceiling locally at install time,+ // so Pulse cannot raise it from here; that is what keeps such a host safe+ // from a compromised Pulse. The locked Docker update pill sends users to+ // this dialog, so it names the one host-side step and opens the installer+ // with that option already ticked.+ const openCommandAccessInstaller = () => {+ closeEditFlow();+ void operations.setEnableCommands(true);+ openAddFlow('agent');+ };++ const renderRemoteCommandsSetup = (connection: Connection) => (+ <Show when={connection.agentIdentity && !connection.agentIdentity.commandsEnabled}>+ <section class="rounded-xl border border-border bg-surface p-4" aria-label="Remote commands">+ <div class="flex flex-col gap-3 sm:flex-row sm:items-start sm:justify-between">+ <div class="space-y-1">+ <div class="text-sm font-semibold text-base-content">Remote commands are off</div>+ <p class="text-xs text-muted">+ Pulse can't apply container updates or other actions on {connection.name}. Command+ access is granted on the host, not from Pulse: run the install command on{' '}+ {connection.name} with{' '}+ <span class="font-medium">{getUnifiedAgentCommandAccessOptionLabel()}</span> ticked.+ </p>+ </div>+ <Show when={!readOnly()}>+ <Button+ variant="outline"+ size="settingsAction"+ class="shrink-0"+ // The install state ignores a command-access change while a token+ // is minting, so the installer would open without the option.+ disabled={operations.isGeneratingToken()}+ onClick={openCommandAccessInstaller}+ >+ Get install command+ </Button>+ </Show>+ </div>+ </section>+ </Show>+ );+const renderAgentConnectionDetails = (connection: Connection) => {const removePending = () => rowActions.pendingAction(connection.id) === 'remove';const removeConfirming = () => rowActions.confirmingRemove(connection.id);@@ -537,11 +580,8 @@ const InfrastructureWorkspaceContent: Component<InfrastructureWorkspaceProps> =<Show when={connection.agentIdentity?.architecture?.trim()}>{(architecture) => infoCard('Architecture', architecture())}</Show>- <Show when={connection.agentIdentity}>- {infoCard(- 'Remote commands',- connection.agentIdentity?.commandsEnabled ? 'Enabled' : 'Not enabled',- )}+ <Show when={connection.agentIdentity?.commandsEnabled}>+ {infoCard('Remote commands', 'Enabled')}</Show></div>@@ -552,6 +592,8 @@ const InfrastructureWorkspaceContent: Component<InfrastructureWorkspaceProps> =</Show></section>+ {renderRemoteCommandsSetup(connection)}+<section class="rounded-xl border border-border bg-surface p-4"><div class="space-y-3"><div class="space-y-1">@@ -686,6 +728,8 @@ const InfrastructureWorkspaceContent: Component<InfrastructureWorkspaceProps> =</div></div>+ <div class="mt-3 empty:hidden">{renderRemoteCommandsSetup(connection)}</div>+<Show when={error()}>{(message) => (<divdiff --git a/frontend-modern/src/components/Settings/__tests__/InfrastructureWorkspace.test.tsx b/frontend-modern/src/components/Settings/__tests__/InfrastructureWorkspace.test.tsxindex 67d17d4439..b30dbeb0aa 100644--- a/frontend-modern/src/components/Settings/__tests__/InfrastructureWorkspace.test.tsx+++ b/frontend-modern/src/components/Settings/__tests__/InfrastructureWorkspace.test.tsx@@ -65,6 +65,7 @@ const emptyFleetMember = vi.hoisted(}) as Pick<InfrastructureSystemMemberRow, 'fleetSignals' | 'fleetHighlights'>,);const navigateSpy = vi.hoisted(() => vi.fn());+const setEnableCommandsSpy = vi.hoisted(() => vi.fn());const presentationPolicyIsReadOnlyMock = vi.hoisted(() => vi.fn(() => false));const originalResizeObserver = globalThis.ResizeObserver;@@ -130,6 +131,7 @@ vi.mock('../useInfrastructureOperationsState', () => ({customCaPath: () => '',insecureMode: () => false,selectedAgentUrl: () => 'http://pulse',+ setEnableCommands: setEnableCommandsSpy,getAgentConnectionUpgradeCommand: (connection: Connection, installFlags: string[] = []) =>`upgrade ${connection.id}${installFlags.length > 0 ? ` ${installFlags.join(' ')}` : ''}`,getAgentConnectionUpgradeCommandRequiresToken: () => false,@@ -1690,6 +1692,66 @@ describe('InfrastructureWorkspace', () => {expect(screen.getAllByText('Enabled').length).toBeGreaterThan(0);});+ it('hands an agent without command access the host-side step and the preset installer', async () => {+ const towerAgent = connectionFixture({+ id: 'agent:tower',+ type: 'agent',+ name: 'Tower',+ address: 'Tower',+ surfaces: ['host', 'docker'],+ scope: { host: true } as any,+ source: 'agent',+ agentVersion: '6.0.3',+ agentIdentity: { hostname: 'tower', platform: 'linux' },+ capabilities: { supportsPause: false, supportsScope: false, supportsTest: false },+ });++ connectionState.connections = [towerAgent];+ connectionState.rows = [+ {+ id: towerAgent.id,+ ownerType: 'agent',+ name: 'Tower',+ subtitle: 'via Pulse Agent',+ source: 'agent',+ host: 'tower',+ coverageLabels: ['Host telemetry'],+ statusLabel: 'Active',+ statusClassName: 'bg-green-100 text-green-800',+ agentUpdateCount: 0,+ lastActivityText: '0s ago',+ ...emptyFleetRow,+ enabled: true,+ canEdit: false,+ canPause: false,+ canRemove: true,+ isAgent: true,+ isCluster: false,+ attachedConnections: [],+ members: [],+ connection: towerAgent,+ },+ ];++ renderWorkspace();++ await waitFor(() => expect(screen.getByText('Tower')).toBeInTheDocument());+ fireEvent.click(screen.getByRole('button', { name: /^Manage$/i }));+ await waitFor(() => expect(screen.getByRole('dialog')).toBeInTheDocument());++ const section = screen.getByRole('region', { name: 'Remote commands' });+ expect(section).toHaveTextContent('Remote commands are off');+ expect(section).toHaveTextContent('Command access is granted on the host, not from Pulse');+ expect(section).toHaveTextContent('Allow Pulse to run commands on this host');++ navigateSpy.mockClear();+ fireEvent.click(within(section).getByRole('button', { name: 'Get install command' }));+ expect(setEnableCommandsSpy).toHaveBeenCalledWith(true);+ expect(navigateSpy).toHaveBeenCalledWith('/settings/infrastructure?add=agent', {+ scroll: false,+ });+ });+it('shows attached Pulse Agent augmentation details on a grouped platform source', async () => {const primaryConnection = connectionFixture();const attachedAgent = connectionFixture({diff --git a/frontend-modern/src/components/shared/__tests__/ContainerUpdateBadge.test.tsx b/frontend-modern/src/components/shared/__tests__/ContainerUpdateBadge.test.tsxindex 5bf55ca33b..77003e8df5 100644--- a/frontend-modern/src/components/shared/__tests__/ContainerUpdateBadge.test.tsx+++ b/frontend-modern/src/components/shared/__tests__/ContainerUpdateBadge.test.tsx@@ -245,11 +245,10 @@ describe('ContainerUpdateBadge', () => {));expect(screen.queryByRole('button')).not.toBeInTheDocument();- const status = screen.getByLabelText(/installed without command access/);+ const status = screen.getByLabelText(/does not accept commands from Pulse/);expect(status.getAttribute('aria-label')).toContain('the Pulse agent on Tower');- expect(status.getAttribute('aria-label')).toContain('Settings → Infrastructure');expect(status.getAttribute('aria-label')).toContain(- '"Allow Pulse to run commands on this host" selected and run it on Tower',+ 'choose Manage on Tower, and follow Remote commands',);});diff --git a/frontend-modern/src/components/shared/__tests__/containerUpdateBadgeModel.unavailable.test.ts b/frontend-modern/src/components/shared/__tests__/containerUpdateBadgeModel.unavailable.test.tsindex ae93a397ad..7738176cb9 100644--- a/frontend-modern/src/components/shared/__tests__/containerUpdateBadgeModel.unavailable.test.ts+++ b/frontend-modern/src/components/shared/__tests__/containerUpdateBadgeModel.unavailable.test.ts@@ -15,10 +15,9 @@ const disconnected = {describe('locked update explanation', () => {it('names a missing command access and where to turn it on', () => {const text = getUpdateUnavailableExplanation({ ...disconnected, hostCommandsEnabled: false });- expect(text).toContain('the Pulse agent on Tower was installed without command access');- expect(text).toContain('Settings → Infrastructure');+ expect(text).toContain('the Pulse agent on Tower does not accept commands from Pulse');expect(text).toContain(- '"Allow Pulse to run commands on this host" selected and run it on Tower',+ 'open Settings → Infrastructure, choose Manage on Tower, and follow Remote commands',);expect(text).not.toContain('advanced');expect(text).not.toContain('not connected');@@ -27,7 +26,7 @@ describe('locked update explanation', () => {it('tells a lost command channel apart from missing access', () => {const text = getUpdateUnavailableExplanation({ ...disconnected, hostCommandsEnabled: true });expect(text).toContain('the command channel to the Pulse agent on Tower is not connected');- expect(text).not.toContain('Allow Pulse to run commands');+ expect(text).not.toContain('Remote commands');});it("falls back to the server's reason when command access is unknown", () => {diff --git a/frontend-modern/src/components/shared/containerUpdateBadgeModel.ts b/frontend-modern/src/components/shared/containerUpdateBadgeModel.tsindex 7bdcba2fa0..b7d8a48d24 100644--- a/frontend-modern/src/components/shared/containerUpdateBadgeModel.ts+++ b/frontend-modern/src/components/shared/containerUpdateBadgeModel.ts@@ -1,6 +1,5 @@import type { DockerContainerUpdateStatus } from '@/types/api';import type { ResourceActionReadiness } from '@/types/resource';-import { getUnifiedAgentCommandAccessOptionLabel } from '@/utils/unifiedAgentInventoryPresentation';export interface ContainerUpdateBadgeProps {updateStatus?: DockerContainerUpdateStatus;@@ -126,8 +125,11 @@ export function getContainerUpdateCurrentTooltip(/*** What the locked "Update available" badge says when Pulse cannot apply the- * update. An agent installed without command access is the common case and has- * one fix, so it is named outright instead of the server's transport wording.+ * update. An agent that does not accept commands is the common case and has+ * one fix, so it is named outright instead of the server's transport wording,+ * with the exact place that hands over the command. An absent commandsEnabled+ * flag reads as false, so the copy says the agent does not accept commands+ * rather than claiming how it was installed.*/export function getUpdateUnavailableExplanation(input: {reason: string;@@ -139,10 +141,9 @@ export function getUpdateUnavailableExplanation(input: {if (input.reasonCode === 'command_agent_disconnected') {if (input.hostCommandsEnabled === false) {return (- `Update available. Pulse cannot apply it because the Pulse agent on ${host} was installed without command access.\n` +- `To allow updates from Pulse, copy the install command from Settings → Infrastructure with ` +- `"${getUnifiedAgentCommandAccessOptionLabel()}" selected and run it on ${host}. ` +- 'Otherwise, apply the update with your container manager.'+ `Update available. Pulse cannot apply it because the Pulse agent on ${host} does not accept commands from Pulse.\n` ++ `To allow it, open Settings → Infrastructure, choose Manage on ${host}, and follow Remote commands. ` ++ 'Or apply the update with your container manager.');}if (input.hostCommandsEnabled === true) {