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.
Can't enable secure DNS option in Brave because of policy
Reported by rogeriopvl · filed Oct 25, 2025Closed upstream on 2026-02-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Thinkpad X1 Nano
What's wrong?
When opening Brave settings there's a message saying that "Your browser is managed by your organization".
The issue is that when Brave is "managed," it restricts the ability to configure important security settings, such as Secure DNS:
<img width="1083" height="163" alt="Image" src="https://github.com/user-attachments/assets/ddfc05b7-8657-4746-ae5b-6789e88c0ae1" />
Is there a way to make the theme color policy optional and revert Brave to an "unmanaged" state permanently? I know I can eventually solve the problem by removing the policy from /etc/brave/policies/managed/color.json, but it will probably be restored in the next omarchy update.
I believe it's crucial to retain control over such security settings rather than sacrificing them for superficial features like color themes.
Edit: I can also confirm that the same is happening with Chromium.
View raw text
### System details Thinkpad X1 Nano ### What's wrong? When opening Brave settings there's a message saying that "Your browser is managed by your organization". The issue is that when Brave is "managed," it restricts the ability to configure important security settings, such as Secure DNS: <img width="1083" height="163" alt="Image" src="https://github.com/user-attachments/assets/ddfc05b7-8657-4746-ae5b-6789e88c0ae1" /> Is there a way to make the theme color policy optional and revert Brave to an "unmanaged" state permanently? I know I can eventually solve the problem by removing the policy from `/etc/brave/policies/managed/color.json`, but it will probably be restored in the next omarchy update. I believe it's crucial to retain control over such security settings rather than sacrificing them for superficial features like color themes. **Edit:** I can also confirm that the same is happening with Chromium.
- ddfc05b7-8657-4746-ae5b-6789e88c0ae1
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.
No decision has been recorded yet.