Omahub
← All plugins
E

Bar Autohide

by Eric van Riet Paap

Event-driven auto-hide for the Omarchy bar

GitHub

Security review

No obvious issues detected

Deterministic scan — not a security guarantee

None
Risk level
None
Analyzed commit
514d6fc
Scanned
1 month ago

No potentially dangerous behavior detected in the analyzed commit.

Automated analysis only — not a security guarantee.

AI advisory review

No obvious issues detected

Language-model assessment · ~deepseek/deepseek-v4-flash-latest — advisory only

Low
AI risk level
Low
Recommendation
install
Model
~deepseek/deepseek-v4-flash-latest
Analyzed commit
514d6fc
Reviewed
1 month ago

The plugin is a straightforward QML service that toggles a bar visibility marker file based on pointer events, with no obfuscation, persistence, or credential access. The only file operations are touch/rm on a state file under ~/.local/state/omarchy/toggles, and the dev scripts are clearly documented as local helpers not run during normal install. The deterministic scan found no issues, and my review agrees with that assessment.

  • The service uses shell commands (touch/rm) to manage a state file, but paths are shell-quoted and limited to a dedicated state directory, so risk is minimal.
  • The dev-install.sh script modifies the user's shell.json and restarts the shell, but it is explicitly a development helper and not executed during normal plugin installation.
How this check works

This review combines the deterministic scan (the rule-based results above) with an independent look at the plugin's code by a language model. The model reads a trimmed sample of the repository's files, the manifest, and the README, then gives a plain-language risk level and a recommendation: install (no notable danger), review (look closer first), or avoid (clearly dangerous).

It runs on the same analyzed commit as the deterministic scan and is strictly advisory — it is not a security guarantee and never blocks a plugin by itself. A human moderator still reviews plugins before they are listed.

AI advisory only — automated analysis, not a security guarantee.

Install
$ omarchy plugin add https://github.com/ericvrp/omarchy-bar-autohide --enable
Appearance #Hyprland #bar

Omarchy Bar Autohide

An event-driven auto-hide service plugin for the Omarchy bar.

Omarchy Bar Autohide hidden and revealed states

[!IMPORTANT] This plugin is for Omarchy 4 (Quattro), where the desktop shell and bar use Quickshell. It is not intended for older Omarchy releases that use Waybar.

Behavior

  • Supports bars anchored to the top, bottom, left, or right screen edge.
  • Reveals the bar only when the pointer reaches its anchored screen edge.
  • Keeps the bar open while the pointer remains over it.
  • Hides the bar 1000ms after the pointer leaves that area.
  • Leaves the bar visible when the user opens it with the bar hotkey.
  • Keeps the bar visible while a bar popout is open.
  • Supports multiple monitors, scaling, rotation, and monitor offsets.

A transparent one-pixel Quickshell surface listens for pointer entry at the bar edge. A passive hover observer attached to each live bar surface handles pointer exit without blocking its controls. There is no cursor polling and no persistent helper process, so the plugin causes no idle timer wakeups.

Requirements

  • Omarchy with the Quickshell bar
  • Hyprland

Install

omarchy plugin add https://github.com/ericvrp/omarchy-bar-autohide.git --enable

Omarchy clones the repository to ~/.config/omarchy/plugins/ericvrp.bar-autohide, validates it, and enables the service in the shell configuration.

Update

omarchy plugin update ericvrp.bar-autohide

Disable

omarchy plugin disable ericvrp.bar-autohide

Disabling or removing the plugin restores the bar visibility state from before the plugin was enabled.

Uninstall

omarchy plugin remove ericvrp.bar-autohide

License And Warranty

Licensed under the MIT License.

The software is provided as is, without warranty of any kind, express or implied. See the license for the complete warranty and liability disclaimer.

Development and local testing instructions are in DEVELOPING.md.