Chisle
코딩 에이전트 플러그인, 20개 실시간 작업에서 기본 모델 52% 활용, 간결한 페르소나와 출력 압축 제공
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
The omarchy-asus plugin for Omarchy: one panel for an ASUS laptop's hardware (keyboard and Slash LEDs, per-charger refresh rate, keyboard and power limits, charge limit, Fn+Super). Part of omarchy-asus: https://omarchy-asus.github.io
README 전체를 불러오는 중입니다.
README 전문 보기 ↗One panel for your ASUS laptop's hardware, in the Omarchy bar.
From omarchy-asus: ASUS fixes for Omarchy. A signed pacman repo carries the kernel, NVIDIA and Omarchy fixes that make an ASUS laptop work properly: the Fn+Super Win-lock keys, the touchpad, sleep with an HDMI monitor attached, the NVIDIA hibernate hang, USB-C charging profiles and more. This plugin is the control panel. → omarchy-asus.github.io · repository
Written and tested on the ASUS ROG Zephyrus G16 (GA605). Everything goes through asusd and the kernel's ASUS drivers, and each section hides when your laptop doesn't have it, so other ASUS models get what they support. The lid Slash LEDs, for example, appear only on models that have them.
hyprctl reload.omarchy-plugin-add https://github.com/omarchy-asus/omarchy-asus-plugin --enable
Update with omarchy-plugin-update io.github.omarchy-asus.panel; the shell reloads it by itself.
Needs: stock Omarchy (Python and PyGObject are already there). Optional:
asusd (asusctl): the keyboard, Slash, charge limit and power limits. Without it those sections hide.asus-rog-nkey-winlock and the Win-lock kernel patch, both from omarchy-asus./usr/bin/python3 -I ~/.config/omarchy/plugins/io.github.omarchy-asus.panel/bridge/asus_bridge.py release # only if you set power limits or the charge hold
omarchy-plugin-remove io.github.omarchy-asus.panel
release turns off the fan curves and asusd PPT tuning groups the plugin turned on for power limits, so no limit outlives it, and puts back a charge limit a charge hold left behind. The plugin leaves your settings in place; delete them if you want a clean slate:
~/.config/omarchy/omarchy-asus.conf;~/.local/state/omarchy/omarchy-asus*;~/.config/systemd/user/g16-winlock.service.d/mode.conf, if you changed the Fn+Super mode./usr/bin/python3 -I -B bridge/asus_bridge.py, started by the shell with a cleared, allow-listed environment. It spawns nothing and uses no network.asusd: reads and sets the keyboard, Slash, charge limit, panel overdrive, PPT attributes, CPU fan-curve enable and the PPT tuning group. The last three only for power-limit keys you set.UPower: read only.logind SetBrightness: the screen backlight, only if you set BRIGHT_BATTERY.g16-winlock.service when you change the Fn+Super mode.hl.monitor() for the internal panel's refresh rate, and hotplug/reload events.~/.config/omarchy/omarchy-asus.conf, ~/.local/state/omarchy/ and the Win-lock drop-in above, and reads ~/.config/hypr/monitors.lua.
~/.local/state/omarchy/toggles/hypr/ it keeps one file, omarchy-asus-refresh.lua: the panel's refresh rate as an hl.monitor() line that Omarchy loads on every Hyprland reload. Only while the bridge runs, a rate is set and monitors.lua has a rule for the panel; the bridge removes it when it stops./ one component at a time without following symbolic links; each must be yours or a root-owned system directory, and none of yours may be writable by your group or others.0600) temporary file that is atomically renamed into place. A file is never left writable by anyone but you.omarchy-asus.conf (copy it from your dotfiles), and the log says so if it is a link.The widget applies these itself on every plug and unplug. They live in
~/.config/omarchy/omarchy-asus.conf, as plain KEY=VALUE lines (never run as
a script):
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗