Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Feature: manage NetworkManager VPN profiles from the built-in network panel
Reported by sparksbenjamin · filed Aug 27, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Feature request: manage NetworkManager VPN profiles from the built-in network panel
Omarchy now uses NetworkManager for desktop networking, but the built-in omarchy.network panel currently focuses on Wi-Fi, Ethernet, DNS, and related network actions. VPN profiles installed through NetworkManager are not discoverable or connectable from the panel.
Proposed behavior
- Show saved VPN profiles in the existing network panel.
- Show active VPN tunnels and provide connect/disconnect actions.
- Use NetworkManager's generic VPN API so the feature works with installed plugins rather than hard-coding one provider.
- Provide a path to import or open the system connection editor for profiles such as OpenVPN
.ovpnfiles. - Support OpenConnect profiles, including AnyConnect deployments that require external-browser/SAML SSO.
- Keep secrets handled by NetworkManager and the existing polkit/keyring flow.
This would make Hack The Box OpenVPN profiles and work VPNs manageable from the same built-in surface as Wi-Fi and Ethernet, without requiring a separate tray applet.
The implementation should remain optional when no VPN plugin or profile is installed, and should preserve the current panel behavior for systems without VPN connections.
View raw text
## Feature request: manage NetworkManager VPN profiles from the built-in network panel Omarchy now uses NetworkManager for desktop networking, but the built-in `omarchy.network` panel currently focuses on Wi-Fi, Ethernet, DNS, and related network actions. VPN profiles installed through NetworkManager are not discoverable or connectable from the panel. ### Proposed behavior - Show saved VPN profiles in the existing network panel. - Show active VPN tunnels and provide connect/disconnect actions. - Use NetworkManager's generic VPN API so the feature works with installed plugins rather than hard-coding one provider. - Provide a path to import or open the system connection editor for profiles such as OpenVPN `.ovpn` files. - Support OpenConnect profiles, including AnyConnect deployments that require external-browser/SAML SSO. - Keep secrets handled by NetworkManager and the existing polkit/keyring flow. This would make Hack The Box OpenVPN profiles and work VPNs manageable from the same built-in surface as Wi-Fi and Ethernet, without requiring a separate tray applet. The implementation should remain optional when no VPN plugin or profile is installed, and should preserve the current panel behavior for systems without VPN connections.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 09:29 UTC