marceloeatworld/hyprland-ai-skill
hyprland
FlaggedThis skill should be used when the user asks about "Hyprland configuration", "hyprland.lua", "hyprland.conf", "Hyprland Lua config", "hyprctl", "Hyprland keybinds", "Hyprland window rules", "Hyprland monitors", "Hyprland dispatchers", "Hyprland animations", "Hyprland workspaces", "Hyprland IPC", "Hyprland plugins", "hyprlock", "hypridle", "hyprpaper", "hyprcursor", "hyprpicker", "hyprsunset", "xdg-desktop-portal-hyprland", "Hyprland on NixOS", "Hyprland Home Manager", "Hyprland layouts", "Hyprland dwindle", "Hyprland master layout", "Hyprland FAQ", "Hyprland performance", "Hyprland Nvidia", "Hyprland screen sharing", "Hyprland special workspace", "Hyprland smart gaps", "Hyprland multi-monitor", "Hyprland tearing", or any topic related to configuring, troubleshooting, or extending the Hyprland Wayland compositor and its ecosystem tools.
references/hyprsunset.md
View on GitHub<!-- source: https://wiki.hypr.land/hypr-ecosystem/user/hyprsunset -->
<!-- wiki commit: 41c7222 (2026-11-20 18:16:21 +0100) -->
<!-- auto-generated by scripts/generate-references.sh - DO NOT EDIT MANUALLY -->
---
weight: 80
title: hyprsunset
---
[hyprsunset](https://github.com/hyprwm/hyprsunset) is a small utility to provide a blue light filter for your system.
This method is preferred to screen shaders as it will _not_ be captured via recording/screenshots.
hyprsunset also provides a gamma filter, which can be used to adjust perceived display brightness on monitors that do not support software control, or to reduce perceived brightness below the monitor's minimum.
## Configuration
Configuration is done via the config file at `~/.config/hypr/hyprsunset.conf`.
This file is not required for running hyprsunset, though recommended.
Hyprsunset uses profiles to determine when to change temperature and gamma.
You can define as many profiles as you like.
Each Profile is activated at it's specified time and resets all options set by other profiles.
On startup, hyprsunset will apply the current profile.
For example, when launching hyprsunset with the following example config at 20:00, it will activate the first profile, essentially changing nothing.
Once the clock strikes 21:00, hyprsunset will automatically apply the new profile.
| Variable | Description | Type | Default |
| -- | -- | -- | -- |
| `max-gamma` | The maximum percentage the gamma value can be. Absolute maximum is `200`%. Mostly useful when controlling hyprsunset via IPC | int | `100` |
### Profile
| Variable | Description | Type | Default |
| -- | -- | -- | -- |
| `time` | The time at which the profile should be activated. Must be in the format `<hours>:<minutes>` | string | `00:00` |
| `temperature` | The screen temperature. Lower means warmer | int | `6000` |
| `gamma` | The perceived brightness of the screen. This will allow you to lower the brightness beyond your screen's minimum | float | `1.0` |
| `identity` | When set, the value of temperature is ignored and the only effect of hyprsunset is the change in apparent brightness by gamma | bool | `false` |
| `on-switch` | A command to be executed when the profile is activated | string | [[Empty]] |
{{% details title="Example" closed="true" %}}
```ini
max-gamma = 150
profile {
time = 7:30
identity = true
}
profile {
time = 21:00
temperature = 5500
gamma = 0.8
}
```
{{% /details %}}
## Usage
To autostart hyprsunset, add: `hyprsunset` to your `hyprland.lua`'s autostart section.
<!-- If Hyprland is started with [uwsm](../../Useful-Utilities/Systemd-start), you can use `systemctl --user enable --now hyprsunset.service`. -->
Hyprsunset can also be controlled by supplying arguments to the command.
By specifying `hyprsunset --temperature 5000` you will override the current active config's temperature setting.
This however, will be overridden once a new profile is activated.
For more information on CLI arguments, run `hyprsunset --help`
## IPC
`hyprsunset` supports IPC via hyprctl.
Both color temperature and the gamma filter are adjustable:
```sh
# Enable blue-light filter
hyprctl hyprsunset temperature 2500
# Disable blue-light filter
hyprctl hyprsunset identity
# Set gamma to 50%
hyprctl hyprsunset gamma 50
# Increase gamma by 10%
hyprctl hyprsunset gamma +10
# Reset config to current profile
hyprctl hyprsunset reset
# Reset value to current profile
hyprctl hyprsunset reset temperature
hyprctl hyprsunset reset gamma
hyprctl hyprsunset reset identity
# Print current profile
hyprctl hyprsunset profile
```
This can be used by other software to change the temperature throughout the day, or to adjust perceived monitor brightness, such as with the following Hyprland keybinds:
```lua
hl.bind("XF86MonBrightnessUp", hl.dsp.exec_cmd("hyprctl hyprsunset gamma +10"), { repeating = true, locked = true, })
hl.bind("XF86MonBrightnessDown", hl.dsp.exec_cmd("hyprctl hyprsunset gamma -10"), { repeating = true, locked = true, })
```
> [!WARNING]
> Using the gamma control will degrade color accuracy.
> If your monitor does support software control, it is highly recommended to use that instead.
## On-Switch Command
The following example shows how the `on-switch` command can be utilized.
This particular example shows that a GTK theme command is run for each profile as a form of light and dark mode.
When a profile is activated, the designated `on-switch` command is run:
```ini
# Light Mode
profile {
time = 8:00
temperature = 6000
on-switch = gsettings set org.gnome.desktop.interface color-scheme "prefer-light"
}
# Dark Mode
profile {
time = 20:00
temperature = 1500
on-switch = gsettings set org.gnome.desktop.interface color-scheme "prefer-dark"
}
```
Other use cases for this include updating the Omarchy night light indicator by setting the `on-switch` command to `omarchy-shell -q nightlight refresh`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |