mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-10 02:25:56 +00:00
rcourtman
7996848b64
A paying operator asked the Assistant to reboot five Proxmox VMs matching a name pattern (GitHub #1782, support mail 2026-08-26 and 2026-08-29). The model resolved the VMs and then ended with a report that invented a prerequisite: a QEMU guest agent on 6.3.2, a "discovery binding" on stable 6.4.0. It never planned the action. Three defects made the governed path fail whenever the model did try it, and nothing refused the prose ending when it did not: - pulse_control handed the session-scoped id (vm:<node>:<vmid>) to the action lifecycle, whose registry keys on canonical unified ids, so a Proxmox guest plan could never resolve. - pulse_control gated the action on the legacy per-executor action list, which never carried the canonical "reboot" capability Proxmox guests advertise, so "reboot" was refused as not permitted before planning. - A reference absent from the session context was refused with "resource discovery is required" even when the unified inventory resolved it. pulse_control now binds its target to the canonical unified resource (session alias first, then a unique inventory match, refusing ambiguity with candidate ids and naming the pulse_query recovery on a miss), passes the canonical id to the planner, and answers "not available" only from the resource's current advertised capabilities. The FSM ordering block and the shared operating instructions state that a recoverable block is not a limitation to report, and the instructions require the governed action tool for advertised capabilities. The agentic loop adds a bounded advertised-action gate: when the operator asked for a lifecycle action, pulse_control was offered but never submitted, and a session-resolved resource advertises the action, a tool-free final answer is refused once with the exact per-target calls. Covered by tools and loop unit tests (the #1782 transcript against a scripted provider fails on the previous code with the two exact errors above), a prompt-contract test, and the live eval scenario ProxmoxBulkLifecycleActionScenario.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.