Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-3052GitHub issuePublicReceived

Waybar Custom Widget Persistence

Reported by Somnius · filed Sep 27, 2025Closed upstream on 2025-09-29 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Waybar Custom Widget Persistencerevision 1 · captured 2026-10-04 11:35 UTC via poll

Waybar Custom Widget Persistence

About 2 weeks ago i added a Tailscale status indicator on my waybar config, 

 "custom/tailscale": {
    "exec": "~/.config/waybar/scripts/tailscale-status.sh",
    "interval": 10,
    "return-type": "json",
    "format": "{text}",

    "on-click": "bash -c 'NAME=$(tailscale

[...] if you want the status and toggle scripts just ask.

and when i got the latest version of the dhh dotfiles it got replaced with defaults, no problem there i had a backup and merge/diff it. BUT

Why not include in the end a "CUSTOM" widget to chainload more stuff onto the waybar ?

e.g.
in the start of the waybar config

"custom/test",

in the end of file

},
  "include": "custom.jsonc"
}

and on the custom.jsonc file we just requested a simple test

{
  "custom/test": {
    "format": "TEST",
    "tooltip-format": "This is a test module"
  }
}

The result will be

<img width="345" height="46" alt="Image" src="https://github.com/user-attachments/assets/de72a67e-3962-4d26-ae8c-b70788cde234" />

That way users can create their own custom widgets that CAN survive and update, if it is empty nothing is called.

Basic requirements call it up top via its name custom/test and place the widget on the custom.jsonc and that is it.

pkill waybar
waybar &

And see the results 😉

View raw text
### Waybar Custom Widget Persistence

About 2 weeks ago i added a Tailscale status indicator on my waybar config, 

```
 "custom/tailscale": {
    "exec": "~/.config/waybar/scripts/tailscale-status.sh",
    "interval": 10,
    "return-type": "json",
    "format": "{text}",

    "on-click": "bash -c 'NAME=$(tailscale 
```
[...] _if you want the status and toggle scripts just ask._

and when i got the latest version of the dhh dotfiles it got replaced with defaults, no problem there i had a backup and merge/diff it. BUT

Why not include in the end a "CUSTOM" widget to chainload more stuff onto the waybar ?

e.g. 
in the start of the waybar config
```
"custom/test",
```

in the end of file
```
},
  "include": "custom.jsonc"
}
```

and on the `custom.jsonc` file we just requested a simple test

```
{
  "custom/test": {
    "format": "TEST",
    "tooltip-format": "This is a test module"
  }
}
```

The result will be 

<img width="345" height="46" alt="Image" src="https://github.com/user-attachments/assets/de72a67e-3962-4d26-ae8c-b70788cde234" />

That way users can create their own custom widgets that CAN survive and update, if it is empty nothing is called.

Basic requirements call it up top via its name `custom/test` and place the widget on the `custom.jsonc` and that is it.

```
pkill waybar
waybar &
```

And see the results 😉
  • de72a67e-3962-4d26-ae8c-b70788cde234

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.