mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-26 21:47:20 +00:00
rcourtman
db57faf1c0
Patrol now has two modes: **Watch only** reports findings, and **Ask first** investigates and proposes fixes. Every fix waits in Actions for an operator to approve and run it. Safe auto-fix (`assisted`) and Autopilot (`full`) are retired. Why: schema-v17 telemetry for the week to 2026-10-11 counts 1 assisted and 2 full installs out of 612 reporting Patrol, and 4 executed Patrol actions in 30 days, all on one install. No GitHub issue asks for more autonomy. Meanwhile the automatic path carried its own policy leases, acknowledgement store, per-resource allowlist, release gate and Colima lab. Investigation is what paid installs use, so it stays. Behaviour - A saved `assisted`, `full` or `autonomous` level reads as `approval`. Both autonomy update routes refuse those levels with `400 invalid_autonomy_level`. The acknowledgement routes are gone. - The core Patrol action broker only plans: `Plan` and `Submit` persist the plan and return. `TestContract_PatrolActionBrokerOnlyPlans` forbids execution calls in its source. - Removed: - `ExecuteUnderPolicy`, the policy authorization lease, and the policy execution store methods; - Autopilot acknowledgement persistence, its routes and its dialog; - the per-resource automatic-action allowlist: type, API field and drawer editor. The store column is written as NULL. - Kept for compatibility: - `GetPatrolFullModeUnlocked` stays on the extension contract and reports false; - historical action records keep their lease and reason codes decodable, labelled as retired modes. - The Patrol inbox no longer has a "continuing without a decision" bucket: every current issue is an operator decision. Governance - RG-06 now proves Patrol never executes without an operator decision (integration tier). - RG-02/RG-04 and the RA35/RA39/RA40 proof commands point at surviving tests. Every `-run` name was checked against `git grep '^func Test'`. - Pro plan copy, AI docs, privacy telemetry wording and the subsystem contracts describe the two modes. Verification - Go: vet is clean. config, ai, ai/qualification, telemetry, actionlifecycle, unifiedresources, aicontracts and api pass on pulse-dev. - Frontend: type-check and lint are clean; 217 related test files pass. - Governance: release_control Python suites, status/registry audits and the docs mirror pass. - Browser: a pulse-enterprise build of this tree with a Pro licence, run before and after merging onto main: - the Patrol selector has exactly two modes, and each save reads back; - retired levels get 400, and the acknowledgement route returns 404; - the drawer Manage tab has no allowlist editor and still saves; - phone width is fine; the plan page shows no retired modes.
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.
Need help with a failure? Read the safe reporting guidance before sharing evidence. A second reproduction or diagnostics export is not required; keep the original evidence if another attempt could interrupt workloads or send duplicate notifications. GitHub reports and attachments are public: review them locally and keep credentials and private details out.
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.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- 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.